I agree with Jack Spade mostly. At my table, if the drones were in the racks, I'd have counted them as just "part of the car" and no subjected them to damage. I'd probably also allow this if they were disabled/inactive and in someone's pocket because, as Jack also said...
If you start rolling damage on guns, then you'd also logically roll damage on armor every time someone's attacked. And their clothes. And anything they're carrying. And the ground they're standing on for some attacks.
It'd just be way too complex and, most importantly, not how the game is intended to be played. Gear can only be damaged when it's specifically targeted.
Now, no rule says this outright as far as I know, but here's the thing, attacks also as written only affect those targeted. If you shoot someone, you're shooting them, not their gear or weapon or armor. Yes, armor comes up, and it's reasonable to assume they have bullet-holes and blood if they take damage, but there's no mechanical impact on their armor. No rules say there would be.
Similarly, AoEs like some spells or grenades are left to "damage the scenery as appropriate". The "damaging barriers" rules on page 197 of the core book go indepth about this; but what I want to point out is the difference between "barriers" and "gear". Grenades in particular deal with barriers a lot, to determine if they bounce off of the walls and go that whole "totally OP please don't use this rule" thing. They don't bounce of players, even the ones who're more machine than man, covered head-to-toe in armor and carrying three backpacks full of gear and electronics.
It may seem unrealistic, but it's acceptable. It's like how no one has to worry about every single wound they take getting infected, and how bleeding out as an optional rule in a small side-book. For the sake of gameplay to remain fun without having to overcomplicate every step. Even GURPS takes these kind of conveniences at times.
