Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
10-24-2005, 10:16 AM
|
#1
|
Member
Registered: Jun 2003
Location: Cleveburg, OH
Distribution: mostly Fedora
Posts: 154
Rep:
|
corrupt ext3 partition - need to recover
I resized my ext3 partition using Partition Commander, rebooted into Linux (FC4) and everything seemed fine... booted up right away, straight into my Desktop with no complaints.
I then resized my Windows partition, rebooted into Windows, and everything was fine.
I booted into Linux again and got the "Enter root password or press Ctrl-D" prompt, and saw errors on screen about inconsistency in my file system.
I gave it root, and ran fsck... here's what I got:
Code:
Group XX inode table at XX conflicts with some other fs block.
Relocate? yes
hundreds (thousands?) of times, then
Code:
Root inode is not a directory. Clear? yes
Error allocating 1022 contiguous block(s) in block group 1 for inode table: Could not allocate block in ext2 filesystem
Error allocating 1022 contiguous block(s) in block group 25 for inode table: Could not allocate block in ext2 filesystem
Error allocating 1022 contiguous block(s) in block group 49 for inode table: Could not allocate block in ext2 filesystem
Restarting e2fsck from the beginning...
/ contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
and the whole process repeats itself. I even tried running it with the -b option and feeding it a backup supernode with no success.
This is a brand-new system that I just migrated to, and do not have a backup (I know, I've become everything I hate). It is critical for me to recover my home directory. Does anybody have any suggestions.
When I initially had the problem, it at least started booting, after a failed repair attempt, it will not even load the grub config.
|
|
|
10-25-2005, 02:53 PM
|
#2
|
Member
Registered: Jun 2003
Location: Cleveburg, OH
Distribution: mostly Fedora
Posts: 154
Original Poster
Rep:
|
For what it´s worth, I gave up trying to fix this partition.
I mounted the hard drive in a working Windows system, and grabbed this utility:
http://www.data-recovery-software.ne...Recovery.shtml
The R-Linux utility was able to recover about 90% of what I wanted. I would highly recomend this to anybody, and best of all, it´s free!
|
|
|
10-27-2005, 12:12 AM
|
#3
|
LQ Newbie
Registered: Oct 2005
Location: Bhutan
Distribution: Debian
Posts: 4
Rep:
|
I have the same problem right now, but I can access all my data by booting up with Knoppix. I'm still working on how to restore the partition without losing all the configuration changes I've made. If I succeed, I'll let you know.
|
|
|
11-21-2005, 05:27 AM
|
#4
|
LQ Newbie
Registered: May 2005
Location: Barbados
Distribution: Suse, Knoppix, Mandrake
Posts: 8
Rep:
|
Booting from Knoppix
I tried booting from Knoppix but once I get there it sees both my WinBlows (got me into this in the first place) and my Ubunut Linux drives though it does not see the partition that actually contains the data that I am trying to recover.
HELP!!!!!
|
|
|
11-21-2005, 06:30 AM
|
#5
|
LQ Newbie
Registered: Oct 2005
Location: Bhutan
Distribution: Debian
Posts: 4
Rep:
|
I forgot to post that I'd resolved my problem. Probably the excitement. I'd misread a friend's advice and ran
tune2fs -s 0 /dev/hda3
when it was meant to be a backup option. As soon as I reverted:
tune2fs -s 1 /dev/hda3
the e2fsck command ran without problems.
gfdecaires, can you mount the drive manually? Do you know the device name (ie, which partitiion) your data was on before you ran into trouble?
|
|
|
11-21-2005, 06:47 AM
|
#6
|
LQ Newbie
Registered: May 2005
Location: Barbados
Distribution: Suse, Knoppix, Mandrake
Posts: 8
Rep:
|
corrupt ext3 partition
When I boot into a Knoppix Live CD I have to partitions on the drive hdb1 & hdb5 that are mounted but they do not have on the data, they just seem to have the Grub files on them. Runnind fdisk -l /dev/hdb shows me that there is a third partition hdb2 but I cannot mount it. When I try the mount command it says something like (are your sure you don't mean to mount an extended partition?). I don't know where to go from here.
|
|
|
07-02-2010, 12:30 AM
|
#7
|
LQ Newbie
Registered: Jun 2010
Posts: 9
Rep:
|
Serious issue
Quote:
Originally Posted by whysyn
I resized my ext3 partition using Partition Commander, rebooted into Linux (FC4) and everything seemed fine... booted up right away, straight into my Desktop with no complaints.
I then resized my Windows partition, rebooted into Windows, and everything was fine.
I booted into Linux again and got the "Enter root password or press Ctrl-D" prompt, and saw errors on screen about inconsistency in my file system.
I gave it root, and ran fsck... here's what I got:
Code:
Group XX inode table at XX conflicts with some other fs block.
Relocate? yes
hundreds (thousands?) of times, then
Code:
Root inode is not a directory. Clear? yes
Error allocating 1022 contiguous block(s) in block group 1 for inode table: Could not allocate block in ext2 filesystem
Error allocating 1022 contiguous block(s) in block group 25 for inode table: Could not allocate block in ext2 filesystem
Error allocating 1022 contiguous block(s) in block group 49 for inode table: Could not allocate block in ext2 filesystem
Restarting e2fsck from the beginning...
/ contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
and the whole process repeats itself. I even tried running it with the -b option and feeding it a backup supernode with no success.
This is a brand-new system that I just migrated to, and do not have a backup (I know, I've become everything I hate). It is critical for me to recover my home directory. Does anybody have any suggestions.
When I initially had the problem, it at least started booting, after a failed repair attempt, it will not even load the grub config.
|
Loosing data from ext3 system is a serious issue i thought journaling will help it out
|
|
0 members found this post helpful.
|
07-02-2010, 09:23 AM
|
#8
|
Moderator
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,971
|
Hi,
Why resurrect a 5 year old thread? Nothing to contribute?

|
|
|
07-02-2010, 09:30 AM
|
#9
|
LQ Veteran
Registered: Nov 2005
Location: Annapolis, MD
Distribution: Mint
Posts: 17,809
|
mariapeter12;
In addition to digging up a thread that is almost 5 years old, your comment does not seem relevant to solving the problem.
If you have a question, please start a new thread.
|
|
|
All times are GMT -5. The time now is 08:41 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|