David C. Rankin wrote:
On 12/15/2019 03:20 AM, Per Jessen wrote:
This morning, I decided I would copy the kernel and initrd to my tftp server and boot them with pxe. I had no expectations that this would produce any better result, just pure desperation.
It worked!!! So here is the puzzle - why would a kernel+initrd boot from PXE but not from disk?
That is strange.
That tells me it wasn't finding what it needed at /dev/sda2. Is there a bios order for boot devices that may specify the actual devices (on of which would be PXE -- which is why that succeeded)??
For testing, I would just hit F8 to pick the PXE boot, but for the time being, I'm letting it default to PXE boot. So the non-working order would be: #1 local disk #2 pxe The curreent order is #1 pxe #2 local disk I'm overjoyed. Have just been watching some HDTV 1080 without stuttering! I am however wondering if the initrd is in fact being loaded when it fails to boot. It is as if the kernel does not have "enough" built in to access the disk.
I'd double check bios, and think through anything being funny with /dev/sda2. I guess there is nothing to look at from a log standpoint pre-boot, so it will be hunt and peck....
A lot of groping in the dark, indeed :-) I am actually perfectly happy for it to boot over PXE, I"m not religious about it. I'm just annoyed that I don't know why it doesn't work directly from disk. -- Per Jessen, Zürich (11.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org