valleytech
asked on
mount ext3 linux on ubuntu
HI
one of my linux system went dead :(
I ended up with using another ubuntu system, mount linux-based disks to extract all data.
On ubuntu system, I did "mount /dev/sdb3 /linux" .
Then I got error of corrupted file system, which lead me to use "fsck /dev/sdb3"
After all the processes are completed, I did "cd /linux" and "ls" (after remount /dev/sdb3 to /linux), what i saw was horrifying, no familiar folders are there ;(
I only see: lost+founds and a whole bunch of strange file , named core.???? (where ???? = number)
Is there anyway for me to get back the data?
I'm so thankful for your help
one of my linux system went dead :(
I ended up with using another ubuntu system, mount linux-based disks to extract all data.
On ubuntu system, I did "mount /dev/sdb3 /linux" .
Then I got error of corrupted file system, which lead me to use "fsck /dev/sdb3"
After all the processes are completed, I did "cd /linux" and "ls" (after remount /dev/sdb3 to /linux), what i saw was horrifying, no familiar folders are there ;(
I only see: lost+founds and a whole bunch of strange file , named core.???? (where ???? = number)
Is there anyway for me to get back the data?
I'm so thankful for your help
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have done "mount" many times before without speciying ext3 or ext2.
If that causes problem, is there any away to reverse? ;(
If that causes problem, is there any away to reverse? ;(
ASKER
under pressure, i might have caused this.
I ran "fsck /dev/sdb3" without specifying ext3 or ext2 and fsck assumes ext2. The result is more catastrophic.
I'm not experience at this level, can you please help?
Many thanks!!!
I ran "fsck /dev/sdb3" without specifying ext3 or ext2 and fsck assumes ext2. The result is more catastrophic.
I'm not experience at this level, can you please help?
Many thanks!!!
If you already ran the fsck under ext2 rather than ext3, the data is most likely corrupted and irretrievable by normal means.
ASKER
then the system showed error and force me using fsck, and i end up running "fsck /dev/sdb3"
after all that, I did "mount /dev/sdb3 /linux" again and list files/folders, I saw nothing but weird contents :(