Any thought?
There is a reason OMV doesn't let you include USB devices in a raid array - you shouldn't do it. The hat (i have one) doesn't do magical things to make it good for a raid array.
Any thought?
There is a reason OMV doesn't let you include USB devices in a raid array - you shouldn't do it. The hat (i have one) doesn't do magical things to make it good for a raid array.
There is a reason OMV doesn't let you include USB devices in a raid array - you shouldn't do it. The hat (i have one) doesn't do magical things to make it good for a raid array.
Thanks for the reply. OMV doesn't appear to be what I need if it cant run raid on this device. Since the device does support software raid 0/1/5 per the manufacturer, I guess I'll be forced to do it manually. Thanks for the info.
OMV doesn't appear to be what I need if it cant run raid on this device
No one said you can't run raid on the device. If you create the array from the command line, you can do everything else from the web interface. I really don't know why you want to though. There is nothing redundant about this board. You can pool disks and use snapraid for redundancy which is a much better idea for arm devices.
Since the device does support software raid 0/1/5 per the manufacturer, I guess I'll be forced to do it manually
Anything "supports" raid when you are using mdadm. That doesn't mean it is a good idea. What is really disappointing about the hat is the hack needed to make the drives look like separate disks (unique serial numbers). The nano pi m4 with quad sata hat is a much better board and is not using USB.
I started to build a UDEV database for USB PATA/SATA bridge controllers that do not pass on the serial number correctly at https://github.com/openmediavault/openmediavault/pull/746. Please help to populate this database, so OMV can ship it out-of-the-box and help other users to do not run into the same problem.
Hi,
in my case (JMicron JM20337 USB PATA/SATA bridge on Orangepi PC2 with OMV5) the generic env ENV{ID_VENDOR}=="JMicron" in the troubleshooting sectiondid not work and I had to change the rule as follows:
CodeKERNEL=="sd*", ATTRS{idVendor}=="152d", ATTRS{idProduct}=="2338", SUBSYSTEMS=="usb", PROGRAM="/root/serial.sh %k", ENV{ID_SERIAL}="USB-%c", ENV{ID_SERIAL_SHORT}="%c"
where idVendor and idProduct are simply coming from lsusb command output
latimeria Could you please run the command udevadm info --query=all --name=/dev/sdX for one of your disks and post the output here.
....sorry I've been away for a long period
root@orangepipc2:~# udevadm info --query=all --name=/dev/sda
P: /devices/platform/soc/1c1c000.usb/usb4/4-1/4-1:1.0/host1/target1:0:0/1:0:0:0/block/sda
N: sda
L: 0
S: disk/by-path/platform-1c1c000.usb-usb-0:1:1.0-scsi-0:0:0:0
S: disk/by-id/usb-WDC_WD50_00AAKB-00H8A0_7D5000AA5B50-0:0
E: DEVPATH=/devices/platform/soc/1c1c000.usb/usb4/4-1/4-1:1.0/host1/target1:0:0/1:0:0:0/block/sda
E: DEVNAME=/dev/sda
E: DEVTYPE=disk
E: MAJOR=8
E: MINOR=0
E: SUBSYSTEM=block
E: USEC_INITIALIZED=40368394
E: ID_VENDOR=WDC_WD50
E: ID_VENDOR_ENC=WDC\x20WD50
E: ID_VENDOR_ID=152d
E: ID_MODEL=00AAKB-00H8A0
E: ID_MODEL_ENC=00AAKB-00H8A0\x20\x20\x20
E: ID_MODEL_ID=2338
E: ID_REVISION=0100
E: ID_SERIAL=WDC_WD50_00AAKB-00H8A0_7D5000AA5B50-0:0
E: ID_SERIAL_SHORT=7D5000AA5B50
E: ID_TYPE=disk
E: ID_INSTANCE=0:0
E: ID_BUS=usb
E: ID_USB_INTERFACES=:080650:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=usb-storage
E: ID_PATH=platform-1c1c000.usb-usb-0:1:1.0-scsi-0:0:0:0
E: ID_PATH_TAG=platform-1c1c000_usb-usb-0_1_1_0-scsi-0_0_0_0
E: ID_PART_TABLE_UUID=000dc561
E: ID_PART_TABLE_TYPE=dos
E: DEVLINKS=/dev/disk/by-path/platform-1c1c000.usb-usb-0:1:1.0-scsi-0:0:0:0 /dev/disk/by-id/usb-WDC_WD50_00AAKB-00H8A0_7D5000AA5B50-0:0
E: TAGS=:systemd:
Alles anzeigen
....and, I'm on OMV 5.5.6-1 and it doesn't work
/etc/udev/rules.d/99-openmediavault-dev-disk-by-id.rules is in place
/lib/udev/serial_id is missing
Should be fixed in openmediavault 5.5.6, see https://github.com/openmediava…4d949b45da8621746b4315378.
I have the same problem with 2 HDs on JMicron controllers which cannot be seen in OMV. I tried the fixes in the rules-files as mentioned above but still no luck.
Any ideas?
I have the same issue with JMicron controllers. Tried all of the above with only partial success. One of 2 HDs is recognised as a disk but not in Smart and not in Encryption plug in. The second disk is not visible anywhere.
Are there any more fixes for JMicorn?
Should be fixed in openmediavault 5.5.6, see https://github.com/openmediava…4d949b45da8621746b4315378.
I am now on OMV 5.5.7 buy still not working, the disk list mask just shows one disk with the wrong serial number ( I have attached a pic above). I will test again the solution that was working posted above.
I am now on OMV 5.5.7 buy still not working, the disk list mask just shows one disk with the wrong serial number ( I have attached a pic above). I will test again the solution that was working posted above.
I can not test it because i do not own such hardware, so someone else MUST contribute a working pull request.
I gave up and swapped the sata controllers to non JMicron. Cost me gbp10. Works perfectly since then. I’d say Just try to avoid JMicron. It’s not compatible and the time is not worth it.
Could anyone please test the pull request https://github.com/openmediavault/openmediavault/pull/843? The UDEV rules had to be more restrictive.
just made a test even if my issue was solved in https://github.com/openmediavault/openmediavault/issues/839
don't merge it please as it screwed up my system again, see below
just made a test even if my issue was solved in https://github.com/openmediavault/openmediavault/issues/839
don't merge it please as it screwed up my system again, see below
Plese become familar with UDEV and try to get it working on your system so that we can fix it correct. I can't do anything without having the hardware.
If you can tell me exactly which rule is applied on your system we can test some modifications of the rule.
# JMicron JM20337 USB PATA/SATA bridge on Orangepi PC2
ACTION=="add", KERNEL=="sd*", SUBSYSTEMS=="usb", \
ATTRS{idVendor}=="152d", ATTRS{idProduct}=="2338", \
ACTION=="add", KERNEL=="sd*", SUBSYSTEM=="block", \
ENV{DEVTYPE}=="disk", \
ATTRS{idVendor}=="152d", \
ATTRS{idProduct}=="2338", \
any reason why the SUBSYSTEM was changed from usb to block?
There is a difference between SUBSYSTEMS and SUBSYSTEM. SUBSYSTEMS searches the devpath upwards for a matching device subsystem name, so IMO ENV{DEVTYPE}=="disk" and SUBSYSTEMS=="usb" will never match. That's why i changed it. Could you please provide the output of udevadm info --query=property --name=/dev/sda --attribute-walk?
As you see here the interesting part is always SUBSYSTEM=block.
# DEVPATH=/devices/platform/soc/soc:usb3-0/12000000.dwc3/xhci-hcd.3.auto/usb4/4-1/4-1:1.0/host0/target0:0:0/0:0:0:0/block/sda
# DEVNAME=/dev/sda
# DEVTYPE=disk
# MAJOR=8
# MINOR=0
# SUBSYSTEM=block
# USEC_INITIALIZED=16854982
# ID_VENDOR=JMicron
# ID_VENDOR_ENC=JMicron\x20
# ID_VENDOR_ID=152d
# ID_MODEL=USB_to_SATA_bridge
# ID_MODEL_ENC=USB\x20to\x20SATA\x20bridge
# ID_MODEL_ID=0578
# ID_REVISION=0105
Alles anzeigen
ok my fault reading
root@orangepipc2:~# udevadm info --query=property --name=/dev/sda --attribute-walk
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/platform/soc/1c1b000.usb/usb3/3-1/3-1:1.0/host0/target0:0:0/0:0:0:0/block/sda':
KERNEL=="sda"
SUBSYSTEM=="block"
DRIVER==""
ATTR{capability}=="50"
ATTR{events}==""
ATTR{stat}==" 2691 3 146396 9778 2 0 16 2 0 7612 9780 0 0 0 0 0 0"
ATTR{size}=="976773168"
ATTR{ro}=="0"
ATTR{events_async}==""
ATTR{discard_alignment}=="0"
ATTR{hidden}=="0"
ATTR{removable}=="0"
ATTR{ext_range}=="256"
ATTR{alignment_offset}=="0"
ATTR{range}=="16"
ATTR{events_poll_msecs}=="-1"
ATTR{inflight}==" 0 0"
looking at parent device '/devices/platform/soc/1c1b000.usb/usb3/3-1/3-1:1.0/host0/target0:0:0/0:0:0:0':
KERNELS=="0:0:0:0"
SUBSYSTEMS=="scsi"
DRIVERS=="sd"
ATTRS{evt_inquiry_change_reported}=="0"
ATTRS{type}=="0"
ATTRS{model}=="00AAKB-00H8A0 "
ATTRS{state}=="running"
ATTRS{queue_type}=="none"
ATTRS{max_sectors}=="240"
ATTRS{iocounterbits}=="32"
ATTRS{iodone_cnt}=="0xc72"
ATTRS{inquiry}==""
ATTRS{evt_media_change}=="0"
ATTRS{evt_capacity_change_reported}=="0"
ATTRS{scsi_level}=="6"
ATTRS{evt_soft_threshold_reached}=="0"
ATTRS{evt_lun_change_reported}=="0"
ATTRS{blacklist}==""
ATTRS{iorequest_cnt}=="0xc72"
ATTRS{queue_depth}=="1"
ATTRS{vendor}=="WDC WD50"
ATTRS{evt_mode_parameter_change_reported}=="0"
ATTRS{eh_timeout}=="10"
ATTRS{device_blocked}=="0"
ATTRS{rev}==" "
ATTRS{ioerr_cnt}=="0x2"
ATTRS{timeout}=="30"
ATTRS{device_busy}=="0"
looking at parent device '/devices/platform/soc/1c1b000.usb/usb3/3-1/3-1:1.0/host0/target0:0:0':
KERNELS=="target0:0:0"
SUBSYSTEMS=="scsi"
DRIVERS==""
looking at parent device '/devices/platform/soc/1c1b000.usb/usb3/3-1/3-1:1.0/host0':
KERNELS=="host0"
SUBSYSTEMS=="scsi"
DRIVERS==""
looking at parent device '/devices/platform/soc/1c1b000.usb/usb3/3-1/3-1:1.0':
KERNELS=="3-1:1.0"
SUBSYSTEMS=="usb"
DRIVERS=="usb-storage"
ATTRS{authorized}=="1"
ATTRS{supports_autosuspend}=="1"
ATTRS{interface}=="MSC Bulk-Only Transfer"
ATTRS{bInterfaceNumber}=="00"
ATTRS{bAlternateSetting}==" 0"
ATTRS{bInterfaceSubClass}=="06"
ATTRS{bInterfaceProtocol}=="50"
ATTRS{bNumEndpoints}=="02"
ATTRS{bInterfaceClass}=="08"
looking at parent device '/devices/platform/soc/1c1b000.usb/usb3/3-1':
KERNELS=="3-1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bcdDevice}=="0100"
ATTRS{devpath}=="1"
ATTRS{tx_lanes}=="1"
ATTRS{speed}=="480"
ATTRS{bDeviceSubClass}=="00"
ATTRS{version}==" 2.00"
ATTRS{idProduct}=="2338"
ATTRS{serial}=="7D5000AA5B50"
ATTRS{rx_lanes}=="1"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{bDeviceClass}=="00"
ATTRS{configuration}=="USB Mass Storage"
ATTRS{bDeviceProtocol}=="00"
ATTRS{bNumInterfaces}==" 1"
ATTRS{maxchild}=="0"
ATTRS{removable}=="unknown"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="c0"
ATTRS{devspec}=="(null)"
ATTRS{busnum}=="3"
ATTRS{idVendor}=="152d"
ATTRS{bConfigurationValue}=="1"
ATTRS{devnum}=="2"
ATTRS{bMaxPower}=="2mA"
ATTRS{bNumConfigurations}=="1"
ATTRS{manufacturer}=="JMicron"
ATTRS{product}=="USB to ATA/ATAPI bridge"
ATTRS{ltm_capable}=="no"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{urbnum}=="9603"
ATTRS{quirks}=="0x0"
looking at parent device '/devices/platform/soc/1c1b000.usb/usb3':
KERNELS=="usb3"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{version}==" 2.00"
ATTRS{bMaxPower}=="0mA"
ATTRS{manufacturer}=="Linux 5.8.16-sunxi64 ehci_hcd"
ATTRS{bmAttributes}=="e0"
ATTRS{authorized}=="1"
ATTRS{urbnum}=="28"
ATTRS{devnum}=="1"
ATTRS{idVendor}=="1d6b"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bDeviceProtocol}=="00"
ATTRS{rx_lanes}=="1"
ATTRS{product}=="EHCI Host Controller"
ATTRS{idProduct}=="0002"
ATTRS{serial}=="1c1b000.usb"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{interface_authorized_default}=="1"
ATTRS{tx_lanes}=="1"
ATTRS{removable}=="unknown"
ATTRS{maxchild}=="1"
ATTRS{devpath}=="0"
ATTRS{bConfigurationValue}=="1"
ATTRS{quirks}=="0x0"
ATTRS{authorized_default}=="1"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bNumConfigurations}=="1"
ATTRS{bcdDevice}=="0508"
ATTRS{ltm_capable}=="no"
ATTRS{speed}=="480"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{bDeviceClass}=="09"
ATTRS{configuration}==""
ATTRS{busnum}=="3"
looking at parent device '/devices/platform/soc/1c1b000.usb':
KERNELS=="1c1b000.usb"
SUBSYSTEMS=="platform"
DRIVERS=="ehci-platform"
ATTRS{companion}==""
ATTRS{uframe_periodic_max}=="100"
ATTRS{driver_override}=="(null)"
looking at parent device '/devices/platform/soc':
KERNELS=="soc"
SUBSYSTEMS=="platform"
DRIVERS==""
ATTRS{driver_override}=="(null)"
looking at parent device '/devices/platform':
KERNELS=="platform"
SUBSYSTEMS==""
DRIVERS==""
Alles anzeigen
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!