MandrivaThis Forum is for the discussion of Mandriva (Mandrake) Linux.
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 had a couple of powercuts while i was working in mdk 9.1 and when i restart mdk, at the bootup it says "press Y within 1 second to start filesystem check", but 1 second is not long enough, and when i reboot it does not say it as i i have then shutdown the machine properly, so is there any way of either making that time longer or to make it do the check automatically when mdk is not properly shutdown?
Thanks
Christian
Last edited by firestomper41; 02-17-2004 at 08:24 AM.
Distribution: RH 6.2, Gen2, Knoppix,arch, bodhi, studio, suse, mint
Posts: 3,304
Rep:
you can boot with the install cd and check the hard drive from there.
you might be using a filesystem that doesn't need to be checked, like
reiser or ext3.
Why does linux default to not checking the file system?
(It actually gives you 5 seconds, but you were not looking for
the first 4).
The assertion was that file systems like ext3 and reiser don't need
to be checked. Well, I lost quite a all of a ext3 file system after
a reboot that did not check the system. Any timeout is too short
as you cannot be sure of being around during a power failure.
Is there some way of turning off this "feature"? I made one
attempt to find out, but did not invest enough time.
In the meantime, when I rebuilt my system, I partitioned off
a separate root so I am less likely to loose everything.
Distribution: RH 6.2, Gen2, Knoppix,arch, bodhi, studio, suse, mint
Posts: 3,304
Rep:
i gave some bad info. it's the last number on the line that means whether to check and in what order. when reiserfs was new, i did a bunch of resets in the middle of writes to see if the filesystem would get corrupted, and it didn't. i think you just had some bad luck, but if i had ext3 get corrupted on my machine, i wouldn't use it again. especially since there's reiserfs, jfs, and xfs too.
The sixth field, (fs_passno), is used by the fsck(8) pro_
gram to determine the order in which filesystem checks are
done at reboot time. The root filesystem should be speci_
fied with a fs_passno of 1, and other filesystems should
have a fs_passno of 2. Filesystems within a drive will be
checked sequentially, but filesystems on different drives
will be checked at the same time to utilize parallelism
available in the hardware. If the sixth field is not pre_
sent or zero, a value of zero is returned and fsck will
assume that the filesystem does not need to be checked.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.