Bjoern
October 29th, 2009, 12:34 PM
Hello,
some weird problems with my external hd (Western Digital My Passport, 160GB): it was formatted with NFTS, I tried to resize that partition to 30GB, rename it, and create an ext3 partition for the remaining space.
3 operations with gparted. After a while gparted said the operations where done, even though the LED on the external hd was still blinking. Since quite some time had passed, I decided to reboot the computer, hoping any pending operations would be executed before shutting down.
Since then, the hd can not be accessed (starting gparted or cfdisk just hangs, and it doesn't show up in the file system). As soon as the hd is connected, it's LED starts blinking like crazy.
I tried to overwrite the whole disk with zeros using dd, but after 8 hours quit the process - only 3GB had been written. I suspect that it was slowed down by the other process that makes the LED blink, as the computer is supposed to have an USB 2.0 port.
Any ideas on how to make the hd usable again, and what is causing the blinking? My only guess is that it could be a process that constantly tries to mount the hd and fails, as otherwise no process should have a reason to access the hd.
Thanks!
Björn
some weird problems with my external hd (Western Digital My Passport, 160GB): it was formatted with NFTS, I tried to resize that partition to 30GB, rename it, and create an ext3 partition for the remaining space.
3 operations with gparted. After a while gparted said the operations where done, even though the LED on the external hd was still blinking. Since quite some time had passed, I decided to reboot the computer, hoping any pending operations would be executed before shutting down.
Since then, the hd can not be accessed (starting gparted or cfdisk just hangs, and it doesn't show up in the file system). As soon as the hd is connected, it's LED starts blinking like crazy.
I tried to overwrite the whole disk with zeros using dd, but after 8 hours quit the process - only 3GB had been written. I suspect that it was slowed down by the other process that makes the LED blink, as the computer is supposed to have an USB 2.0 port.
Any ideas on how to make the hd usable again, and what is causing the blinking? My only guess is that it could be a process that constantly tries to mount the hd and fails, as otherwise no process should have a reason to access the hd.
Thanks!
Björn