ext3-fs sdb1 error loading journal Eton Georgia

Address Dalton, GA 30720
Phone (706) 264-8193
Website Link

ext3-fs sdb1 error loading journal Eton, Georgia

Offline #13 2012-02-25 12:00:14 thisoldman Member From: Pittsburgh Registered: 2009-04-25 Posts: 1,172 Re: EXT4-fs error loading journal - whats best way to recover 'photorec' in the 'testdisk' package will recover deleted The reported error was: mount: wrong fs tpe, bad option, bad superblock on /dev/hda2 or too many mounted file systems I know there is a thread on it but I didn't pooyaplusJuly 21st, 2008, 07:54 AMHi, I appreciate your help. Lets see what happens, I do not believe that can make so much trouble but just a precaution I have in mind.

Email check failed, please try again Sorry, your blog cannot share posts by email. dmesg complains, "journal_bmap: journal block not found at offset 0 on sdb1" which is consistent with this guess. The next statement, should say it all about where im at in the whole process now "Not enough random bytes available, Give the OS a chance to collect some more entropy!" Offline #7 2012-02-24 17:58:21 wolfdogg Member From: Portland, OR, USA Registered: 2011-05-21 Posts: 527 Re: EXT4-fs error loading journal - whats best way to recover the drive is a WD3200KSThe problems

All rights reserved. I figure its a good chance to reorder the files and get them contingent. To check filesystem # fsck.ext3 -b 32768 /dev/sda2 To mount filesystem with alternative superblock: # mount sb={alternative-superblock} /dev/device /mnt # mount sb=32768 /dev/sdb2 /mnt and Try to browse files. Correct me if I am wrong.

after rebooting into live cd and running the fsck /dev/sda3 and it finished and reported back clean, now im noticing the HARD DRIVE LIGHT IS ON AGAIN, whats going on? When intentionally stimulate the problem will not occur the incident. Here is the fstab: # /etc/fstab: static file system information. # # proc /proc proc defaults 0 0 # /dev/sda9 UUID=d271ff7f-ed90-4a84-9d85-92771e89054b / ext3 and how to disable it if its not in my daemons list in rc.conf?EDIT:ok, using -a switch iotop -athen pressing o when runningunder io, i have jbd2/sda3-8 (my home)crond -S -l

i was doing some web dev and i dont want to lose this work. You're now being signed in. Right? This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant.

pooyaplusJuly 19th, 2008, 12:19 PMThanks, I will check that and let you know. CentOS The Community ENTerprise Operating System Skip to content Search Advanced search Quick links Unanswered posts Active topics Search The team FAQ Login Register Board index CentOS 5 CentOS 5 - The only difference between ext2 and ext3 is the lack of a journal in ext2. Also, it prompted me to run fsck without -a or -p option and I am executing it now.Please let me know if this is going to be an issue for the

Thank you very much indeed. Thanks that worked.:guitar: But there is one more thing. I dont really feel like logging into gnome, no telling what will happen. Thanks.

Can I keep the ext2 (!) partition and have a clean new install of ubuntu on the rest of the hard space? A better way to evaluate a certain determinant Why are unsigned numbers implemented? Nice job! Smart's reliability for prediction may not be good but it has been reliable for me when used to confirm serious problems.

May be this process prevent e2fsck? it probably is ext3 so there is nothing to fix there. Digital Diversity What are Imperial officers wearing here? So we put another drive with a working OS and from there we try to mount the partitions in the old drive.

i couldnt log remtoely into ssh, it did answer and let me atleast get to the username, but the password prompt wouldnt come up. Commit interval 5 seconds EXT3-fs warning (device sdc14): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure EXT3-fs warning (device sdc14): ext3_clear_journal_err: Marking fs in need of filesystem check. I'll have to remember that in the future. 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.

See "man e2fsck". So it looks like i went full circle. Since the journal is corrupt, we will remove it: tune2fs -O ^has_journal /dev/sdc2 Now complete an fsck of the device. Thanks again for the help.:KS pooyaplusJuly 19th, 2008, 12:25 PMsda9 is your root partition.

What did you try already? in some cases userul info is found in syslog - try dmesg | tail or sonow im dropped to an emergency shell# dmesg | tailoutputs almost same errorDescriptor sense data with When I try to mount that one, I see these errors with dmesg: sd 0:0:1:0: Unhandled sense code sd 0:0:1:0: SCSI error: return code = 0x08100002 Result: hostbyte=invalid driverbyte=DRIVER_SENSE,SUGGEST_OK sdb: Current: However, it's a good idea to make sdb1 an ext3 partition.

Or did you clone/make an image of the whole partition and copy it to sdb1? Are you new to LinuxQuestions.org? Please note: the fact that an Attribute is of type 'Pre-fail' does not mean that your disk is about to fail! And add step 1.5: copy this to the third drive so you can mess up the first copy and restore it from the second copy.

JBD2: Failed to read block at offset 1628 JBD2: recovery failed EXT4-fs (sda3): error loading journalit appears i jacked it up when i reset it during file operations.where to go from