[Charset ISO-8859-1 unsupported, filtering to ASCII...]
> It seems Cejka Rudolf wrote:
> > I think internal bad block remapping is long time here. But
> > in the middle of 1996 I have bought a new Western Digital disk
> > with some bad sectors and it runs without any problems till today
> > (and
On Sun, 26 Sep 1999, Cejka Rudolf wrote:
> Ok: Just run "disklabel -r -e ad0", clear word "badsect"
> in "Flags:" line and booting of new kernels is back...
I think phk set to switch back to the wd driver to run disklabel, but
that shouldn't be necessary -- a new label can certainly be written
u
It seems Cejka Rudolf wrote:
> I think internal bad block remapping is long time here. But
> in the middle of 1996 I have bought a new Western Digital disk
> with some bad sectors and it runs without any problems till today
> (and without any new bad sectors - I have tried new disk format
> some
Thanks to both replies - these helped me for staying in -current...
Poul-Henning Kamp wrote (1999/09/25):
> Your disk claims to have bad144 enabled, the ata driver doesn't
> support this.
> If you need bad144 support (ESDI or ST506 disks, you can recognize
> them by the two ribbon cables and the
It seems Cejka Rudolf wrote:
>
> I'm trying to update my -current system compiled from July 12 (both
> kernel and base system). But before all system updating I have tried to
> compile and run new kernel from today (September 25) - and it won't
> boot so I'm afraid to update all the system...
> B
Your disk claims to have bad144 enabled, the ata driver doesn't
support this.
If you need bad144 support (ESDI or ST506 disks, you can recognize
them by the two ribbon cables and their 8+ years of age) you need
to use the wd driver.
Otherwise you need to fix your disklabel (by booting with the
