home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!mcsun!fuug!mits!kennu
- From: kennu@mits.mdata.fi (Kenneth Falck)
- Subject: About those bad blocks
- Message-ID: <1992Jul23.002731.4126@mits.mdata.fi>
- Organization: Microdata Oy, Helsinki, Finland
- Date: Thu, 23 Jul 1992 00:27:31 GMT
- Lines: 35
-
- Sorry to bring up the subject again, but I'm just a little
- bit worried for my filesystem...
-
- The situation is: I have a "normal" MFM hard disk (Seagate 251-1),
- which I have low-level formatted with my AMI-BIOS, and at the same
- time marked the bad tracks.
-
- The question is: Should mkfs -c find these bad tracks and create
- a .badblocks file, or are they somehow automatically ignored because
- of the low-level format? It doesn't, there's no such file on my root
- partition, though I know the bad blocks exist. With MSDOS, CHKDSK
- shows that there are bad sectors. (And I did use the -c switch,
- and .badblocks does appear on corrupt floppies.)
-
- Another thing, what exactly does it mean that the kernel doesn't
- support the ext fs as a root filesystem? Is it impossible to
- have an ext fs partition configured as the rootdev in the boot
- image, or is it only impossible to boot with the image itself
- being on an ext fs?
-
- I'm getting mixed up here a bit... But I was thinking of a setup
- which would consist of two partitions: The first would be ~300k
- and contain a minix fs, with only the boot image on it. The second
- would be an ext fs, containing everything else, and the boot image
- would be configured as the second partition as the rootdev...
-
- (I want to boot without floppies.)
-
- If this makes any sense to anyone, drop me a letter or followup
- this article and enlighten me on the subject... Thanks.
-
- --
- kennu@mits.mdata.fi
- Insomnia isn't anything to lose sleep over.
-
-