Last night the fuse box tripped and everything shut off. When I booted up my PC, I noticed that my 1TbHD was empty, it was full before, what could have happened?
It’s still full but I cant see any files. I’ve even tried ‘CTRL’+ H and nothing shows up
I’ve never come across anyone that has more file system issues than you.
Have you tried running fsck on the partition ?
and if you have an unstable power supply, it may be best to add the “errors=remount-ro” option to your additional drives in fstab.
Well, it keeps you on your toes lol
Do I just type fsck in terminal, I don’t have to specify a drive?
How do I type all this, I’m not sure?
Boot to a LiveCD, as you shouldn’t run fsck on a mounted partition…
Then:
sudo fdisk -l
will give you your drive/partition layout.
Then run fsck on the desired drive/partition with:
sudo fsck /dev/sdXY
Where -
X = the drive
Y = the partition
EXAMPLE:-
sudo fsck /dev/sdb1
The above is an EXAMPLE, not the exact command you want.
sudo fdisk -l
Gave me;
Disk /dev/sda: 251.0 GB, 251000193024 bytes
255 heads, 63 sectors/track, 30515 cylinders, total 490234752 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00044d2a
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 484474879 242236416 83 Linux
/dev/sda2 484474880 490233855 2879488 82 Linux swap / Solaris
Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0009b408
Device Boot Start End Blocks Id System
/dev/sdb1 63 3907024064 1953512001 83 Linux
Disk /dev/sdc: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000b090e
Device Boot Start End Blocks Id System
/dev/sdc1 63 488392064 244196001 83 Linux
ubuntu@ubuntu:~$
I ran
sudo fsck /dev/sdc1
and got;
ubuntu@ubuntu:~$ sudo fsck /dev/sdc1
fsck from util-linux 2.20.1
e2fsck 1.42 (29-Nov-2011)
Drive1: clean, 2284/15269888 files, 4841338/61049000 blocks
ubuntu@ubuntu:~$
Non of those drives are 1TB ???
Well, I’ve only got 4 drives connected…
2 * 250 Gb
1 * 1Tb
1 * 2Tb
Whats happened?
I rebooted with just the 1Tb Hd connected and got this;
ubuntu@ubuntu:~$ sudo fdisk -l
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0002506b
Device Boot Start End Blocks Id System
/dev/sda1 63 1953520064 976760001 83 Linux
ubuntu@ubuntu:~$ sudo fsck /dev/sdc1a
fsck from util-linux 2.20.1
e2fsck 1.42 (29-Nov-2011)
fsck.ext2: No such file or directory while trying to open /dev/sdc1a
Possibly non-existent device?
ubuntu@ubuntu:~$ sudo fsck /dev/sda1
fsck from util-linux 2.20.1
e2fsck 1.42 (29-Nov-2011)
Drive2 has been mounted 44 times without being checked, check forced.
Pass 1: Checking inodes, blocks, and sizes
Error reading block 147849248 (Attempt to read block from filesystem resulted in short read) while getting next inode from scan. Ignore error? yes
Force rewrite? no
Error reading block 147849249 (Attempt to read block from filesystem resulted in short read) while getting next inode from scan. Ignore error?
I’ve stopped for now to post the results to you.
Dude … you’re asking (again) for me to make decisions with your data for you.
What is it telling me?
Thats WHY I posted it.
OK … as I’ve said before, “I’m not a data recovery expert”, so I’ll drop out of this topic.
Try running fsck again and see if it halts at the same block;
Error reading block 147849248
I’m trying to find some more information on recovering with this error but be prepared to replace the hard drive.
Re-run fsck, if it asks to force rewrite, do it. Though it sounds like your hard-drive have went up in a puff of smoke.
Have you got a big enough power supply for all the hard-drives? You should get a hold of a volt meter and test voltages, I’m thinking perhaps your power supply has been damaged from the power surge and may need replacing / upgraded.
If you have that much equipment on all the time it may also be a good idea to invest in a Uninterruptible Power Supply (UPS).
If I had a penny for everytime mine has saved my life… I’d have 2 pence!! But it’s worth it!
I wonder if they do Uninterruptible Power Extension sockets…
I decided not to mess with it as the 500Gb Hd that went faulty was sent for recovery, it died sortly after, luckily, the daar was recovered. I think about 99.9% was recovered. I didn’t need the OS and as far as I can see, all of what I wanted has been recovered. I am still sorting it out and having to rename over 1 million files, audio, video and picture.
The PSU I have is a 650w.
I have one of those surge protectors from B&Q.