Hi,
You guys seem like you have got a clue!
I have a small issue with my GoFlex Net.
The device has got two SATA ports, so I would expect there to be two symlinks under /dev/disk/by-path/ after plugging two drives in, one in each port. Never mind the usb stick on /dev/sda and it's partitions.
The SATA drives appear as /dev/sdb and /dev/sdc but it looks like the symlink "platform-sata_mv.0-scsi-0:0:0:0" is used for both of them and overwritten when I plug the second drive in.
I would expect one of the drives to show as "platform-sata_mv.0-scsi-1:0:0:0", as per ls /sys/class/scsi_disk/.
I assume the symlinks under /dev/disk/by-path/ are created by the kernel, possibly the sata_mv module. Does anyone have a clue what's going on or do you know of someone who could help me figure it out?
I need/want the symlinks to setup software raid locked to the two ports, not to UUIDs or partition labels.
I'm running kernel version 3.3.2 which I found in a .deb somewhere in a dusty corner of the internet.
Regards,
xpress
You guys seem like you have got a clue!
I have a small issue with my GoFlex Net.
The device has got two SATA ports, so I would expect there to be two symlinks under /dev/disk/by-path/ after plugging two drives in, one in each port. Never mind the usb stick on /dev/sda and it's partitions.
root@goflex:~# ls -l /dev/disk/by-path/ total 0 lrwxrwxrwx 1 root root 9 Jan 1 1970 platform-orion-ehci.0-usb-0:1:1.0-scsi-0:0:0:0 -> ../../sda lrwxrwxrwx 1 root root 10 Jan 1 1970 platform-orion-ehci.0-usb-0:1:1.0-scsi-0:0:0:0-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Jan 1 1970 platform-orion-ehci.0-usb-0:1:1.0-scsi-0:0:0:0-part2 -> ../../sda2 lrwxrwxrwx 1 root root 9 Jun 25 22:59 platform-sata_mv.0-scsi-0:0:0:0 -> ../../sdc
The SATA drives appear as /dev/sdb and /dev/sdc but it looks like the symlink "platform-sata_mv.0-scsi-0:0:0:0" is used for both of them and overwritten when I plug the second drive in.
I would expect one of the drives to show as "platform-sata_mv.0-scsi-1:0:0:0", as per ls /sys/class/scsi_disk/.
root@goflex:~# ls -l /sys/class/scsi_disk/ total 0 lrwxrwxrwx 1 root root 0 Jun 25 23:07 0:0:0:0 -> ../../devices/platform/sata_mv.0/ata1/host0/target0:0:0/0:0:0:0/scsi_disk/0:0:0:0 lrwxrwxrwx 1 root root 0 Jun 25 23:07 1:0:0:0 -> ../../devices/platform/sata_mv.0/ata2/host1/target1:0:0/1:0:0:0/scsi_disk/1:0:0:0 lrwxrwxrwx 1 root root 0 Jun 25 23:07 2:0:0:0 -> ../../devices/platform/orion-ehci.0/usb1/1-1/1-1:1.0/host2/target2:0:0/2:0:0:0/scsi_disk/2:0:0:0
I assume the symlinks under /dev/disk/by-path/ are created by the kernel, possibly the sata_mv module. Does anyone have a clue what's going on or do you know of someone who could help me figure it out?
I need/want the symlinks to setup software raid locked to the two ports, not to UUIDs or partition labels.
I'm running kernel version 3.3.2 which I found in a .deb somewhere in a dusty corner of the internet.
root@goflex:~# uname -a Linux goflex 3.3.2-kirkwood-dg #1 Mon Apr 23 17:09:27 CDT 2012 armv5tel GNU/Linux
Regards,
xpress