Hi Thomas,

Currently, If I try to boot the openindiana disk (Windows and Openindiana are on 2 different SSD) on this HP elitebook 820G3,

If I try to boot it uefi, I come back to the general booting menu of HP,

If I try to boot it legacy, I get on the screen

   BIOS drive C: is disk0

   BIOS drive D: is disk1

   ZFS: i/o error - all block copies unavailable

   ZFS:  can't read MOS of pool rpool

   Can't find /boot/loader

   Can't find /boot/zfsloader

   illumos/x86 boot

   Default: /boot/loader

   boot:

Do you know how to fix it  ?

Thanks

Marc

On 7/1/22 12:09, Toomas Soome via openindiana-discuss wrote:

On 1. Jul 2022, at 11:24, Marc Lobelle<marc.lobe...@uclouvain.be>  wrote:

I think I know where the problem is: "# bootadm install-bootloader -P rpool " installs what is 
needed to boot in UEFI mode and this is not possible on a computer that can be dual booted with windows, even 
in my case where openindiana and windows are on 2 different ssd. And this operation made all the disks in 
rpool unbootable on this system. I should probably have run"# bootadm install-bootloader -Mf -P rpool 
" to force installation of a "legacy" MDB boot.

So, at this point, the only way to run openindiana on the system to fix this 
issue is running it from the installation dvd. However, if I type zpool list on 
that, I do not see any pool even if I boot it with reconfigure. How can I 
install the booting stuff on the internal disk of the system from an openidiana 
running on the installation dvd. Some versions of bootadm allow specifying the 
device on which to install the booting  stuff, but not the bootdm on 
openindiana.

Thanks for your help

Marc
At this time,we do not have an access to EFI runtime functions, so, we only do install boot 
loader as generic efi application (<ESP>/boot/bootx64.efi). If you have 
dual/multiboot setupand have this binary from some other OS, you need to make backup of it 
first, then after bootloader install/update,you need to create alternate locationfor it, 
like <ESP>/boot/illumos/ and create UEFIboot manager configuration in firmware setup 
and restore the original bootx64.efi.

The problem is without an access to EFI RT functions, we can not access/create 
efi bootmanager variables, and thats why we do use default.

Please note, every pkg update may also update the boot loader (depending on if 
the bootloader has received some change - see installboot -i).

Also, bootadm does internally use installboot, and we do install boot support 
for both UEFI and BIOS boot.

rgds,
toomas


On 6/28/22 10:38, Marc Lobelle wrote:
Hello, more information below on this problem

On 6/27/22 17:33, Marc Lobelle wrote:
Hello

Thanks for your help._/I also found a good step by step guide 
athttps://omnios.org/info/migrate_rpool. /_(There are other ones, but over 10 
years old) The only change I had to make was using the guid for the source disk 
and the complete real path name to the new device ( even /dev/dsk/..., which is 
a symlink did not work) in zpool attach. The need to use the GUID is a known 
old bug that was supposed to have been fixed. I do not know why I had the use 
the full pathname of the new disk. Maybe it is due to the fact that the new 
disk was connected to a usb adaptor.
So what I did is

# zpool attach rpool 9083243097870587132 
/devices/pci@0,0/pci103c,807c@14/storage@d/disk@0,0:q

# bootadm install-bootloader -P rpool

However my bios could not boot from this usb disk when I tried to place it in 
the internal slot, so I rebooted the old internal disk, with the usb disk 
connected . Then I detached old internal disk and now the notebook runs on the 
external disk.
# zpool detach rpool c6t0d0s0


# zpool status
   pool: rpool
  state: ONLINE
   scan: resilvered 30,5M in 0 days 00:00:01 with 0 errors on Mon Jun 27 
16:30:25 2022
config:

         NAME STATE     READ WRITE CKSUM
         rpool ONLINE       0     0     0
/devices/pci@0,0/pci103c,807c@14/storage@d/disk@0,0:q ONLINE 0     0     0

errors: No known data errors

   pool: szpool
  state: ONLINE
   scan: none requested
config:

         NAME           STATE     READ WRITE CKSUM
         szpool         ONLINE       0     0     0
           /dev/lofi/1  ONLINE       0     0     0

errors: No known data errors

Of course, my aim is to put the new inside the notebook at the place where the 
old one was.

I assume that there are probably things to change in the new disk before 
putting it in the notebook.

Besides, now that the old internal disk has been detached, can I still reboot 
the computer with only the old internal disk

My current situation is thus that I booted from the internal disk, attached the 
external one and detached the internal one (at this point everything runs fine)

My two questions are thus:
1. Now that I have detached the disk inside the computer, can I still
    reboot with only this disk ? i.e. may I stop the computer, remove the usb 
disk that is now the only one remaining from the mirror consisting of the 
internal and the external disk. ie does the boot know that his disk is not part 
of the mirror ?
2. Do I have to change something in the new disk to connect it as sata
    drive rather than as usb drive and boot the system from it ?

Thanks, I wait for your advice before risking to turn off the notebook

Best regards

Marc


On 6/26/22 23:46, Marc Lobelle wrote:
Hello

In tried to replace the ssd of my notebook running openindiana (120G) by a 
bigger one (1T).

I first copied the small ssd on the big one: I connected the big disk on a usb 
adapter, ran format to identify the two devices then

dd if=/dev/rdsk/c6t0d0p0 of=/dev/rdsk/c4t0d0p0 bs=2048K

then I replaced the small internal disk by the big one.

However, when booting, I got the following message

    ZFS:i/o error - all block copies unavailable

    ZFS: Can't read MOS of pool rpool

    Can't find /boot/loader

    Can't find /boot/zfsloader

    illumos/x86 boot

    Default: /boot/loader

    boot:

if I type <enter>, I get

    Can't find /boot/loader

    illumos/x86 boot

    Default: /boot/loader

    boot:

How can I fix this ? (without reinstalling everything if possible;-) (after 
that I plan of course to grow the fs to the whole disk)

Marc
_______________________________________________
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
_______________________________________________
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
_______________________________________________
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
_______________________________________________
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

_______________________________________________
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
_______________________________________________
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Reply via email to