ferroresonance
Dabbler
- Joined
- Aug 19, 2016
- Messages
- 21
Hardware:
HP proliant n54l, 16GB Ram 5x 3TB Seagate Barracuda drives setup in Raidz.
FreeNAS Version and build:
FreeNAS-9.10.1-U2 (f045a8b)
Boot Volume mirrored:
devices da1p2 , da0p2 - Both USB's are a Lexar 16GB JumpDrive
FreeNAS Volume and Data Set:
1x Volume using 5x 3TB split into 3 Data sets as windows share
Hi All
This morning i awoke to find that the 35day boot volume scrub had finished and i was left with a checksum error on da0p2 USB. As a cautious person i decided to replaced the drive. I added a new (Exact Model) USB to one of the front USB ports and selected replace and chose the new USB from the front ports, the resilvering took place and completed ok. Now this is where i think the error may lie. I then removed the freshly resilvered USB and placed it in the location of the old failed one (Rear of server). Obviously i had alerts again saying the volume was degraded, i once again chose to replace the missing USB and chose the same USB that had been freshy re-silvered. The re-silvering process finished but i was left with another drive under the mirror-0 which was the one that was resilvered at the front and moved to the back. I chose to detach the listed drive and the alerts disappeared and the boot volume condition is now healthy.
The problem i have now is freeNAS will not boot from the da0p2, but will boot fine from da1p2. After the resilvering process, I shutdown and removed da1p2 to check that da0p2 would boot, after the post test when you would get the freeNAS boot screen i now get a blinking white cursor (like there is not bootable disk). I have set the da0p2 USB as the primary booting device in the bios as i do for da1p2.
What is going on? How do i fix this?
I understand that i should have just removed the failed USB and inserted the new USB in its place and chose replace and selected the new USB. I guess i didnt think at the time and made a mistake
HP proliant n54l, 16GB Ram 5x 3TB Seagate Barracuda drives setup in Raidz.
FreeNAS Version and build:
FreeNAS-9.10.1-U2 (f045a8b)
Boot Volume mirrored:
devices da1p2 , da0p2 - Both USB's are a Lexar 16GB JumpDrive
FreeNAS Volume and Data Set:
1x Volume using 5x 3TB split into 3 Data sets as windows share
Hi All
This morning i awoke to find that the 35day boot volume scrub had finished and i was left with a checksum error on da0p2 USB. As a cautious person i decided to replaced the drive. I added a new (Exact Model) USB to one of the front USB ports and selected replace and chose the new USB from the front ports, the resilvering took place and completed ok. Now this is where i think the error may lie. I then removed the freshly resilvered USB and placed it in the location of the old failed one (Rear of server). Obviously i had alerts again saying the volume was degraded, i once again chose to replace the missing USB and chose the same USB that had been freshy re-silvered. The re-silvering process finished but i was left with another drive under the mirror-0 which was the one that was resilvered at the front and moved to the back. I chose to detach the listed drive and the alerts disappeared and the boot volume condition is now healthy.
The problem i have now is freeNAS will not boot from the da0p2, but will boot fine from da1p2. After the resilvering process, I shutdown and removed da1p2 to check that da0p2 would boot, after the post test when you would get the freeNAS boot screen i now get a blinking white cursor (like there is not bootable disk). I have set the da0p2 USB as the primary booting device in the bios as i do for da1p2.
What is going on? How do i fix this?
I understand that i should have just removed the failed USB and inserted the new USB in its place and chose replace and selected the new USB. I guess i didnt think at the time and made a mistake