Ian Bennett
Dabbler
- Joined
- Jun 10, 2016
- Messages
- 11
This might have been answered elsewhere, but I've searched the forum and can't find anything. OK, here we go...
Installed fresh 9.10.2-U1 onto a pair of mirrored Sandisk Cruiser Fit 16GB devices, all worked fine and status shows device names for 'freenas-boot/mirror-0' as da0p2 and da1p2, exactly as expected. I then added drives, created volumes, shared out the data via AFP and all works sweet as a nut.
I need to run some automatic backup scripts over night which write some data to an external USB drive containing a UFS file system. Initially the USB drive gets a /dev/da2 device file name, which makes sense. The interesting part happens when the machine is restarted. If the USB drive is attached to a rear USB port then it gets alloacted a /dev/da0 device file name and the Sandisk Cruiser USB boot devices get /dev/da1 and /dev/da2. Everything works ok, but that change of device file name causes some of my scripts some issues! Even more interestingly, if I attach the USB drive to one of the front ports then it gets a /dev/da2 name again and the boot devices are back to /dev/da0 and /dev/da1. However, using the front ports means that stray hands and feet can catch cables leading to possible damaged USB drives!
I'd like my two USB boot devices to ALWAYS have the da0/da1 device file names, regardless of whether another USB drive is connected. Now, I could (and probably should!) beef up the scripts to cope with the situation but, for now, is there a way that I can force the boot device files names to always be consistent?
I've now tested this on both a new Dell T20 and an old HP Proliant, both exhibited the exact same behaviour as described above.
Installed fresh 9.10.2-U1 onto a pair of mirrored Sandisk Cruiser Fit 16GB devices, all worked fine and status shows device names for 'freenas-boot/mirror-0' as da0p2 and da1p2, exactly as expected. I then added drives, created volumes, shared out the data via AFP and all works sweet as a nut.
I need to run some automatic backup scripts over night which write some data to an external USB drive containing a UFS file system. Initially the USB drive gets a /dev/da2 device file name, which makes sense. The interesting part happens when the machine is restarted. If the USB drive is attached to a rear USB port then it gets alloacted a /dev/da0 device file name and the Sandisk Cruiser USB boot devices get /dev/da1 and /dev/da2. Everything works ok, but that change of device file name causes some of my scripts some issues! Even more interestingly, if I attach the USB drive to one of the front ports then it gets a /dev/da2 name again and the boot devices are back to /dev/da0 and /dev/da1. However, using the front ports means that stray hands and feet can catch cables leading to possible damaged USB drives!
I'd like my two USB boot devices to ALWAYS have the da0/da1 device file names, regardless of whether another USB drive is connected. Now, I could (and probably should!) beef up the scripts to cope with the situation but, for now, is there a way that I can force the boot device files names to always be consistent?
I've now tested this on both a new Dell T20 and an old HP Proliant, both exhibited the exact same behaviour as described above.