Re: [OpenIndiana-discuss] dell 15810 bricked after latest update

2022-06-27 Thread s...@pandora.be
By the way the subject line says "dell 15810" but in fact in the text you wrote t5810 I think the T5810 is probably the right model name 'T' for Tower not '1' like 15810 There is no entry for the T5810 but interesting perhaps to have it submitted (added) to http://docs.openindiana.org/commu

Re: [OpenIndiana-discuss] problem replacing a disk by a bigger one

2022-06-27 Thread Gary Mills
On Mon, Jun 27, 2022 at 05:33:45PM +0200, Marc Lobelle wrote: > > 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

Re: [OpenIndiana-discuss] problem replacing a disk by a bigger one

2022-06-27 Thread Marc Lobelle
Hello Thanks for your help._/I also found a good step by step guide at https://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/

Re: [OpenIndiana-discuss] problem replacing a disk by a bigger one

2022-06-27 Thread Toomas Soome via openindiana-discuss
hi! Ok, first of all, there is no reason to copy zfs pool with dd. It may or may not work. For single disk migration, it is better to use either zpool mirror + zpool split, or zfs send, as zfs send or beadm create -p poolname beName. please note that beadm create does not mirror everything over

Re: [OpenIndiana-discuss] problem replacing a disk by a bigger one

2022-06-27 Thread Guenther Alka
If you want to replace the bootdisk the easiest disaster recovery method is to zfs send the current BE to your datapool, then do a clean install of OI to a new disk, send the BE back, activate then boot into the old BE. For a non boot disk (with rpool) do a zpool replace poolname olddisk newdi