Another way is to use a livecd to run fsck on the drive.
fsck -y -c /dev/locationofdrivePartition
-c will also run a simple read-test on sectors of the drive, in case there are
'bad-sectors' - This will take a wee while. -y will just answer yes to any and
all questions (which may be
Another way is to use a livecd to run fsck on the drive.
Errr - I wouldn't.
Once a drive has started dropping data like this, it is likely to keep on
doing so. The more operations you perform, the more likely you are to drop
stuff you want.
This is why I suggest getting as much data off the
Depends how the error occurred.
Clone the data than run a fsck -cc it will count how many fubars it detects.
I have drives 8 years + old that are still going strong, with a couple with
patched out areas from when a computer had the power removed abruptly. No more
pending failures or errors
Hi all
Funnily enough, I was reading about the prolonged hard drive price hike
yesterday and hey presto, looks like I have my own drive failure today.
Can anyone suggest if the following is terminal?
I got the Ubuntu Target filesystem doesn't have /sbin/init and (not
surprisingly) no GUI.
1) Is that it for the drive
Yes.
2) Is that it for the fs but the drive can be reused (i.e. a reinstall)?
Probably not.
The error you posted is a failure to read the journal. That means you
might have lost any recent writes, but the data may be largely preserved -
so far.
What I do in
