- Joined
- Nov 25, 2008
Hey guys, so I've got one of those nasty seagate 3tb drives. You know, the ones that die? Well, it's died. Kinda. It had a few read errors on it but did fine for a few months and then started choking. I didn't have anything to move the data to so now it's in a bit of a bad state. In fact, it's pretty difficult to get it to detect on start up.
Now, it seems like there is a bad sector in either the MBR or the partition table. If the system attempts to boot from the drive (there was never an OS installed), it will hit TLER and attempt to read something. You can't hear the drive, but if you feel it there is a faint "bum-bum" sensation about once a second of the heads moving around. If this happens on boot, it's impossible to get the drive to detect since it will essentially hang for a minute and a half or so and the BIOS will give up on it, but if I go straight to a USB and get it to ignore the drive, then it'll show up as a physical drive in linux. I believe when gparted attempts to read partitions it causes the same TLER error, but I didn't feel the drive last time I tried. It did give out data errors on reading /dev/sda and /dev/sda1, I'm not sure if reading for a sda1 is default or if it did grab that there was a partition there. Gparted obviously can't get anything substantial from it either way.
Now, the thing I can think that would explain what is wrong and possibly allow me to recover data is if the MBR and partition tables are bad but the data is still there, so in theory I need something that will read the raw data from the drive and piece this back together into actual data, and also play well with the 90 second TLER if and when it hits it. I suspect there are bad sectors in the drive that aren't in the MBR/Partition table and it's gonna hit those at one point or another.
What's the best way to go about trying to recover data from this, if it's recoverable at all? The only program I know about that can do stuff like this would be ddrescue, and I'm not that well versed in it.
Now, it seems like there is a bad sector in either the MBR or the partition table. If the system attempts to boot from the drive (there was never an OS installed), it will hit TLER and attempt to read something. You can't hear the drive, but if you feel it there is a faint "bum-bum" sensation about once a second of the heads moving around. If this happens on boot, it's impossible to get the drive to detect since it will essentially hang for a minute and a half or so and the BIOS will give up on it, but if I go straight to a USB and get it to ignore the drive, then it'll show up as a physical drive in linux. I believe when gparted attempts to read partitions it causes the same TLER error, but I didn't feel the drive last time I tried. It did give out data errors on reading /dev/sda and /dev/sda1, I'm not sure if reading for a sda1 is default or if it did grab that there was a partition there. Gparted obviously can't get anything substantial from it either way.
Now, the thing I can think that would explain what is wrong and possibly allow me to recover data is if the MBR and partition tables are bad but the data is still there, so in theory I need something that will read the raw data from the drive and piece this back together into actual data, and also play well with the 90 second TLER if and when it hits it. I suspect there are bad sectors in the drive that aren't in the MBR/Partition table and it's gonna hit those at one point or another.
What's the best way to go about trying to recover data from this, if it's recoverable at all? The only program I know about that can do stuff like this would be ddrescue, and I'm not that well versed in it.