On Mon, Apr 13, 2015 at 04:11:05PM +0600, Sergey Zolotarev wrote: > Hello, > > Is it possible that fdisk could damage / kill a hard drive after using the "Fix partition order" command? > [...] > Both of HDDs seem unrecoverable. It's probably not the drive that's bad, it's just that your BIOS won't boot when it's attached. So boot without, THEN connect it via a USB adapter. Or via SATA. (SATA is electrically safe to hotplug, thanks to having the ground pins longer than any others, and Linux handles it just as well as USB. I never reboot to swap hard drives. I only reboot to check that my system still boots if I've done anything that might put that in doubt :P) Or set your BIOS to not even look at USB devices while booting. > could it be the result of a corrupted / bad sector in the place where the partition table is stored? A badly-written BIOS could certainly have it's boot-sector detection code get stuck in an infinite loop with unexpected inputs. There's no reason to believe the data read from the sector is anything other than what fdisk wrote to it. You can check with smartctl -a /dev/sdX once you get it connected to a booted-up computer. -- #define X(x,y) x##y Peter Cordes ; e-mail: X(peter@cor , des.ca) "The gods confound the man who first found out how to distinguish the hours! Confound him, too, who in this place set up a sundial, to cut and hack my day so wretchedly into small pieces!" -- Plautus, 200 BC -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
