July 21, 201114 yr Ok, so here's a weird one... I have a drive *outside* of my protected array that I use for processing and downloads (SAB and Sickbeard run from here). On unRAID 4.7, I had this as /dev/sdc and mounted as /mnt/extra After upgrading to 5.0b9, everytime I reboot, this drive gets assigned a different sdX?!?! So far it's been: /dev/sdn, /dev/sdh, /dev/sdf and /dev/sdb What's odd about this is it's mounting some of the arrayed disks as the "extra" disk occasionally then too. Sincerely, Confused in Canada
July 21, 201114 yr Ok, so here's a weird one... I have a drive *outside* of my protected array that I use for processing and downloads (SAB and Sickbeard run from here). On unRAID 4.7, I had this as /dev/sdc and mounted as /mnt/extra After upgrading to 5.0b9, everytime I reboot, this drive gets assigned a different sdX?!?! So far it's been: /dev/sdn, /dev/sdh, /dev/sdf and /dev/sdb What's odd about this is it's mounting some of the arrayed disks as the "extra" disk occasionally then too. Sincerely, Confused in Canada It is all in the timing of the SATA ports being detected and them "responding" to the OS. There is NO control over the sdX assignment and you SHOULD NOT be keying off of it to mount your drive. use disk/by-label or on of the others under /dev/disk/*
July 21, 201114 yr Author Ok, so here's a weird one... I have a drive *outside* of my protected array that I use for processing and downloads (SAB and Sickbeard run from here). On unRAID 4.7, I had this as /dev/sdc and mounted as /mnt/extra After upgrading to 5.0b9, everytime I reboot, this drive gets assigned a different sdX?!?! So far it's been: /dev/sdn, /dev/sdh, /dev/sdf and /dev/sdb What's odd about this is it's mounting some of the arrayed disks as the "extra" disk occasionally then too. Sincerely, Confused in Canada It is all in the timing of the SATA ports being detected and them "responding" to the OS. There is NO control over the sdX assignment and you SHOULD NOT be keying off of it to mount your drive. use disk/by-label or on of the others under /dev/disk/* I was wondering about the timing of that... I feel like a fool now. *blush* When I look under "/disk/by-label" only my unraid shows up there... how do I add an entry there? EDIT: Ok, Google-FU!!! reiserfstune -l yourlabelhere /dev/sdx where: yourlabelhere = the label for the drive, in my case 500G /dev/sdx = the device you want to label, in my case, /dev/sdb Then I modified my /boot/config/go and changed the line: mount -t reiserfs /dev/sdb /mnt/extra to mount -t reiserfs LABEL=500G /mnt/extra ... and now we're good to go. Thanks for the pointer!
July 21, 201114 yr Ok, so here's a weird one... I have a drive *outside* of my protected array that I use for processing and downloads (SAB and Sickbeard run from here). On unRAID 4.7, I had this as /dev/sdc and mounted as /mnt/extra After upgrading to 5.0b9, everytime I reboot, this drive gets assigned a different sdX?!?! So far it's been: /dev/sdn, /dev/sdh, /dev/sdf and /dev/sdb What's odd about this is it's mounting some of the arrayed disks as the "extra" disk occasionally then too. Sincerely, Confused in Canada It is all in the timing of the SATA ports being detected and them "responding" to the OS. There is NO control over the sdX assignment and you SHOULD NOT be keying off of it to mount your drive. use disk/by-label or on of the others under /dev/disk/* I was wondering about the timing of that... I feel like a fool now. *blush* When I look under "/disk/by-label" only my unraid shows up there... how do I add an entry there? EDIT: Ok, Google-FU!!! reiserfstune -l yourlabelhere /dev/sdx where: yourlabelhere = the label for the drive, in my case 500G /dev/sdx = the device you want to label, in my case, /dev/sdb Then I modified my /boot/config/go and changed the line: mount -t reiserfs /dev/sdb /mnt/extra to mount -t reiserfs LABEL=500G /mnt/extra ... and now we're good to go. Thanks for the pointer! Glad my pointer helped you find the answer.
Archived
This topic is now archived and is closed to further replies.