Sorry for the slow response on this one. I've went away on holiday and turned it off to ensure no further data loss.
I was under the assumption that like Linux etc disk enumeration doesn't necessarily persist across reboots. So what could happen is:
sata0 - ada0
sata1 - ada1
sata2 - ada2
sata3 - ada3
Disk sata1 dies for whatever reason, lets say the sata cable is faulty, so this happens:
sata0 - ada0
sata1 - dead
sata2 - ada1
sata3 - ada2
I know this is how it work as I actually had a duff SATA cable when using Openfiler. It caused a LOT of headaches as when sata1 reappeared, it would become ada3 etc.
For this reason I used smartctl to dump out the serial number of the failing disk. I could of course have made a mistake, but I'm pretty sure I swapped out the right disk.
Can someone confirms that disk enumeration works like this, and not like Solaris where disk enumeration is always c0t0d1, c0t0d2 etc depending on what channel the disk is connected to?
Also is there a guide to replacing a busted disk for the future?
Cheers....
b0redom
I was under the assumption that like Linux etc disk enumeration doesn't necessarily persist across reboots. So what could happen is:
sata0 - ada0
sata1 - ada1
sata2 - ada2
sata3 - ada3
Disk sata1 dies for whatever reason, lets say the sata cable is faulty, so this happens:
sata0 - ada0
sata1 - dead
sata2 - ada1
sata3 - ada2
I know this is how it work as I actually had a duff SATA cable when using Openfiler. It caused a LOT of headaches as when sata1 reappeared, it would become ada3 etc.
For this reason I used smartctl to dump out the serial number of the failing disk. I could of course have made a mistake, but I'm pretty sure I swapped out the right disk.
Can someone confirms that disk enumeration works like this, and not like Solaris where disk enumeration is always c0t0d1, c0t0d2 etc depending on what channel the disk is connected to?
Also is there a guide to replacing a busted disk for the future?
Cheers....
b0redom