Disk serial number or UUID is not legitimate or unique

Hi, before anyone tells me off for asking a question that is already posted please let me explain.

I have a 4-bay Orico USB3.0 storage unit and when I add a second disk I get the above error. I suspect that this is because it is using a single interface. All of the answers that I find on the forums are related to the error for Roskstor that is running on a VM not a dedicated machine. Really like Rockstor but will have to change other software if I cant resolve this.

@beaglenz First of all welcome to the Rockstor community. Could you please post the output from the following 3 commands separately so that I can see how your external usb caddy is representing the disks within it. If you do the commands on the machine in the configuration that produces the serial warning that would be most helpful.

/usr/bin/lsblk -P -o NAME,MODEL,SERIAL,SIZE,TRAN,VENDOR,HCTL,TYPE,FSTYPE,LABEL,UUID

This is the command that Rockstor uses currently to see what’s what.

And also the following command would be helpful as well:

ls -la /dev/disk/by-id/

and finally

udevadm info --name sdX

where the sdX is a valid name for a drive in the caddy.
What would be great is if you could do this last command for 2 different drives in the caddy (when they are in at the same time), ie 2 drives in caddy and do the last command for each of their names as they appear in disks.

Also a screen grab of the Disk’s page would be great.

N.B. there may be concerns over publishing your drive serial numbers however all we need to see is if they are alike / unique or show up at all. Thanks. So you could obscure the beginning of them all if that worries you.

If you could surround the results with triple back single inverted commas in the forum posting it will help with formatting and readability. ie as I have done here with the commands.

Please also be aware that this kind of hw setup does rather circumvent many of the safeguards that are assumed though and a recent discussion on the linux-btrfs mailing list didn’t come out in favour for this kind of device (sorry bit pushed time wise to look it up and link but will try to do so later). I’m assuming, maybe rather prematurely, that this caddy has one usb cable and talks to all 4 drives through it. In that arrangement all 4 drives can disappear in one go simply through a usb reset so isn’t at all robust from a hardware perspective, or from a btrfs perspective as momentarily all drives will be lost at once. Especially given usb resets are not rare.

Glad you like Rockstor and lets hope we can accommodate you, even given the questions over the hw arrangement.

1 Like

Thanks for the response Philip

Here goes:

/usr/bin/lsblk -P -o NAME,MODEL,SERIAL,SIZE,TRAN,VENDOR,HCTL,TYPE,FSTYPE,LABEL,UUID

NAME=“sda” MODEL=“SanDisk SDSSDHP1” SERIAL=“133654401026” SIZE=“119.2G” TRAN=“sata” VENDOR=“ATA " HCTL=“1:0:0:0” TYPE=“disk” FSTYPE=”" LABEL="" UUID="“
NAME=“sda1” MODEL=”" SERIAL="" SIZE=“500M” TRAN="" VENDOR="" HCTL="" TYPE=“part” FSTYPE=“ext4” LABEL="" UUID=“551db418-de8c-4628-8848-c6f08a8f438e"
NAME=“sda2” MODEL=”" SERIAL="" SIZE=“7.8G” TRAN="" VENDOR="" HCTL="" TYPE=“part” FSTYPE=“swap” LABEL="" UUID=“e846fdf6-d8fb-408c-963d-0e8cec838e44"
NAME=“sda3” MODEL=”" SERIAL="" SIZE=“111G” TRAN="" VENDOR="" HCTL="" TYPE=“part” FSTYPE=“btrfs” LABEL=“rockstor_rockstor” UUID=“be6c3b18-7c45-48b8-9693-6a2ea5e4d138"
NAME=“sdb” MODEL=“42AS " SERIAL=“000000000000” SIZE=“1.8T” TRAN=“usb” VENDOR=“ST320005” HCTL=“3:0:0:0” TYPE=“disk” FSTYPE=”” LABEL="" UUID="“
NAME=“sdc” MODEL=“42AS " SERIAL=“000000000000” SIZE=“1.8T” TRAN=“usb” VENDOR=“ST320005” HCTL=“3:0:0:1” TYPE=“disk” FSTYPE=”” LABEL="" UUID=""

ls -la /dev/disk/by-id/

total 0
drwxr-xr-x 2 root root 240 May 28 10:15 .
drwxr-xr-x 6 root root 120 May 28 10:10 …
lrwxrwxrwx 1 root root 9 May 28 10:12 ata-SanDisk_SDSSDHP128G_133654401026 -> …/…/sda
lrwxrwxrwx 1 root root 10 May 28 10:12 ata-SanDisk_SDSSDHP128G_133654401026-part1 -> …/…/sda1
lrwxrwxrwx 1 root root 10 May 28 10:12 ata-SanDisk_SDSSDHP128G_133654401026-part2 -> …/…/sda2
lrwxrwxrwx 1 root root 10 May 28 10:12 ata-SanDisk_SDSSDHP128G_133654401026-part3 -> …/…/sda3
lrwxrwxrwx 1 root root 9 May 28 10:15 usb-ST320005_42AS_000000000000-0:0 -> …/…/sdb
lrwxrwxrwx 1 root root 9 May 28 10:15 usb-ST320005_42AS_000000000000-0:1 -> …/…/sdc
lrwxrwxrwx 1 root root 9 May 28 10:12 wwn-0x5001b44a2a014c02 -> …/…/sda
lrwxrwxrwx 1 root root 10 May 28 10:12 wwn-0x5001b44a2a014c02-part1 -> …/…/sda1
lrwxrwxrwx 1 root root 10 May 28 10:12 wwn-0x5001b44a2a014c02-part2 -> …/…/sda2
lrwxrwxrwx 1 root root 10 May 28 10:12 wwn-0x5001b44a2a014c02-part3 -> …/…/sda3

udevadm info --name sdb

P: /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/host3/target3:0:0/3:0:0:0/block/sdb
N: sdb
S: disk/by-id/usb-ST320005_42AS_000000000000-0:0
S: disk/by-path/pci-0000:00:14.0-usb-0:1:1.0-scsi-0:0:0:0
E: DEVLINKS=/dev/disk/by-id/usb-ST320005_42AS_000000000000-0:0 /dev/disk/by-path/pci-0000:00:14.0-usb-0:1:1.0-scsi-0:0:0:0
E: DEVNAME=/dev/sdb
E: DEVPATH=/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/host3/target3:0:0/3:0:0:0/block/sdb
E: DEVTYPE=disk
E: ID_BUS=usb
E: ID_INSTANCE=0:0
E: ID_MODEL=42AS
E: ID_MODEL_ENC=42AS\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20
E: ID_MODEL_ID=0539
E: ID_PATH=pci-0000:00:14.0-usb-0:1:1.0-scsi-0:0:0:0
E: ID_PATH_TAG=pci-0000_00_14_0-usb-0_1_1_0-scsi-0_0_0_0
E: ID_REVISION=0X06
E: ID_SERIAL=ST320005_42AS_000000000000-0:0
E: ID_SERIAL_SHORT=000000000000
E: ID_TYPE=disk
E: ID_USB_DRIVER=usb-storage
E: ID_USB_INTERFACES=:080650:
E: ID_USB_INTERFACE_NUM=00
E: ID_VENDOR=ST320005
E: ID_VENDOR_ENC=ST320005
E: ID_VENDOR_ID=152d
E: MAJOR=8
E: MINOR=16
E: SUBSYSTEM=block
E: TAGS=:systemd:
E: USEC_INITIALIZED=9896900

udevadm info --name sdc

P: /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/host3/target3:0:0/3:0:0:1/block/sdc
N: sdc
S: disk/by-id/usb-ST320005_42AS_000000000000-0:1
S: disk/by-path/pci-0000:00:14.0-usb-0:1:1.0-scsi-0:0:0:1
E: DEVLINKS=/dev/disk/by-id/usb-ST320005_42AS_000000000000-0:1 /dev/disk/by-path/pci-0000:00:14.0-usb-0:1:1.0-scsi-0:0:0:1
E: DEVNAME=/dev/sdc
E: DEVPATH=/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/host3/target3:0:0/3:0:0:1/block/sdc
E: DEVTYPE=disk
E: ID_BUS=usb
E: ID_INSTANCE=0:1
E: ID_MODEL=42AS
E: ID_MODEL_ENC=42AS\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20
E: ID_MODEL_ID=0539
E: ID_PATH=pci-0000:00:14.0-usb-0:1:1.0-scsi-0:0:0:1
E: ID_PATH_TAG=pci-0000_00_14_0-usb-0_1_1_0-scsi-0_0_0_1
E: ID_REVISION=0X06
E: ID_SERIAL=ST320005_42AS_000000000000-0:1
E: ID_SERIAL_SHORT=000000000000
E: ID_TYPE=disk
E: ID_USB_DRIVER=usb-storage
E: ID_USB_INTERFACES=:080650:
E: ID_USB_INTERFACE_NUM=00
E: ID_VENDOR=ST320005
E: ID_VENDOR_ENC=ST320005
E: ID_VENDOR_ID=152d
E: MAJOR=8
E: MINOR=32
E: SUBSYSTEM=block
E: TAGS=:systemd:
E: USEC_INITIALIZED=269884689

And lastly the screen grab:

Hi Philip, did some further testing and discovered that the USB bus on the storage unit was faulty. Took your advice and took it back to the store and exchanged it for a proper server case which I am now building and will give Rockstor another go.

Cheers
Nigel

2 Likes