Date: Sat, 13 Dec 1997 10:49:02 +1030 From: Mike Smith <mike@smith.net.au> To: "Josu Jos Souza Jr." <josue@compacto.nexos.com.br> Cc: Bruce Evans <bde@zeta.org.au>, freebsd-hardware@freebsd.org Subject: Re: Bad144 Message-ID: <199712130019.KAA00479@word.smith.net.au> In-Reply-To: Your message of "Fri, 12 Dec 1997 09:08:54 -0200." <Pine.BSF.3.96.971212085103.3489B-100000@compacto.nexos.com.br>
next in thread | previous in thread | raw e-mail | index | archive | help
> > bad144 is normally only used for old MFM and ESDI drives, since modern > > drives remap bad blocks themself so that they appear to haeve 0 bad > > blocks. Perhaps the slice size is wrong. > > Is it safe to install the FreeBSD without using bad144 to scan the drive? > What I mean is: does FreeBSD 2.2.5 uses ATA's bios capability of mapping > bad blocks? There is no "ATA's bios capability of mapping bad blocks", so FreeBSD could not possibly use it. The firmware on most decent modern disks of all sorts (even the Zip, if you want to believe it) will perform automatic reallocation of bad disk areas. If you have a disk manufactured in the last 4-5 years that is generating media errors it is because it has *run*out* of spare sectors, or a large amount of layout data has been lost. In this case you may be able to recover the disk with a vendor-specific repair program, but generally the best course of action is to dump the unit. Unless you are using an ancient disk, *do*not* use bad144. mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199712130019.KAA00479>