The cause of this problem is: Apr 21 15:52:52 /netbsd: vendor 0x8086 product 0xa12f (USB serial bus, xHCI, re vision 0x31) at pci0 dev 20 function 0 not configured
No USB functionality meant attempts to use install media failed at the point where a root device is asked for (because no keyboard, and there's no PS/2 socket on these servers). I got the system to a multi-user login (but can't login) by building an installation on one of the hot-swappable drives taken out of its frame and stuck in a USB caddy on a different machine. I'm planning to enable the LAN that may allow me to carry on configuring with an rlogin - it's very tricky via the USB caddy because all the device names are wrong. Does anyone know if this chip is supported/likely to be supported? -- Steve Blinkhorn <[email protected]> You wrote: > > Date: Fri, 20 Apr 2018 15:52:43 +0000 (UTC) > From: [email protected] (Steve Blinkhorn) > Message-ID: <[email protected]> > > | But returning it to the server, it gives the message: > | > | NetBSD MBR boot > | Error No operating system > > This all comes from the MBR boot code (the 400 or so bytes that > follow the MBR partition table). "No operating system" seems to > mean that the magic number of the bootable partition was not > correct. > > That all was OK on the other system suggests that perhaps there's > a drive geometry mapping problem - to be as portable to ancient > systems as possible, the MBR boot code uses CHS addressing if > it believes that it should work (there's not much space there to allow > for fallbacks, and alternatives,...) > > What does fdisk report about the MBR, and is that likely to be what > the system you want to boot from implements? > > Also beware of sector size issues - drives in USB caddies sometimes > do not act the same way as when directly SATA connected (or so I > have read). > > kre > >
