On Monday 13 April 2015, Sergey Zolotarev wrote: > Hello, > > Is it possible that fdisk could damage / kill a hard drive after > using the "Fix partition order" command? I remember there was such bug in past. Which version are you using? $ fdisk -V > It seems that that is > exactly what happened to me two times already, with two different > hard drives. > > First time I thought that it was my hard drive's fault as it was > pretty old and cheap, So I bought a new not-so-cheap one and was > quite happy with until today, when I used that evil command again! > > Both of HDDs seem unrecoverable. When either is plugged BIOS gets > stuck at initial screen (can't even enter setup). Using a USB adapter > didn't help either... I'm not an expert in hard drives, but could it > be the result of a corrupted / bad sector in the place where the > partition table is stored? First I would try to boot via rescue CD or similar. Then check how the partitiontable looks now (fdisk -l) and try to mout partitions manually. If you are missing partitions or if you just can't mount them then you may try to repair/recover the partition table. cu, Rudi -- 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
