Best of the Newsgroups: OSR5 fsck

If this isn't exactly what you wanted, please try our Search (there's a LOT of techy and non-techy stuff here about Linux, Unix, Mac OS X and just computers in general!):

From: Bela Lubkin <belal@sco.com>
Subject: Re: fsck on sco 5.0.5 open server. where is it?
Date: Tue, 1 Jul 2003 06:25:00 GMT
References: <3060687.1057028670@dbforums.com> 

romppast wrote:

> Im new to SCO server family and recently just encountered problem with
> my SCO 5.0.5 Openserver as it hangs-up while booting with the message of
> **Root File System Modified** followed by **Remounted Root File System**
> then stops from there. This happened after the server was turned-off
> accidentally by my baby :) while i was doing a vi on resolv.conf.
>
> The bad thing is, i bought the server second hand without installer
> disks, boot/root floppies and manual to look up to so im just relying on
> the internet in finding cure to this problem.
> 
> I check on google and found infos on how to boot the system using
> oss604a.boot and from there mount /dev/hd0root /mnt. However, in most of
> the advices on threads, fsck is required but cant call it from the /etc
> and not even in the mounted /mnt/bin as it is not there. Im wondering
> why didnt they put this fsck on this boot disk...

If you're getting those messages, the system is running fsck for you, so
it's certainly present.  I think you would only get those messages about
the root filesystem after a question like "Root filesystem is dirty, OK
to check it?".  One thing you can do is: say no.  Then go to single-user
mode and run:

  fsck -o full /dev/root

and see how it goes.

Using the boot floppy, you would need to do this:

  mount /dev/hd0root /mnt
  chroot /mnt /bin/sh
  fsck -o full /dev/root

But I think this won't work because of the way root is mounted.  fsck is
only willing to check a mounted filesystem if it's the root filesystem
(according to the booted kernel).  When booted from a floppy, the floppy
is the root.  You _might_ be able to:

  mount -r /dev/hd0root /mnt
  chroot /mnt /bin/sh
  fsck -o full /dev/root

Doing it from single-user mode is probably much easier.

If you're still stuck, post the full messages you're getting during the
failed bootup.

>Bela<

Jump to Comments

Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.