Code-tags --- Boot-Repair --- Grub2 wiki & Grub2 Basics --- RootSudo --- Wireless-Info --- SolvedThreads --- System-Info-Script
The command: "sudo fsck /dev/sdb1" seemed to work. Now I have a list with tthe folders followed by "Start does point to root directory. Deleting dir."
It finishes by saying:
Reclaimed 87655457 unused clusters (297765443344.. bytes).
Free cluster summary wrong (587665 vs. really 9560941)
1) correct
2) don't correct
?
Which option should I choose?
Once you press 1) Correct. You get 270+gigs free. Once you pres 2) Don't correct. You get nothing.
In short, you lost your files, but there is a way to recover what is left of them.
You have to learn what partition table it is using, go to System -> Administration -> Disk Utility and find your external HDD, note what it says under Partitioning (If Master Boot Record then it's Intel)
Install a program called TestDisk and PhotoRec
Now you will have to restore the files using photorec, well, what is left of them.Code:sudo apt-get install testdisk
Proceed -> Intel -> Pick the 1st partition -> Pick whatever FS it is (Usually FAT, also check using Disk Utility), Free (Or Whole if you did not select to reclaim the 270+ gigs free) then find a directory you will save the files (Somewhere NOT on your external HDD, another external HDD or your Internal HDD), if you don't have enough space, it will fill it up then ask you to select a new place to save the files. Once you find a good place, press Y.Code:sudo photorec /dev/sdb
Last edited by Lisiano; September 18th, 2011 at 01:19 PM.
Originally Posted by Linus Torvalds
That is not the news I was hoping for...
I will give it a try. I'll first need to find a new storage place...
Well, sorry for your loss, I guess. Also I can't stress enough how you MUST NOT WRITE ANYTHING to your external HDD. If you do so, some or all files will be overwritten, until then label it as a "Do NOT use under ANY circumstances" or something.
Originally Posted by Linus Torvalds
This is indeed a fat drive, as shown by the output of your blkid command. Unfortunately, while the data is still on your disk, the "housekeeping" data are lost.
Use vfat only for USB sticks where only little and temporary data is stored. For storage media, use modern, more resilient file systems such as ext3 or ext4 on linux.
Unfortunatelly, you indeed have a problem if you do not have a backup of these data. Trying to rescue some is your only bet, and there, I second the hint of Lisiano to attempt photorec.
Maybe unnecessary to say, but you always need a backup of data for which you care. Now, it was an accidental disconnection at the wrong moment, but also hardware failure may at any time threaten your data. So even with a better file system, you still need the backup.
ntfs?
Since when Linux has native NTFS support?
Originally Posted by Linus Torvalds
Solid read/write support came with ntfs-3g about three years ago. The previous ntfs driver was read-only.
@OP
If, as we suspect, the external drive has a DOS or NTFS filesystem, you really need to connect the drive to a Windows machine and run "chkdsk" against it. While the ntfsfix program that comes the ntfsprogs suite can fix some problems, I really only trust Microsoft's utilities with a broken NTFS filesystem.
Last edited by SeijiSensei; September 18th, 2011 at 08:27 PM.
Bookmarks