On Thu, 16 Jun 2022 16:08:15 +0200
Martin Husemann wrote:
> On Wed, Jun 15, 2022 at 05:42:55PM -0500, Ted Spradley wrote:
> > The other drive was a NetBSD-5.1 raid pair, one of which was apparently
> > damaged.
>
> What was the "Root partition:" value in the "raidctl -s" output for that
>
On Wed, Jun 15, 2022 at 05:42:55PM -0500, Ted Spradley wrote:
> The other drive was a NetBSD-5.1 raid pair, one of which was apparently
> damaged.
What was the "Root partition:" value in the "raidctl -s" output for that
raid?
Martin
On Wed, 15 Jun 2022 05:12:37 - (UTC)
mlel...@serpens.de (Michael van Elst) wrote:
> tsp...@talent-free-studios.com (Ted Spradley) writes:
>
> >As long as it's the only disk attached this boots up and works fine:
> >But if there is any other drive attached, that other drive gets mounted as
>
tsp...@talent-free-studios.com (Ted Spradley) writes:
>As long as it's the only disk attached this boots up and works fine:
>But if there is any other drive attached, that other drive gets mounted as
>root (apparently).
What is on that other drive ?
Here is a rough description of the default
On Mon, 13 Jun 2022, Ted Spradley wrote:
Any suggestions how to fix in place?
If you cam convert your MBR to GPT, and label the GPT partitions, then
you can use those labels instead of device-names:
$ cat /boot.cfg
[...]
menu=Boot TEST:gop 0;rndseed /var/db/entropy-file;boot
As long as it's the only disk attached this boots up and works fine:
unit2$ doas gpt show wd0
gpt: /dev/rwd0: bogus map current=mbr partition new=secondary gpt header
unit2$ doas fdisk wd0
Disk: /dev/rwd0
NetBSD disklabel disk geometry:
cylinders: 465141, heads: 16, sectors/track: 63 (1008
