Re: Getting "Boot error" after replacing a disk in softraid
a bit late, but fwiw - I have 7.5 on an optiplex 990 on SSD, no issues. Not quite a 980, but I honestly doubt that this matters given my experience on these boxes. (I also have 7.5 on a 960, and have had it on a 955 and 945. There’s nothing special about the Dells that I have and booting MBR with SSD.) AHCI vs IDE shouldnt matter for booting (but IDE is slower), but if you had the ports in RAID mode it might. # dmesg|egrep 'OpenBSD|Opti|INTEL' OpenBSD 7.5 (GENERIC.MP) #82: Wed Mar 20 15:48:40 MDT 2024 bios0: Dell Inc. OptiPlex 990 sd0 at scsibus1 targ 0 lun 0: naa.55cd2e404b451004 > On Apr 23, 2024, at 2:08 PM, Martin wrote: > > Turns out this machine, for some reason, simply cannot boot of SSDs with > neither OpenBSD or FreeBSD on the box. Only spinning drives work. > > It's an old Dell Inc. OptiPlex 980. > > I suspect there is some issue with the BIOS of the machine and the BSD > bootloaders as Linux with GRUB works on SSDs. >
Re: Getting "Boot error" after replacing a disk in softraid [SOLVED]
On 2024-04-25, Chris Petrik wrote: > Remember softraid isn't the same as hw raid and I will always chose hw over > soft this includes zfs. There are advantages and disadvantages for both. e.g. a software setup with multiple disk controllers can, if there's support for data error detection[1], protect against (or at least detect) errors on the hardware->cpu path which might not be noticable on a single hw raid controller. And in the event of controller/motherboard failure it might not be possible to attach drives to another machine (unless a suitable spare is at hand) with hw raid, whereas with sw they could often just be moved. [1] yes I know OpenBSD softraid(4) doesn't do it, but some others do
Re: Getting "Boot error" after replacing a disk in softraid [SOLVED]
> Hello, > > Remember softraid isn't the same as hw raid and I will always chose hw over > soft this includes zfs. > > Chris I am sorry, but what relevance does your personal preferences have to anything regarding this issue? FWIW, I have seen more than one example of some really crappy hardware raid controllers that I wouldn't hesitate a split second to replace with ZFS.
Re: Getting "Boot error" after replacing a disk in softraid [SOLVED]
Hello, Remember softraid isn't the same as hw raid and I will always chose hw over soft this includes zfs. Chris Sent from Proton Mail Android Original Message On 4/25/24 3:14 PM, Martin wrote: > > On Thu, Apr 25, 2024 at 09:12:47AM +0200, Stefan Sperling wrote: > > > > > I checked, the softraid manual page already has an example installboot > > > invocation in EXAMPLES, which should be clear enough. > > > > > > Regardless, I've tweaked the wording a bit. Hopefully more clear now. > > Indeed :) Thank you very much! > >
Re: Getting "Boot error" after replacing a disk in softraid [SOLVED]
> On Thu, Apr 25, 2024 at 09:12:47AM +0200, Stefan Sperling wrote: > > > I checked, the softraid manual page already has an example installboot > > invocation in EXAMPLES, which should be clear enough. > > > Regardless, I've tweaked the wording a bit. Hopefully more clear now. Indeed :) Thank you very much!
Re: Getting "Boot error" after replacing a disk in softraid [SOLVED]
On Thu, Apr 25, 2024 at 09:12:47AM +0200, Stefan Sperling wrote: > I checked, the softraid manual page already has an example installboot > invocation in EXAMPLES, which should be clear enough. Regardless, I've tweaked the wording a bit. Hopefully more clear now.
Re: Getting "Boot error" after replacing a disk in softraid [SOLVED]
On Thu, Apr 25, 2024 at 03:27:29AM +, Martin wrote: > I eventually found out what was going on. > > The FreeBSD boot problem was not related at all. > > Long story short and for future reference, installboot needs > to be run on the softraid volume, NOT on the physical disk. And this > has to be repeated after a softraid volume rebuild in order for the new > disk to be bootable too. > > This cannot be done from the boot media, but one can boot from media > and then mount the softraid with the working disk and then chroot into > that and run 'installboot sd2' (or whatever device name the softraid > volume has). > > This was not obvious to me. Perhaps because with GRUB one has to install > the bootloader and boot code on each single disk in a mdadm volume and > not on the volume itself. Ah, indeed. Thanks for reporting back with the solution. This should be obvious but it's understandable that new users might miss it. I checked, the softraid manual page already has an example installboot invocation in EXAMPLES, which should be clear enough.
Re: Getting "Boot error" after replacing a disk in softraid [SOLVED]
I eventually found out what was going on. The FreeBSD boot problem was not related at all. Long story short and for future reference, installboot needs to be run on the softraid volume, NOT on the physical disk. And this has to be repeated after a softraid volume rebuild in order for the new disk to be bootable too. This cannot be done from the boot media, but one can boot from media and then mount the softraid with the working disk and then chroot into that and run 'installboot sd2' (or whatever device name the softraid volume has). This was not obvious to me. Perhaps because with GRUB one has to install the bootloader and boot code on each single disk in a mdadm volume and not on the volume itself.
Re: Getting "Boot error" after replacing a disk in softraid
> That seems... unusual. Do you have an (old) IDE compatibility option turned > on in > the BIOS? I would have expected it to attach via AHCI: > sd0 at scsibus1 targ 2 lun 0:
Re: Getting "Boot error" after replacing a disk in softraid
On Tue, Apr 23, 2024 at 08:26:40PM -0500, Brian Conway wrote: > > wd0 at pciide0 channel 0 drive 0: > > That seems... unusual. Do you have an (old) IDE compatibility option turned > on in the BIOS? I would have expected it to attach via AHCI: > > sd0 at scsibus1 targ 2 lun 0: > naa.5002538e304456ac > > Brian Conway I don't see any special settings in the BIOS. Two of the pertinent screenshots from the BIOS settings are at: https://www.eskimo.com/~joji/optiplex745/ Not sure why the wd(4) driver was chosen over the sd(4) driver.
Re: Getting "Boot error" after replacing a disk in softraid
On 2024-04-24, Brian Conway wrote: >> wd0 at pciide0 channel 0 drive 0: > > That seems... unusual. Do you have an (old) IDE compatibility option turned > on in the BIOS? I would have expected it to attach via AHCI: Optiplex 980 is from ~2010, similar age to the HP N54L microserver etc. Disks connecting by wd(4) and BIOS bugs relating to certain types of storage device were pretty common back then.
Re: Getting "Boot error" after replacing a disk in softraid
> RAID replicates the data in the RAIDed area, yes? > > Do you have some reason to believe that the boot information (MBR, etc) is > _inside_ the RAID area, because I do not believe that. Really feels like > installboot needs to be run on this drive to, uh, install the proper boot > info. > > Philip Guenther installboot has been run.
Re: Getting "Boot error" after replacing a disk in softraid
> wd0 at pciide0 channel 0 drive 0: That seems... unusual. Do you have an (old) IDE compatibility option turned on in the BIOS? I would have expected it to attach via AHCI: sd0 at scsibus1 targ 2 lun 0: naa.5002538e304456ac Brian Conway
Re: Getting "Boot error" after replacing a disk in softraid
RAID replicates the data in the RAIDed area, yes? Do you have some reason to believe that the boot information (MBR, etc) is _inside_ the RAID area, because I do not believe that. Really feels like installboot needs to be run on this drive to, uh, install the proper boot info. Philip Guenther On Tue, Apr 23, 2024 at 8:19 AM wrote: > Also, if I boot from a USB stick, with only the new SSD attached, the > softraid is registered as degraded (as the other old disk is missing), so > it has been populated, and the partition is also marked with an asterisk > for boot, but I still cannot boot from that drive. > >
Re: Getting "Boot error" after replacing a disk in softraid
> FWIW, my current desktop which is a Dell OptiPlex 745 is booting off an SSD. > > joji@surya$ dmesg | grep -iE "optiplex|Samsung" > bios0: Dell Inc. OptiPlex 745 > wd0 at pciide0 channel 0 drive 0: > > > joji@surya$ uname -a > OpenBSD surya 7.5 GENERIC.MP#82 amd64 > > Don't know if your OptiPlex 980 is newer than mine. I find it strange that this isn't working, but I have tried just going for a standard OpenBSD install and also tested a standard FreeBSD install on two different SSDs - ignoring my original softraid setup, but no matter what I do, it just will not boot with either BSDs on either of those disks on this machine. I have tried placing each disk in each different SATA plug, also just to eliminate an issue with a specific SATA port, but it's the same result, no matter what port is set to boot from. I wiped the disks, installed Devuan Linux with GRUB on the same pair of disks, just to test, and it boots fine from either disk. So, for the moment I have given up running OpenBSD on SSDs on this box.
Re: Getting "Boot error" after replacing a disk in softraid
On Tue, Apr 23, 2024 at 09:08:26PM +, Martin wrote: > Turns out this machine, for some reason, simply cannot boot of SSDs with > neither OpenBSD or FreeBSD on the box. Only spinning drives work. > > It's an old Dell Inc. OptiPlex 980. > > I suspect there is some issue with the BIOS of the machine and the BSD > bootloaders as Linux with GRUB works on SSDs. FWIW, my current desktop which is a Dell OptiPlex 745 is booting off an SSD. joji@surya$ dmesg | grep -iE "optiplex|Samsung" bios0: Dell Inc. OptiPlex 745 wd0 at pciide0 channel 0 drive 0: joji@surya$ uname -a OpenBSD surya 7.5 GENERIC.MP#82 amd64 Don't know if your OptiPlex 980 is newer than mine.
Re: Getting "Boot error" after replacing a disk in softraid
Turns out this machine, for some reason, simply cannot boot of SSDs with neither OpenBSD or FreeBSD on the box. Only spinning drives work. It's an old Dell Inc. OptiPlex 980. I suspect there is some issue with the BIOS of the machine and the BSD bootloaders as Linux with GRUB works on SSDs.
Re: Getting "Boot error" after replacing a disk in softraid
Also, if I boot from a USB stick, with only the new SSD attached, the softraid is registered as degraded (as the other old disk is missing), so it has been populated, and the partition is also marked with an asterisk for boot, but I still cannot boot from that drive.
Re: Getting "Boot error" after replacing a disk in softraid
> I suspect this error comes from your BIOS/UEFI rather than the OpenBSD > boot loader. Did you check how boot drives are configured in firmware? I already tested that by moving the new disk to another box and boot it from that, unfortunately I get the same error.
Re: Getting "Boot error" after replacing a disk in softraid
On Tue, Apr 23, 2024 at 12:51:41AM +, i...@protonmail.com wrote: > I have a softraid mirror setup with two old spinning disks. I have detached > one of the disks from the mirror and attached a new SSD. I then wanted to > rebuild the mirror, using one old spinning drive and the new SSD, and then > afterwards, remove the old spinning drive and replace with yet another SSD, > ending up with a mirror of two new SSDs. > > After I attached the new SSD to the box, I did: > > fdisk -iy sd1 (the new disk) > > Then I cloned the layout of the old drive onto the new: > > disklabel sd0 > layout > disklabel -R sd1 layout > > Then I used installboot: > > installboot sd1 > > And started rebuilding the mirror: > > bioctl -R /dev/sda1 sd2 (sd2 being the RAID device) > > This worked fine and the mirror is up. > > However, when I now dettach the old drive and boot from only the new SSD, I > get "Boot error". > > What am I missing? I suspect this error comes from your BIOS/UEFI rather than the OpenBSD boot loader. Did you check how boot drives are configured in firmware?
Getting "Boot error" after replacing a disk in softraid
I have a softraid mirror setup with two old spinning disks. I have detached one of the disks from the mirror and attached a new SSD. I then wanted to rebuild the mirror, using one old spinning drive and the new SSD, and then afterwards, remove the old spinning drive and replace with yet another SSD, ending up with a mirror of two new SSDs. After I attached the new SSD to the box, I did: fdisk -iy sd1 (the new disk) Then I cloned the layout of the old drive onto the new: disklabel sd0 > layout disklabel -R sd1 layout Then I used installboot: installboot sd1 And started rebuilding the mirror: bioctl -R /dev/sda1 sd2 (sd2 being the RAID device) This worked fine and the mirror is up. However, when I now dettach the old drive and boot from only the new SSD, I get "Boot error". What am I missing?
