Good Morning
I have a USB drive Sandisk Ultra USB 3.0 64GB which mounts correctly
when plugged into a USB 2.0 port, unmounted the drive and unplugged then
plugged into USB3.0 port which failed to mount the drive, after waiting a
couple of minutes I plugged the drive into the same USB 3.0 port
I have verified all the USB ports on the Z840 using the flash drive and all
function properly.
The 4 TB ZFS volume is still getting scrubbed.on 2017. I have another identical
drive not in ZFS format.
Both WD drives are USB 3 with the double connector at the drive end. The 2nd
one which is a "
On Thu, 23 Jan 2025 at 17:21, Reginald Beardsley wrote:
> Y) 4 TB WD u8 ZFS USB HD
> C does not even see Y via USB
> That's as simply as I can state it. I'll do a port by port test of all 3 with
> Z as soon as all the scrubs finish.
Thanks, that's helpful. What form factor is the 4TB drive? Is
OK.
There are 3 instances of HW. A pair of Z400s with 3 way mirror rpool and 3
slice RAIDZ1, one of which also has a 3 TB plain ZFS pool. One Hipster instance
and one s10_u8, the latter.
A) 2017 Z400 3 disk RAIDZ1
B) s10_u8 Z400 3 disk RAIDZ1 + 1 ZFS pool
C) 2024.10 Z840 4 disk 4 slice RAIDZ2
OK. Another legacy format ZFS USB drive shows up with "zfs import" on the
Z840. Also formatted on the u8 system.
WD drive works on 2017 on an old Z400, but is not seen on newer Z840 running
2024.10
FAT and other ZFS volumes in the same legacy format can be seen on the Z840.
To summarize:
The
On Thu, 23 Jan 2025 at 15:43, Reginald Beardsley via
openindiana-discuss wrote:
> None of those show the USB HD. A flash drive did show up using mdb and it
> automounted. So the USB port is OK, but it doesn't see the WD Elements HD.
>
> Same disk, same cable. Two Z400s see the drive, 2017 and u8,
None of those show the USB HD. A flash drive did show up using mdb and it
automounted. So the USB port is OK, but it doesn't see the WD Elements HD.
Same disk, same cable. Two Z400s see the drive, 2017 and u8, but not the Z840
running 2024.10. Made sure the Z840 was seating the USB A properly.
On Thu, 23 Jan 2025 at 14:54, Reginald Beardsley via
openindiana-discuss wrote:
> Why can 2024.10 not even see it? Is ZFS really broken between 2017 and 2024?
> That seems very unlikely. Is there an OI analog to lsusb(8) on Linux?
> "apropos usb" didn't suggest anything.
There are a number
I have a 4 TB USB HD which can be imported and exported by s10_u8 and Hipster
2017, but which produces no response to "zpool import" on Hipster 2024.10.
2017 reported it was an old format which means it was created on the s10_u8
system.
Why can 2024.10 not even see it? Is ZFS really broken bet
Am 23.01.25 um 17:56 schrieb Marc Lobelle via openindiana-discuss:
Hello,
I have a few machines running still openindiana2023.05.
In tried pkg refresh --full and pkg update -v but when I check which
release is running after rebooting it seems to be still openindiana
2023.05.
Running such outd
It's all in the manpages on your system or online at
https://illumos.org/man/8/bhyve
:)
bHyve is a full VM hypervisor as is Virtualbox. And as Such every VM
needs a Firmware that implements BIOS/UEFI Hardware. For bHyve the
traditional BIOS Firmware was removed as it can not be compiled anymo
FYI
df(1) will tell you the system image which is running in a more human friendly
manner by showing which of the roots is mounted.
Have Fun!
Reg
> zfs list
NAME USED AVAIL REFER MOUNTPOINT
rpool 30.9G 4.25T 186K /rpool
rpool/ROOT 16.8G 4.25T 140K legacy
rpool/ROOT/2021-04-30 153M 4.25T 6.25G
On Thu, Jan 23, 2025 at 05:56:37PM +0100, Marc Lobelle via openindiana-discuss
wrote:
> I have a few machines running still openindiana2023.05.
>
> In tried pkg refresh --full and pkg update -v but when I check which release
> is running after rebooting it seems to be still openindiana 2023.05.
Stick a DVD in a USB optical drive?
FWIW I recently did an update from 2021.04 to 2024.10 via DVD which went
surprisingly smoothly. Came up just as you'd expect. There was no user data on
the machine because by the time i configured it I was unwilling to touch it.
Most brutal sys admin fight o
Hello,
I have a few machines running still openindiana2023.05.
In tried pkg refresh --full and pkg update -v but when I check which
release is running after rebooting it seems to be still openindiana 2023.05.
I'm now copying OI-Hipster-gui-20240426;usb on a usb key . By the way,
is this the
I'm sorry to say I don't understand the "legacy FW" bit.
Does bhyve not present the OS with a virtual bare disk? I spent a good bit of
time looking for technical details about bhyve and didn't find anything well
written. I go back to the "great gray wall" of VMS and all through the
workstation
On 1/23/25 09:23, Toomas Soome via openindiana-discuss wrote:
Solaris 10 was using pre-uefi grub, I doubt very much it got backport because
grub2 appeared in Solaris 11.
rgds,
toomas
Hi!
Just to say it clear.
As the legacy bhyve firmware was removed from OI-bhyve (pkg
system/bhyve/firmware
> On 23. Jan 2025, at 08:38, Till Wegmueller wrote:
>
> Hey Reg,
>
> I am still not on my computer so this is a quick one for now. bHyve and Zones
> brand S10 can both run ontop of any pool. bhyve uses zfs volumes and zones
> use datasets. Both reference the vfs path. Omnios and oi are well
18 matches
Mail list logo
