10:21:57 hadfl in case you missed it (I was editing a bit) https://github.com/omniosorg/zadm/issues/151#issuecomment-3023168201 I think I found the issue, with that change zadm doesn't complain. I think it's also intended to be valid and just a small coding error. But my perl skills are pretty bad so that may open a whole can of unintended side effects. 10:59:16 Hi guys 10:59:25 I'm Amir and I'm from Iran 11:00:02 I'm assuming that you are aware of out current situation about the war... 11:00:16 we are having Internet connectivity issues here 11:00:53 so I am going to make an OmniOS mirror hosted here to be used for my servers and other OmniOS users in our country 16:05:07 :) load average: 1,11, 1,11, 1,11 17:57:26 I foolishly added hw.vmm.amdvi.enable=1 in /boot/loader.conf and a few entries as per https://www.cyber-tec.org/2019/05/29/using-bhyve-pci-passthrough-on-omnios/ and now have a non-booting system. Anyway to fix this without a re-install? 18:09:02 Trying to mount anything from the boot disk doesn't work and zfs says there's no datasets. 18:17:38 Is that not a FreeBSD file? On my OmniOS, I don’t even have a /boot/loader.conf . 18:18:43 It's not there by default but you can add it (as per loader manpage). 18:19:16 There has to be a way to mount disk/zfs dataset from a bootdisk. 18:20:16 Do you have more than one boot environment? 18:21:54 Yes, but it's a ways back. That would require re-updating. There's no way to mount from a bootdisk? In linux it's just 'mount /dev/sda2 /mnt' and you have your disk partition to fix. 18:22:14 I think the disk was c1t0d0s0 but it doesnt' show under /dev/dsk. 18:24:19 From the bootdisk, I would try « zpool import » to list zpools ready to import and then « zpool import zpool_name » but you would have to precise an alternate root 18:25:55 Shows rpool ONLINE and then c3t0d0 ONLINE 18:29:13 Might be getting some place. I see the datasets now. 18:35:50 How to mount that dataset someplace else? zfs mount -o mountpoint=/mnt rpool/ROOT/omnios-r151054e doesn't work. Nor does zfs mount rpool/whatever /mnt 18:41:01 Use flag « -R » 18:41:02 https://docs.oracle.com/cd/E18752_01/html/819-5461/gbcgl.html 18:41:52 zfs set mountpoint=/new/mountpoint dataset_name I got the dataset mount, and removed the file. Now to put it back together again... 18:47:42 I put the mountpoint back to / and rebooted but it still hangs. Not sure what to do at this point. 18:51:17 I had to select 'reconfigure' at the loader screen. Now it boots again. Thanks mighty_spiky. As you can tell, I don't know a whole lot about zfs. 18:52:39 You’re welcome. I’m also quite new to Illumos/OmniOS but I have some experience with ZFS on FreeBSD and Linux. 18:54:03 I'm on Slackware, and I guess I could get it, but it's not available to set the system up from install and of course Solaris 9 didn't have it back then. 18:57:54 Even if it’s limited to my data on Linux (As you say, it’s hard to set it up on OS drives), I find ZFS quite useful on all my systems. 20:59:14 jayjwa: for future reference I think you need options at import time to tell it to use an alternative root for the dataset and/or tell it not to automatically mount the zfs dataset mountpoints (see variations of the -N -o and -R flags for zpool import in https://man.omnios.org/man8/zpool) 21:00:02 by default when you import a pool it'll try to mount any dataset on that pool at any configured mountpoint within the dataset config. 21:02:46 So I could have just done it with zpool right off then. 21:03:22 you may also have issues if the boot media uses the same pool name as the media you're trying to mount - I think you can rename the pool at import time if both the boot media and the thing you're trying to fix both use the same pool name (rpool) - although I forget if you might then have to try and rename the pool you're fixing back somehow 21:05:10 Basically I just needed to remove /boot/loader.conf and any /etc/ppt* I added about the passthru. Not sure if it was indeed loader.conf, the /etc/ppt* files, or some combo. 21:06:04 The next question would be why that loader.conf setting caused such a problem. 21:09:24 there might be better ways to fix things in the zfs world for that sort of issue, but from the bits I've played with I think doing something like `zpool import -R /mnt rpool` might have been a fairly easy option - especially if you use a boot medium that doesn't use rpool for it's own zpool 21:12:49 when you get stuck again the man pages are often worth reading - they're generally quite useful in the OmniOS/Illumous/Solaris world 22:00:16 I’m 60% sure creating /boot/loader.conf replaced the default loader config. And since there was only that parameter there the system didn’t know how to boot. 22:00:57 Or you somehow added your boot nvme/hba/storage controller to the ppt driver, but more unlikely 22:03:24 Nope. No /boot/loader.conf. There's a loader.rc, loader, and loader.help in /boot/. The file didn't exist before and I added that one line. 22:06:28 loader.rc has the include so that it is eventually grabbed, according to loader.conf(5) 22:06:58 There is one in /boot/defaults