Stefan Wollny wrote:
Am 11.03.2018 um 01:13 schrieb Alexander Hall:
On March 9, 2018 12:55:31 AM GMT+01:00, Stefan Wollny
wrote:
Am 09.03.2018 um 00:09 schrieb Stefan Wollny:
Am 08.03.2018 um 23:25 schrieb Stefan Wollny:
Am 08.03.2018 um 22:11 schrieb Stefan Wollny:
Am 08.03.2018 um 17:44 schrieb Stefan Wollny:
Gesendet von meinem BlackBerry 10-Smartphone.
Originalnachricht
Von: Kevin Chadwick
Gesendet: Donnerstag, 8. März 2018 17:28
An:misc@openbsd.org
Betreff: Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
On Thu, 8 Mar 2018 14:47:43 +0100
Has anyone a clue what might have happend and how to solve the
issue?
I searched the net but didn't find any substantial infos on this.
As
the error happends with all three USB-keys I have this is
unlikely to
be cause of the trouble.
The bootloader normally lists the disks that the bios sees
beforehand
e.g.
disk: hd0+ hd1+ sr0*
OpenBSD/amd64 BOOT 3.34
Perhaps they have been moved around?
I tried
boot hd1a:/bsd
but got the same message.
I can enter # fsck -fy hd0a but this just gets me a prompt
without any action. BTW: This is a SSD.
OK - back at home I downloaded install63.iso and burned a CD which
does
start. Choosing "(U)pgrade" I am presented with "Available disks
are:
sd0 sd1" - but both are "not a valid root disk". Back to the shell
I
tried fdisk but I get "fdisk: sd0: No such file or directory"
Could this be an issue with the bootloader or is it the encryption
of
softraid0 that hinders the upgrade?
tb@ provided another valuable hint:
I can start the boot-process with 'boot sr0a:/bsd' but this ends with
a
panic:
...
softraid0 at root
scsibus4 at softraid0:256 targets
panic: root device (...) not found
Stopped at db_enter+0x5: popq %rbp
TID PID UID PRFLAGS PFLAGS CPU COMMAND
* 0 0 0 0X1 0X200 OK swapper
...
OK . final remarks for tonight:
I can start 'boot sr0a:/bsd.rd' but trying to upgrade is the same
dead-end road - "sd0 is not a valid root device".
'fdisk sd0' shows the expected '*' before the partition number.
It might help to see the actual output.
'disklabel sd0' shows the expected fstype "RAID" 'for sd0a.
It would certainly help to see the output here. Does it span the *entire* disk,
from 0 to the end?
Doing 'bioctl -c C -l /dev/sd0a' says "KDF hint has invalid size".
'installboot -nv sd0a' misses '/usr/mdec/biosboot' - there is only
'/usr/mdec/mbr'.
While the 'upgrade' started from 'boot sr0a:/bsd.rd' does not see 'sd0'
the 'install' process started from the CD actually does.
"sd0 is not a valid root device" does not say it does not *see* the device. It says
"sd0 is not a valid root device", which is totally correct, as it only holds some raid
metadata and the corresponding encrypted data.
If sd0(a) is a single RAID partition, and sd1 holds the key, your root disk
should appear as sd2 (or whatever the next unused sdN is).
So, if "sd0 is not a valid root device" and "sd1 is not a valid root device",
what gives for sd2?
Please provide as much output as possible from the process. Your interpretation
of it is far less helpful in understanding the problem at hand.
Sincerely,
Alexander
Hi Alexander,
thank you so much for the time you took to look at my posts and to
reply.I type everything from the screen:
At boot time the system reports:
Using drive 0, partition 3.
Loading..
probing: pc0 mem[630k 3250M 7M 246M 452K 12798M a20=on]
disk: hd0+ hd1+ sr0
I'd say something is strange here already. sr0 should have an asterisk
after it. I cannot find the relevant man page to tell you (or me) why,
though. :-d
>> OpenBSD/amd64 BOOT 3.34
open(hd0a:/etc/boot.conf): Invalid argument
boot>
cannot open hd0a:/etc/random.seed: Invalid argument
booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
failed(22). will try /bsd
boot>
cannot open hd0a:/etc/random.seed: Invalid argument
booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
failed(22). will try /bsd
Turning timeout off.
boot>
As said, neither hd0 nor hd1 should be bootable. The assembled sr0
should be.
At this point the system stops the process but is still reachable:
boot> ls
stat(hd0a:/.): Invalid argument
boot> boot hd1a:/bsd
cannot open hd1a:/etc/random.seed: Invalid argument
booting hd1a:/bsd: open hd1a:/bsd: Invalid argument
failed(22). will try /bsd
boot>
Starting /bsd from sr0a is possible but the result is the kernel crash I
already reported.
BUT: I can start bsd.rd!!! By this I was able to post the dmesg (for
your convenience again at the end).
boot> boot sr0a:/bsd.rd
[ ... ]
Welcome to the OpenBSD/amd64 6.3 installation program.
(I)nstall, (U)pgrade, (A)utoinstall or (S)hell?
If I choose to (U)pgrade neither sd0 nor sd1 are recognized as valid
root disks:
Not surprising. There should exist an sd2 at this point though.
[ ... ]
Available disks are: sd0 sd1.
Which disk is the root disk? ('?' for details) {sd0]
sd0 is not a valid
