Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
Am 03/12/18 um 15:02 schrieb Kevin Chadwick: > On Mon, 12 Mar 2018 12:25:40 +0100 > > >> into normal operations. Guess I have to do >> 'installboot sd2' > > I know it is more to type but you can use uids to make sure it is the > right disk too. > You are right - that would have been the better way. I checked beforehand via disklabel if sd0 and sd1 are the actual RAID volumes and sd2 is the decrypted volume. Everything now is fine again: With the key disk inserted OpenBSD starts as usual. Thank you devs for your fine work - the problem sat in front of the screen ;-) Lesson learnt.
Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
On Mon, 12 Mar 2018 12:25:40 +0100 > into normal operations. Guess I have to do > 'installboot sd2' I know it is more to type but you can use uids to make sure it is the right disk too.
Re: Fwd: Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
Gesendet: Sonntag, 11. März 2018 um 22:41 Uhr > Von: "Stefan Wollny" <stefan.wol...@web.de> > An: misc <misc@openbsd.org> > Betreff: Re: Fwd: Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument > Hi Alexander, > > thank you for taking your time to look at my problem! Really appreciate it! > >> Am 11.03.2018 um 22:04 schrieb Alexander Hall: >> 3. Did you by any chance detach the filesystem at any time? IIRC >> that would make it not auto-assemble after reboot, which might >> explain some of the observed behaviours. > Mmmh - this is s.th. I cannot rule out for shure. Last time the system > was work flawless I had an encrypted external HD attached to make my > daily backup. Maybe I did a 'bioctl -d' on the sdx the sd0 was attached > to after disencryption (no - sd0 isn't always attached to sd2! This can > be anything from 2 to 7, usually) instead of the sd-number the external > HD was attached to... > > If so - is there any chance to recover? For the records: As I was able to boot into bsd.rd on the shell I did: 'bioctl -c C -k /dev/sd1a -l /dev/sd0a softraid0' After a reboot I could start via 'boot sr0a:/bsd' into normal operations. Guess I have to do 'installboot sd2' now as this is what the RAID-volume was attached to. Thanks to all of you who took some time and provided help! Best, STEFAN
Re: Fwd: Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
Am 11.03.2018 um 22:04 schrieb Alexander Hall: > 2. Your key disk or sd0 disk raid metadata could be corrupt. Forgot this one: I have three different key disks - none of them gets the system a go.
Re: Fwd: Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
Hi Alexander, thank you for taking your time to look at my problem! Really appreciate it! Am 11.03.2018 um 22:04 schrieb Alexander Hall: > 3. Did you by any chance detach the filesystem at any time? IIRC > that would make it not auto-assemble after reboot, which might > explain some of the observed behaviours. Mmmh - this is s.th. I cannot rule out for shure. Last time the system was work flawless I had an encrypted external HD attached to make my daily backup. Maybe I did a 'bioctl -d' on the sdx the sd0 was attached to after disencryption (no - sd0 isn't always attached to sd2! This can be anything from 2 to 7, usually) instead of the sd-number the external HD was attached to... If so - is there any chance to recover? > 4. Did you by any chance run installboot on sd0 or sd1? That'd be wrong. I tried but without success. Obviously. Thanks again and have a nice week! Best, STEFAN
Re: Fwd: Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
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<stefan.wol...@web.de> 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 su
Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
On March 9, 2018 12:55:31 AM GMT+01:00, Stefan Wollny <stefan.wol...@web.de> 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 > >Sigh - I need some sleep...
Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
> Someone an idea how to proceed? Maybe stop talking to yourself on the email and debug more?
Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
Am 09.03.2018 um 00:55 schrieb Stefan Wollny: > 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. > > 'disklabel sd0' shows the expected fstype "RAID" 'for sd0a. > > 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. Someone an idea how to proceed? I'd hate to reinstall everything... TIA. STEFAN
Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
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. 'disklabel sd0' shows the expected fstype "RAID" 'for sd0a. 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. Sigh - I need some sleep...
Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
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 ...
Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
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? >> > ??? > Running dmesg from the CD-shell the system "sees" sd0 (the internel SSD) > and sd1 (the USB with the key). Having attached another USB drive I see > this is recognizes as sd2. But running 'fdisk sd2' or 'disklabel sd2' I > get "No such file or directory" (and consequently as well when trying to > mount this external drive). > > Puzzled... > tb@ hit me with the clue stick: MAKEDEV was the missing part to mount the external USB drive. Now: Here's the dmesg OpenBSD 6.3-beta (RAMDISK_CD) #38: Thu Mar 8 10:01:01 MST 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 17079074816 (16287MB) avail mem = 16557678592 (15790MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb500 (35 entries) bios0: vendor American Megatrends Inc. version "1.03.06" date 06/25/2014 bios0: Notebook W65_67SZ acpi0 at bios0: rev 2 acpi0: tables DSDT FACP APIC FPDT ASF! SSDT SSDT SSDT MCFG HPET SSDT SSDT SSDT DMAR acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 3093.25 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (RP01) acpiprt2 at acpi0: bus 3 (RP03) acpiprt3 at acpi0: bus 4 (RP04) acpiprt4 at acpi0: bus 1 (P0P2) acpiprt5 at acpi0: bus -1 (P0PA) acpiprt6 at acpi0: bus -1 (P0PB) acpiprt7 at acpi0: bus 1 (PEG0) acpiec0 at acpi0 acpicpu at acpi0 not configured acpitz at acpi0 not configured "INT3F0D" at acpi0 not configured "MSFT0001" at acpi0 not configured "ETD0403" at acpi0 not configured "PNPC000" at acpi0 not configured "PNP0C0C" at acpi0 not configured "PNP0C0E" at acpi0 not configured "PNP0C0D" at acpi0 not configured "ACPI0003" at acpi0 not configured "PNP0C0A" at acpi0 not configured "PNP0C14" at acpi0 not configured "INT340E" at acpi0 not configured pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 4G Host" rev 0x06 ppb0 at pci0 dev 1 function 0 "Intel Core 4G PCIE" rev 0x06: msi pci1 at ppb0 bus 1 vga1 at pci0 dev 2 function 0 "Intel HD Graphics 4600" rev 0x06 wsdisplay1 at vga1 mux 1: console (80x25, vt100 emulation) "Intel Core 4G HD Audio" rev 0x06 at pci0 dev 3 function 0 not configured xhci0 at pci0 dev 20 function 0 "Intel 8 Series xHCI" rev 0x05: msi usb0 at
Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
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? > ??? Running dmesg from the CD-shell the system "sees" sd0 (the internel SSD) and sd1 (the USB with the key). Having attached another USB drive I see this is recognizes as sd2. But running 'fdisk sd2' or 'disklabel sd2' I get "No such file or directory" (and consequently as well when trying to mount this external drive). Puzzled...
Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
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?
Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
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.
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?
booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
Hi there! I need help or some hints on how to proceed: My system a laptop running amd64-current fully encrypted, key-based. I start from BIOS, not UEFI. Two days ago I updated to the then latest snapshot and apparently s.th. went wrong: At reboot the system stops after >> OpenBSD/amd64 BOOT 3.34 open(hd0a:/etc/boot.conf): Invalide argument 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> 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. At present I only have a USB-stick with install62.fs with me (roughly 3~4 weeks old) which only starts if I change from BIOS to UEFI. As all data from /home is redundantly backed up I could reinstall everything but would prefer to avoid it. There are dmesgs from this laptop with some older posts. Obviously no current dmesg possible... Any hint/idea/suggestion welcome! TIA. Best, STEFAN
