Beiträge von les.warden

Also to note, upon reboot the unit doesn't really reboot because of the pin voltage being held on the HAT. I have to issue reboot, then unplug and replug.

That is another whole thread being worked on github.

I created a new file /etc/udev/rules.d/99-sdTEST.rules and places your rule inside the file.

rebooted.

NOTE: I've been messing with formatting the drives and such so you see the partition changed to dos.

I also noted the drive label disappeared. No biggie.

output of previous run command...

pi@piNAS:~ $ sudo udevadm info --query=all --name=/dev/sda

P: /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda

N: sda

L: 0

S: disk/by-id/usb-ACASIS_Go_To_Final_Lap_1234567890123-0:0

S: disk/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:2:1.0-scsi-0:0:0:0

E: DEVPATH=/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda

E: DEVNAME=/dev/sda

E: DEVTYPE=disk

E: MAJOR=8

E: MINOR=0

E: SUBSYSTEM=block

E: USEC_INITIALIZED=10303707

E: ID_VENDOR=ACASIS

E: ID_VENDOR_ENC=ACASIS\x20\x20

E: ID_VENDOR_ID=1058

E: ID_MODEL=Go_To_Final_Lap

E: ID_MODEL_ENC=Go\x20To\x20Final\x20Lap

E: ID_MODEL_ID=0a10

E: ID_REVISION=8034

E: ID_SERIAL=ACASIS_Go_To_Final_Lap_1234567890123-0:0

E: ID_SERIAL_SHORT=1234567890123

E: ID_TYPE=disk

E: ID_INSTANCE=0:0

E: ID_BUS=usb

E: ID_USB_INTERFACES=:080650:080662:

E: ID_USB_INTERFACE_NUM=00

E: ID_USB_DRIVER=uas

E: ID_PATH=platform-fd500000.pcie-pci-0000:01:00.0-usb-0:2:1.0-scsi-0:0:0:0

E: ID_PATH_TAG=platform-fd500000_pcie-pci-0000_01_00_0-usb-0_2_1_0-scsi-0_0_0_0

E: ID_PART_TABLE_UUID=3475d5cb

E: ID_PART_TABLE_TYPE=dos

E: DEVLINKS=/dev/disk/by-id/usb-ACASIS_Go_To_Final_Lap_1234567890123-0:0 /dev/disk/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:2:1.0-scsi-0:0:0:0

E: TAGS=:systemd:

pi@piNAS:~ $

Zitat von votdev

That's interesting, the device uses the Western Digital vendor ID.

The 4 drives I have installed in the unit are each 2TB WD drives.

Where I ordered the kit...

https://shop.allnetchina.cn/pr…os=4&_sid=8298cd20c&_ss=r

The command output....

pi@piNAS:~ $ sudo udevadm info --query=all --name=/dev/sda

P: /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda

N: sda

L: 0

S: disk/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:2:1.0-scsi-0:0:0:0

S: disk/by-id/usb-ACASIS_Go_To_Final_Lap_1234567890123-0:0

S: disk/by-label/SDA2Tpictures

S: disk/by-uuid/cc08740f-b9db-460f-a89e-9d5fb4b334bd

E: DEVPATH=/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda

E: DEVNAME=/dev/sda

E: DEVTYPE=disk

E: MAJOR=8

E: MINOR=0

E: SUBSYSTEM=block

E: USEC_INITIALIZED=11738857

E: ID_VENDOR=ACASIS

E: ID_VENDOR_ENC=ACASIS\x20\x20

E: ID_VENDOR_ID=1058

E: ID_MODEL=Go_To_Final_Lap

E: ID_MODEL_ENC=Go\x20To\x20Final\x20Lap

E: ID_MODEL_ID=0a10

E: ID_REVISION=8034

E: ID_SERIAL=ACASIS_Go_To_Final_Lap_1234567890123-0:0

E: ID_SERIAL_SHORT=1234567890123

E: ID_TYPE=disk

E: ID_INSTANCE=0:0

E: ID_BUS=usb

E: ID_USB_INTERFACES=:080650:080662:

E: ID_USB_INTERFACE_NUM=00

E: ID_USB_DRIVER=uas

E: ID_PATH=platform-fd500000.pcie-pci-0000:01:00.0-usb-0:2:1.0-scsi-0:0:0:0

E: ID_PATH_TAG=platform-fd500000_pcie-pci-0000_01_00_0-usb-0_2_1_0-scsi-0_0_0_0

E: ID_FS_LABEL=SDA2Tpictures

E: ID_FS_LABEL_ENC=SDA2Tpictures

E: ID_FS_UUID=cc08740f-b9db-460f-a89e-9d5fb4b334bd

E: ID_FS_UUID_ENC=cc08740f-b9db-460f-a89e-9d5fb4b334bd

E: ID_FS_VERSION=1.0

E: ID_FS_TYPE=ext4

E: ID_FS_USAGE=filesystem

E: DEVLINKS=/dev/disk/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:2:1.0-scsi-0:0:0:0 /dev/disk/by-id/usb-ACASIS_Go_To_Final_Lap_1234567890123-0:0 /dev/disk/by-label/SDA2Tpictures /dev/disk/by-uuid/cc08740f-b9db-460f-a89e-9d5fb4b334bd

E: TAGS=:systemd:

pi@piNAS:~ $

Well, guess I hadn't really thought about it in terms of not raiding the drives. I put in 4-2TB drives and thought I'd have a couple sets of RAID1 or partition them up and make a couple RAID10. In watching the SATA HAT videos and reading forums, I suppose it stuck in my mind that having the 4 drives, I should raid them up. So, maybe just allocating them up and making them a shareable NAS might be a way to go? That what you're suggesting? I really wasn't set on RAID. My main goal was to have a location where I could put .jpg photos I take so my wife could access for printing. She's a paper person. RAID would give me some reassurance if a drive failed. That was my thought. I'm always open to suggestions.

Well, back to the drawing board. After all drives are showing up, I went to make a RAID in OMV and none of the drives are made available to use. OMV says USB drives will not be listed because they're too unreliable. Looking at the output above, it appears USB is sprinkled throughout the drive information. My assumption is that's the issue. I'll dig around the forum some to see if it's happened to others. I look at most problems with the mindset of....I can't be the first one this has ever happened to.

Thanks for your help!!!! After applying the NAS Support (optional) patch listed right on https://wiki.radxa.com/ website, all drives are showing up now. Not sure how I just ignored that particular step but time to move forward now. Below is a screenshot of OMV now and the OMV disk management output again. Again, thanks for your quick responses and help. -les

pi@piNAS:~ $ sudo omv-rpc -u admin "diskmgmt" "enumerateDevices" | python3 -m json.tool

[

{

"devicename": "mmcblk0",

"canonicaldevicefile": "/dev/mmcblk0",

"devicefile": "/dev/disk/by-id/mmc-USD00_0x64a5a22c",

"devicelinks": [

"/dev/disk/by-id/mmc-USD00_0x64a5a22c",

"/dev/disk/by-path/platform-fe340000.emmc2"

],

"model": "",

"size": "63281561600",

"description": "n/a [/dev/mmcblk0, 58.93 GiB]",

"vendor": "",

"serialnumber": "",

"israid": false,

"isroot": true

},

{

"devicename": "sda",

"canonicaldevicefile": "/dev/sda",

"devicefile": "/dev/disk/by-id/usb-USB-WD-WXD2E10DS03W",

"devicelinks": [

"/dev/disk/by-id/usb-USB-WD-WXD2E10DS03W",

"/dev/disk/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:2:1.0-scsi-0:0:0:0",

"/dev/disk/by-uuid/0388bbe9-dc16-42fc-bddb-19a2cd511d92"

],

"model": "",

"size": "2000398934016",

"description": "n/a [/dev/sda, 1.81 TiB]",

"vendor": "ACASIS",

"serialnumber": "WD-WXD2E10DS03W",

"israid": false,

"isroot": false

},

{

"devicename": "sdb",

"canonicaldevicefile": "/dev/sdb",

"devicefile": "/dev/disk/by-id/usb-USB-WD-WXB2E105PV0C",

"devicelinks": [

"/dev/disk/by-id/usb-USB-WD-WXB2E105PV0C",

"/dev/disk/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:2:1.0-scsi-0:0:0:1",

"/dev/disk/by-uuid/442c2be4-8c77-42ea-a5f6-0df1b5a6278e"

],

"model": "",

"size": "2000398934016",

"description": "n/a [/dev/sdb, 1.81 TiB]",

"vendor": "ACASIS",

"serialnumber": "WD-WXB2E105PV0C",

"israid": false,

"isroot": false

},

{

"devicename": "sdc",

"canonicaldevicefile": "/dev/sdc",

"devicefile": "/dev/disk/by-id/usb-USB-WD-WXD2E10F0SNR",

"devicelinks": [

"/dev/disk/by-id/usb-USB-WD-WXD2E10F0SNR",

"/dev/disk/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1:1.0-scsi-0:0:0:0",

"/dev/disk/by-uuid/3a57b3be-3930-4345-9267-e7161d80bc12"

],

"model": "",

"size": "2000398934016",

"description": "n/a [/dev/sdc, 1.81 TiB]",

"vendor": "ACASIS",

"serialnumber": "WD-WXD2E10F0SNR",

"israid": false,

"isroot": false

},

{

"devicename": "sdd",

"canonicaldevicefile": "/dev/sdd",

"devicefile": "/dev/disk/by-id/usb-USB-WD-WXD2E109CLFD",

"devicelinks": [

"/dev/disk/by-id/usb-USB-WD-WXD2E109CLFD",

"/dev/disk/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1:1.0-scsi-0:0:0:1",

"/dev/disk/by-uuid/cb8f6583-d90a-4781-8fcb-a12350e48201"

],

"model": "",

"size": "2000398934016",

"description": "n/a [/dev/sdd, 1.81 TiB]",

"vendor": "ACASIS",

"serialnumber": "WD-WXD2E109CLFD",

"israid": false,

"isroot": false

}

]

pi@piNAS:~ $

It does appear the serial numbers are the same and the vendors are mis-identified. I looked at what geaves recommended and I will give that a try also. Here's the output.....

pi@piNAS:~ $ sudo omv-rpc -u admin "diskmgmt" "enumerateDevices" | python3 -m json.tool

[

{

"devicename": "mmcblk0",

"canonicaldevicefile": "/dev/mmcblk0",

"devicefile": "/dev/disk/by-id/mmc-USD00_0x64a5a22c",

"devicelinks": [

"/dev/disk/by-id/mmc-USD00_0x64a5a22c",

"/dev/disk/by-path/platform-fe340000.emmc2"

],

"model": "",

"size": "63281561600",

"description": "n/a [/dev/mmcblk0, 58.93 GiB]",

"vendor": "",

"serialnumber": "",

"israid": false,

"isroot": true

},

{

"devicename": "sda",

"canonicaldevicefile": "/dev/sda",

"devicefile": "/dev/disk/by-id/usb-ACASIS_Go_To_Final_Lap_1234567890123-0:0",

"devicelinks": [

"/dev/disk/by-id/usb-ACASIS_Go_To_Final_Lap_1234567890123-0:0",

"/dev/disk/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:2:1.0-scsi-0:0:0:0",

"/dev/disk/by-uuid/0388bbe9-dc16-42fc-bddb-19a2cd511d92"

],

"model": "",

"size": "2000398934016",

"description": "n/a [/dev/sda, 1.81 TiB]",

"vendor": "ACASIS",

"serialnumber": "1234567890123",

"israid": false,

"isroot": false

},

{

"devicename": "sdb",

"canonicaldevicefile": "/dev/sdb",

"devicefile": "/dev/disk/by-id/usb-ACASIS_Go_To_Final_Lap_1234567890123-0:1",

"devicelinks": [

"/dev/disk/by-id/usb-ACASIS_Go_To_Final_Lap_1234567890123-0:1",

"/dev/disk/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:2:1.0-scsi-0:0:0:1",

"/dev/disk/by-uuid/442c2be4-8c77-42ea-a5f6-0df1b5a6278e"

],

"model": "",

"size": "2000398934016",

"description": "n/a [/dev/sdb, 1.81 TiB]",

"vendor": "ACASIS",

"serialnumber": "1234567890123",

"israid": false,

"isroot": false

},

{

"devicename": "sdc",

"canonicaldevicefile": "/dev/sdc",

"devicefile": "/dev/disk/by-id/usb-ACASIS_Go_To_Final_Lap_1234567890123-0:0",

"devicelinks": [

"/dev/disk/by-id/usb-ACASIS_Go_To_Final_Lap_1234567890123-0:0",

"/dev/disk/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1:1.0-scsi-0:0:0:0",

"/dev/disk/by-uuid/3a57b3be-3930-4345-9267-e7161d80bc12"

],

"model": "",

"size": "2000398934016",

"description": "n/a [/dev/sdc, 1.81 TiB]",

"vendor": "ACASIS",

"serialnumber": "1234567890123",

"israid": false,

"isroot": false

},

{

"devicename": "sdd",

"canonicaldevicefile": "/dev/sdd",

"devicefile": "/dev/disk/by-id/usb-ACASIS_Go_To_Final_Lap_1234567890123-0:1",

"devicelinks": [

"/dev/disk/by-id/usb-ACASIS_Go_To_Final_Lap_1234567890123-0:1",

"/dev/disk/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1:1.0-scsi-0:0:0:1",

"/dev/disk/by-uuid/cb8f6583-d90a-4781-8fcb-a12350e48201"

],

"model": "",

"size": "2000398934016",

"description": "n/a [/dev/sdd, 1.81 TiB]",

"vendor": "ACASIS",

"serialnumber": "1234567890123",

"israid": false,

"isroot": false

}

]

pi@piNAS:~ $

Nevy or ryecoaaron, can you expand on your exact steps to install the other kernel. My OMV 5 install recognizes 2of4 but the Debian system see them all via Command Line. I have another post in here about it.

I read this from another pinned post by yourself. If true, how do I keep Linux from mounting the sdX drives so OMV can get them registered in its database?

Problem #2: I mounted the drive using the command line or GUI tool and I can't pick that drive in the shared folder device dropdown.

Solution #2: Never mount a drive with anything other than the OMV web interface. This creates the necessary database entries to populate the device dropdown.

Here they are..attached.

Hello everyone. First post.

Just built a 4 sata-drive NAS. First time using Raspberry Pi, etc. These are the components

Raspberry Pi 4B Ver1.2

Allnet.china Raspberry Pi SATA NAS KIT which includes the Hats.

4-2TB WD Blue SATA drives

I've followed the guidelines from Novaspirit Tech YouTube video and pretty much everything has went according to plan.

My issue is the following:

When I'm on the CLI, I can see all the drives, I can format the drives, I can partition the erives, etc.

When I access the drives via OMV, I only see 2 of the 4 drives.

What I've done:

Started from scratch on the software.

Formatted the SD with Raspberry Pi OS Lite (Debian based, headless).

Ran through all the software upgrades.

Reinstalled OMV 5

I've attached a picture of the cli vs. the OMV.

I'm hoping that since this my first project with RP4 and OMV, that it's really something simple I've overlooked. Thanks in advance for any feedback.