Re: Installer cannot open hd0a

On Sun, Jun 23, 2024 at 11:50:31AM GMT, Anon Loli wrote:
>On Sun, Jun 23, 2024 at 11:44:30AM +0000, Anon Loli wrote:
>> On Sat, Jun 22, 2024 at 06:34:19PM +0000, James Cook wrote:
>> > On Sat, Jun 22, 2024 at 03:46:16PM GMT, Anon Loli wrote:
>> > > On Sat, Jun 22, 2024 at 03:11:50PM +0000, Anon Loli wrote:
>> > > > (I sent this a few hours ago, but I didn't see it in the mailing list, I think
>> > > > you aren't allowed to have a ':' in the subject title)
>> > > >
>> > > > Hello list and fellow wizards
>> > > >
>> > > > I have a problem installing OpenBSD on one of my computers
>> > > > I tried 7.3 and 7.5 installs, both(I think, not sure if both share same "hd0a"
>> > > > part) give me this right after BOOT command is
>> > > > initiated in the initial OpenBSD screen:
>> > > > cannot open hd0a:/etc/random.seed: No such file or directory
>> >
>> > It's normal for that message to appear when you're booting from an install
>> > image. I guess /etc/random.seed is not included because it would be the same
>> > for everyone, defeating the purpose of the file.
>> >
>> > > > And I can't use DD on other drives such as a SD or a WD device
>> > > >
>> > > > Do you know what the issue is? It could be just some BIOS option, but I loaded
>> > > > EFI defaults so IDK
>> > >
>> > > I also forgot to mention that during installation I used auto-partitioning, and
>> > > that seems to have gone well, except that the / partition was like 130% full
>> > > because /dev/rsd1 which was the other drive, was like 600M in size or something
>> > > like that, and I was even able to `rm /dev/rsd1` without problem and that freed
>> > > up the negative storage space.. so I'm sure that it's something related to
>> > > storage, maybe a BIOS setting, or maybe my USB drive was corrupted or
>> > > something?
>> >
>> > /dev/rsd1 should not exist. Probably it is a regular file you created with a
>> > command like cat image > /dev/rsd1. This is a great way to accidentally fill
>> > up your root partition. If you want to overwrite the contents of sd1, the
>> > device you want is /dev/rsd1c.
>> >
>> > --
>> > James
>> >
>>
>> Every time I tried it, be it 7.3 or 7.5 install*.img, or I now tried a CD/DVD
>> 7.5 iso and got "cannot open cd0a.....\n booting cd0a", I always went to SHELL
>> and typed this:
>> `dd if=/dev/urandom of=/dev/rsd0c bs=1m` the sd0 or sd1 being 2 of my drives
>> I always get the exact following message:
>> "uid 0 on /: file system full
>>
>> /: write failed, file system is full
>> dd: /dev/rsd0c: No space left on device
>> 1+0 records in
>> 0+0 records out
>> 0 bytes transferred in 0.003 seconds (0 bytes/sec)"
>>
>> Okay, dmesg seems to see them well, but I don't see them in /dev/ at all, I
>> just now realized this
>>
>> There is another message which looked like an error message, right after the
>> "booting cd0a", it has something similar to "0x00FFFF", but it goes away way
>> too fast for me to read it, is there a logfile of the full boot sequence
>> output that I can take a look at or something?
>>
>
>So it's after "booting cd0a (or hd0a)", but before "OpenBSD 7.5" aka the 1st
>line in dmesg
>There was a logfile with these kind of logs, but I forgot where it is ._.

Sorry, I missed this. (Feel free to cc me to get my attention next
time.)

The bootloader prints a sequence of numbers before it boots the
kernel. I think it's reporting on pieces of the kernel being loaded
into memory. Perhaps that is the message that you are seeing.

As for "dd: /dev/rsd0c: No space left on device": two things.

1. If you are following the normal installation steps without going
into the shell, this sort of thing shouldn't happen. So I guess you
are trying to do something manually through the shell. I'm curious
what that is.

2. Why you're getting that error:

The installer image does not have the device file /dev/rsd0c. You
need to first create it like this (in the install image's shell):

cd /dev
sh MAKEDEV sd0

Otherwise, writing to /dev/rsd0c will create a regular file with
that name, which can quickly fill up the ramdisk filesystem.

--
James