/dev/null
[H]F Junkie
- Joined
- Mar 31, 2001
- Messages
- 15,182
Hey guys,
I think this is a better forum than storage for my issue, as I think this is more of a FreeBSD question than straight FreeNAS.
Story so far:
I have a freenas 11.2 setup with a DL380G6 and an MSA60. This setup has been working very well for a very long time.
Yesterday my MSA60 went offline completely & so did my entire pool (2 vdevs of raidz2, all disks exist in the MSA60). I tried to reboot my FreeNAS box via CLI but it hung so I hard powered off.
The boot drives are a ZFS mirror that are LOCAL storage inside the DL380 G6, not in the MSA60.
Now when it tries to boot, the DL380 G6 goes into a boot loop. It no longer boots as if it can't find a boot sector on either of the ssds in the freenas-boot pool. As a troubleshooting step, I booted a FreeNAS livecd and dropped to a shell. I noticed that my ssds gpt were "corrupted" (from gpart show) and a "gpart recover <disk>" seemed to fix this.
I was then able to "zpool import -f freenas-boot" and scrub it. Everything looks good. A ZFS list shows what looks like OS files.
Howvever, the system still doesn't boot.
So I guess I have 2 issues:
1) Why did the MSA60 go offline?
2) Why was the system then unbootable even though "freenas-boot" pool is on internal, locally attached storage?
I think I need to fix #2 & then #1.
I have a few ideas to recover
Idea #1
0) Boot FreeNAS livecd & mount the filesystem(s) on SSD(s) manually to recover config data.
q1) Where is the config data? If I can mount the filesystems I'm fine copying it somewhere temporarily.
1) Unplug all disks
2) Install 2 new SSDS and install FreeNAS
3) Re-import pool
4) Restore config data from step #0
5) Re-attach MSA60.
Idea #2
0) Figure out how to restore boot sector to existing SSDS and try to boot.
1) Once booting, shut down & then troubleshoot the MSA60
Anyone run into an issue like this? What path would you take to fix this?
I think this is a better forum than storage for my issue, as I think this is more of a FreeBSD question than straight FreeNAS.
Story so far:
I have a freenas 11.2 setup with a DL380G6 and an MSA60. This setup has been working very well for a very long time.
Yesterday my MSA60 went offline completely & so did my entire pool (2 vdevs of raidz2, all disks exist in the MSA60). I tried to reboot my FreeNAS box via CLI but it hung so I hard powered off.
The boot drives are a ZFS mirror that are LOCAL storage inside the DL380 G6, not in the MSA60.
Now when it tries to boot, the DL380 G6 goes into a boot loop. It no longer boots as if it can't find a boot sector on either of the ssds in the freenas-boot pool. As a troubleshooting step, I booted a FreeNAS livecd and dropped to a shell. I noticed that my ssds gpt were "corrupted" (from gpart show) and a "gpart recover <disk>" seemed to fix this.
I was then able to "zpool import -f freenas-boot" and scrub it. Everything looks good. A ZFS list shows what looks like OS files.
Howvever, the system still doesn't boot.
So I guess I have 2 issues:
1) Why did the MSA60 go offline?
2) Why was the system then unbootable even though "freenas-boot" pool is on internal, locally attached storage?
I think I need to fix #2 & then #1.
I have a few ideas to recover
Idea #1
0) Boot FreeNAS livecd & mount the filesystem(s) on SSD(s) manually to recover config data.
q1) Where is the config data? If I can mount the filesystems I'm fine copying it somewhere temporarily.
1) Unplug all disks
2) Install 2 new SSDS and install FreeNAS
3) Re-import pool
4) Restore config data from step #0
5) Re-attach MSA60.
Idea #2
0) Figure out how to restore boot sector to existing SSDS and try to boot.
1) Once booting, shut down & then troubleshoot the MSA60
Anyone run into an issue like this? What path would you take to fix this?