Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
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.
I have a system running FC5.
Over the weekend the system froze.
I rebooted and during the boot O receive the message
Error 16 Inconsistent File System Structure
I have booted with a rescue disk and run fsck, which claims all is well.
I search linuxquestions.org and found a few things tpo try like reinstalling the grub, but nothing has worked.
Is there anything I can do to fix this boot problem?
Disk /dev/sda: 18.2 GB, 18210036736 bytes
255 heads, 63 sectors/track, 2213 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 19 152586 83 Linux
/dev/sda2 20 656 5116702+ 82 Linux swap / Solaris
/dev/sda3 657 2213 12506602+ 83 Linux
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,588
Rep:
Okay, that means GRUB expects your "/" on the first partition (and quite small). Is that so? Did you change something in "root=LABEL=/1" (looks funny to me but I don't use labels much)?
You didn't tell with what file system you formatted the drive...
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,588
Rep:
Do you still have the install CDs? You might just pop in the first one, usually the distros detect an existing OS and offer to repair any damage, including damage to the boot loader.
"fdisk" told you the file system type: 82 (linux) meaning ext2 or ext3. Hum. Out of my depth here...
Well, the GRUB manual says:
"16 : Inconsistent filesystem structure
This error is returned by the filesystem code to denote an internal error caused by the sanity checks of the filesystem structure on disk not matching what it expects. This is usually caused by a corrupt filesystem or bugs in the code handling it in GRUB."
I am facing the same issue for RHEL5 and i am not able to switch to Maintenance mode also.
My server is not booting. Can anyone suggest, what to do in this case.
You have posted to a thread which has been inactive almost nine years.
To get the best exposure for your question and attract replies from those with most knowledge of your problem, please open your own thread with a complete description of your specific system and the problem you are experiencing.
For guidance in posting your question please see the Site FAQ, and in particular this page.
the very dead and very unsupported Fedora core5
is NOT the same as the soon to be End Of Life RHEL5.11
( you are using 5.11 !!! it is the ONLY version of 5 still supported by redhat)
and seeing as this is RHEL5 you do have the REQUIRED support contract ! right ?
contact redhat customer service
as to booting
just use the normal everyday
SINGLE USER boot
put a blank space and a 1 at the end of the grub0.98 kernel line
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.