ext3-fs md0 error unable to read superblock Ericson Nebraska

Address 1523 M St Ste 104, Ord, NE 68862
Phone (308) 728-3410
Website Link
Hours

ext3-fs md0 error unable to read superblock Ericson, Nebraska

Please help!!! IF you are still with me, could you look over my RAID notes. any guidance would be much appreciated. Not the answer you're looking for?

It was nicely explained and worked in few minutes. SEARCH FIRST... In device.map (hd0) is aligned to sda1. I have installed a hard disk (SATA, 7.2rpm) on this machine that I removed from another Dell PowerEdge T100 server with Dual-Core Xeon CPU that was running software RAID 1.Now when

Yay! 6 evidex on July 7, 2010 said: Glad to hear that I helped Fabricio😀 7 Swamprat on July 11, 2010 said: Thank you very much for your help. for 2 weeks to try to solve the problem of my notebook! Created mount point, mounted md0. Smartmontools reports them healty, and i dont see any "failed" or errors inhere.When i manually try to mount i do get a complaint about a superblok :-(((( [[email protected] etc]# mount /dev/md0

Testdisk can be found on the Parted Magic disk, the link to which is above. My first question is whether your method above will work for me despite the empty directory structure having been written? For your information: I made a similar post in the General forums. ToniT View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by ToniT 08-20-2004, 01:12 PM #5 ToniT Senior Member Registered: Oct 2003 Location:

How to solve the old 'gun on a spaceship' problem? There is some problem with mdrun script. Or after booting at the terminal command line just do: Code: dmesg | grep raid or to paginate the entire log Code: dmesg | more Reply With Quote 25-Sep-2008,12:19 #9 Wavester1 Thanx! 18 evidex on October 28, 2010 said: Glad to be of service🙂 19 Pointer Men's Basketball on October 30, 2010 said: Maybe you should edit the page subject title Repair

post#8:"...In /var/log/dmesg I find a (disturbing) line "EXT3-fs: unable to read superblock". When I formatted md0 to ext3 (see step 7), it wrote all superblocks nicely and started the fs without problems.... Last edited by BigF (2013-07-13 02:40:11) Offline #2 2013-06-10 09:00:05 scjet Member Registered: 2010-12-01 Posts: 1,461 Re: BIG problem ..... [SOLVED - kinda -] It sounds like Mr.G pointed you in Red Hat nash version 5.1.19.6 starting insmod: error inserting '/lib/raid456.ko': -1 File exists md: md2: raid array is not clean -- starting background reconstruction raid5: cannot start dirty degraded array for

However, the output of fsck.ext4 was different: [email protected]:~$ sudo fsck.ext4 -v /dev/sdc1 e2fsck 1.41.11 (14-Mar-2010) fsck.ext4: Attempt to read block from filesystem resulted in short read while trying to open /dev/sdc1 I was already blaming Linux but forgot it was indeed a bad HD which I had problems with before sadly… I think I will have a lot of data loss. You will have to register before you can post in the forums. (Be aware the forums do not accept user names with a dash "-") Also, logging in lets you avoid Not the answer you're looking for?

Main Menu LQ Calendar LQ Rules LQ Sitemap Site FAQ View New Posts View Latest Posts Zero Reply Threads LQ Wiki Most Wanted Jeremy's Blog Report LQ Bug Syndicate Latest Thanks! 44 dantux on March 29, 2011 said: Thanks! However, after rebooting, the same boot-up problem (hanging for hours) persists. Do you get /dev/md0 manually running by using mdstat with --assemble parameter?

Is your filesystem type claimed in /etc/fstab correct? There are so many different causes for filesystem corruption that cases can be very individual. Please read the search suggestion thread in JL Ideas Reply With Quote 09-24-2002,12:51 PM #3 ziidle View Profile View Forum Posts Registered User Join Date Sep 2002 Posts 8 okay, I've I think I could do that with e2fsck -b 23887872 /dev/md[01] do you recommend giving this a shot?

The time now is 03:39. © 2015 SUSE, All Rights Reserved. There are no other words to say thank you. Dave DaveJLMarch 9th, 2010, 05:47 AMI'm now in Recovery Mode. For example if you have a memory card reader attached to the system these normally get assigned a device name after hard drives, but it you wait until after the boot

What's the output of mdadm --detail --scan? –frostschutz Aug 2 '14 at 18:13 1 Also those md12[567] you have are on device mapper devices. I could even edit /etc/fstab and /boot/grub/grub.conf because I tried different options to make it work but no luck so far. yes According to the instructions I'm supposed to reboot and see if the partition can be correctly read. Modifying the kernel line in grub and changing the root=/dev/md1 to root=/dev/md0 solved that problem temporarily and the server booted.

Any idea? 91 evidex on January 24, 2012 said: You need to change xxx to your own device name. 92 braikar on January 24, 2012 said: LoL, obviously I knew that How do I explain that this is a terrible idea? NOTE: if you try to use ‘top' to watch and see if fsck is doing anything you will not see the process counter advance, so it appears as though fsck is With this tutorial (very good indeed) I managed to get the folder lost+found really full of my files but it starts with # and I can not do anytinh g with

so lets ignore windows, and see if we can get linux working again.. To be honest, it sounds like a problem with the RAID, rather than the actual filesystem. THANK YOU!!!!! 54 Gaurang on June 20, 2011 said: Thank you very much. denniz View Public Profile View LQ Blog View Review Entries View HCL Entries Visit denniz's homepage!

That's it. Top pschaff Retired Moderator Posts: 18276 Joined: 2006/12/13 20:15:34 Location: Tidewater, Virginia, North America Contact: Contact pschaff Website [SOLVED] EXT3-fs: unable to read superblock Quote Postby pschaff » 2010/09/30 20:20:29 I i love you!!😀 102 evidex on May 25, 2012 said: Glad to hear it helped🙂 103 Olivier on June 4, 2012 said: Hey, thanks a lot, I can now access my If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck

Register. 09-27-2010 #1 TiffDiff View Profile View Forum Posts Private Message View Articles Just Joined!