Home > Unable To > Centos Error Mounting /dev/root On /sysroot As Ext3

Centos Error Mounting /dev/root On /sysroot As Ext3

Contents

Find More Posts by AuroraZero 10-11-2011, 08:35 AM #3 Promo_Sam LQ Newbie Registered: Oct 2011 Location: Orlando Distribution: RHEL Posts: 6 Original Poster Rep: I'm using RHEL 5.2 (64 I even copied the /etc/fstab from another working RHEL5 system and I still get the same error as above. LinuxQuestions.org > Forums > Linux Forums > Linux - Server [SOLVED] Server booting issues(EXT3-fs: unable to read superblock 'etc') User Name Remember Me? Kernel 2.6.18-274.3.1.el5 Thanks again!

From: Ljubomir Ljubojevic ! Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started Or, should I just start creating a new server to replace this one if you think this is irrepairable? Where is it getting the "defaultsi" option from?

Ext3 Fs Unable To Read Superblock Raid

The time now is 02:23 PM. Find More Posts by AuroraZero 10-12-2011, 06:38 PM #11 Promo_Sam LQ Newbie Registered: Oct 2011 Location: Orlando Distribution: RHEL Posts: 6 Original Poster Rep: Thank you for your help Edit: And my kernel is 2.6.18-274. AuroraZero View Public Profile View LQ Blog View Review Entries View HCL Entries Visit AuroraZero's homepage!

Top majun Posts: 137 Joined: 2010/03/11 11:33:59 Re: EXT3-fs: unable to read superblock Quote Postby majun » 2010/09/30 21:23:28 Funny... the latter is acompressed filesystem image that the bootloader just maps into memory,and it holds a number of kernel modules and helper programs for thekernel you are booting. Let me know how it goes, I actually removed all atime settings and went back to the defaults, remade my initrd and got a clean boot. -cluge cluge View Public Profile Like I said before, super noob here.

Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting I did have to clean up the new grub.conf, but I got that from the /boot/grub/grub.conf file in the SuSE partition. asked 3 years ago viewed 917 times active 3 years ago Blog International salaries at Stack Overflow Related 1Trying to pass NIC to domU causes kernel panic1How should I capture Linux AuroraZero View Public Profile View LQ Blog View Review Entries View HCL Entries Visit AuroraZero's homepage!

What kernel is it using? Registration is quick, simple and absolutely free. The machine is using the /boot on /dev/sda3 to boot the machine and when it tries to mount on that drive it can't because you are using it to boot off. Find More Posts by AuroraZero 10-11-2011, 12:29 PM #5 Promo_Sam LQ Newbie Registered: Oct 2011 Location: Orlando Distribution: RHEL Posts: 6 Original Poster Rep: I most certainly can.

Unable To Read Superblock Ext3

For those of you who were in the same situation as I was.... I was thinking it might be hidden in the initrd file but I searched those and it didn't show: strings /boot/initrd* | grep -i norelatime gets no hits BTW, "norelatime" is Ext3 Fs Unable To Read Superblock Raid my mdadm.conf is: Code: DEVICE partitions MAILADDR root ARRAY /dev/md0 super-minor=0 Last edited by Goleteral; 08-17-2010 at 03:41 AM. Unable To Read Superblock Ext4 You should probably create a new server, restore from your last known good backup, and carry on.

If you'd like to contribute content, let us know. ata1.00: cmd c8/00:00:3d:19:86/00:00:00:00:00/e0 tag 0 dma 131072 in ata1.00: status: { DRDY DF ERR } ata1.00: error: { ABRT } That's pretty much the swan song of a dying SATA disk. Date Index Thread: Prev Next Thread Index On 04/12/07 00:41, t35t0r wrote: I ran a kickstart and the system booted up fine for the first time. That disk has died.

Register If you are a new customer, register now for access to product evaluations and purchasing capabilities. It definitely isn't in /etc/fstab or i'm hallucinating and vim isn't working properly because /i didn't return anything in the file! Additional info: * On this system, http://www.smolts.org/show?uuid=pub_c03a1eea-f904-4743-bb2c-dd40aa32b12e I've also experienced theses bugs: https://bugzilla.redhat.com/show_bug.cgi?id=481595 https://bugzilla.redhat.com/show_bug.cgi?id=475283 Initrd images are significantly smaller than the previous ones: [root@kwizatz boot]# export LANG=C; ls -alh initrd-2.6.2* root I rebooted but I still get the error above.

Join our community today! Kernel panic: no init found. I am not the most familiar with the LVM config but I would assume you could change the mount point for /sysroot from someplace within its config options.

Almost like the hard drive have gotten corrupted some how.Can you look at your fstab?

Please visit this page to clear all LQ-related cookies. Product Security Center Security Updates Security Advisories Red Hat CVE Database Security Labs Keep your systems secure with Red Hat's specialized responses for high-priority security vulnerabilities. Why would it cause the kernel to not load? see the error message during the boot process Actual results: boot failed.

Where is it getting the "defaultsi" option from? Since this thread is several years old I'm going to close it. Join Us! Also cleaned out /etc/mtab but it didn't help.

It needed the new initrd file to be built after the fstab edit thanks marko View Public Profile Find all posts by marko #6 16th April 2009, 11:11 PM I'll post my solution. I'm very very new when it comes to linux but I'm handy with google so normally I can weasel my way out of any issue I run into. Last edited by Promo_Sam; 10-11-2011 at 08:41 AM.

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 Comment 2 Michal Schmidt 2009-01-27 10:02:23 EST In could also be a bug in mkinitrd if it was updated recently. the latter is a compressed filesystem image that the bootloader just maps into memory, and it holds a number of kernel modules and helper programs for the kernel you are booting. Linville 2009-01-27 13:12:38 EST FWIW, I'm seeing similar issues with >= 2.6.28 upstream kernels on F10 userland, especially recent wireless-testing (2.6.29-rc2 based)...

Tenant paid rent in cash and it was stolen from a mailbox.