tech-userlevel archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: installboot: Old BPB too big, use -f (may invalidate filesystem)

Le Mon, Feb 14, 2022 at 07:25:37PM +0100, Edgar Fuß a écrit :
> What does
> 	installboot: Old BPB too big, use -f (may invalidate filesystem)
> mean?
> I have a RAIDframe level 1 RAID consisting of /dev/sd0e and /dev/sd1e.
> Now, sd0 failed. I replaced the disc, fdisk'ed and disklabel'ed it and 
> performed a raidctl -R, which succeeded. Now, I need to write the boot 
> code, so I can boot from the new disc. But installboot /dev/rsd0e 
> /usr/mdec/bootxx_ffsv1 gives me above error message.
> I tried installboot -n /dev/rsd1e /usr/mdec/bootxx_ffsv1, which works.
> The only other oddity I see with the new disc is that fdisk provokes an 
> SCSI error and
> 	sd0d: error reading fsbn 71819495 (sd0 bn 71819495; cn 49191 tn 0 sn 635)
> plus
> 	fdisk: Can't read secondary GPT header: Invalid argument
> (the disc size is 71819433).

BPB is PC specific and linked to MBR if I'm not mistaken. What seems to
me problematic is that you mention fdisk (i.e. MBR) first and the
error message is about GPT...

Since I never used directly raid (I had indirect experiences and all
negative---not RAID with NetBSD: appliances coming with RAID), this is
to be taken with a grain of salt. Apparently, the problem is a mix
between MBR and GPT, adding the complication of RAID.
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C

Home | Main Index | Thread Index | Old Index