jblackburn
Dabbler
- Joined
- Jul 1, 2012
- Messages
- 13
Hi,
I've got a problem whereby FreeNAS appears to continually reboot, shortly after importing a degraded ZFS volume.
I have an HP Microsever N40L with 4 3TB Seagate drives. Everything was working well for a couple years. I've been keeping it up-to-date and was running 9.2.1.5. I had a drive fail (ada2). I updated my backup (with zfs send | zfs recv) (which took a few hours and did lots of I/O). And powered down freenas (though I forgot to detach the drive in the WebUI).
I replaced the drive with a 4TB drive. Unfortunately shortly after booting up, the WebUI and shell locks up and the system reboots. It did this on loop, and seems to reboot shortly after mounting the pool - I get an email telling me the pool is degraded right before it reboots.
I've tried everything to make it stop rebooting:
1) putting the bad drive back in
2) booting the system with nothing in ada2
3) swapoff -a as soon as it boots up
4) starting fresh re-imaging my USB thumb drive with the latest version
Finally I reimaged the USB drive with 9.2.1.6 and it boots cleanly now. However as soon as I import the zfs pool (using the web ui, or the command line) it reboots shortly after... There's nothing interesting in /var/log/messages. If I don't import the pool it stays up.
Note that I can perform I/O to the raw devices without issue, e.g. :
dd if=/dev/ada3 of=/dev/null
and I did manage to backup the important filesystems before taking it down for the disk replacement - so I *think* the hardware is fine.
As a result, it feels like there's a kernel panic(?) or similar causing it to reboot shortly after mounting the pool degraded. What's the best way to debug this? Should I expect /var/log/messages to persist across reboot?
Many thanks for any help.
Cheers,
James
I've got a problem whereby FreeNAS appears to continually reboot, shortly after importing a degraded ZFS volume.
I have an HP Microsever N40L with 4 3TB Seagate drives. Everything was working well for a couple years. I've been keeping it up-to-date and was running 9.2.1.5. I had a drive fail (ada2). I updated my backup (with zfs send | zfs recv) (which took a few hours and did lots of I/O). And powered down freenas (though I forgot to detach the drive in the WebUI).
I replaced the drive with a 4TB drive. Unfortunately shortly after booting up, the WebUI and shell locks up and the system reboots. It did this on loop, and seems to reboot shortly after mounting the pool - I get an email telling me the pool is degraded right before it reboots.
I've tried everything to make it stop rebooting:
1) putting the bad drive back in
2) booting the system with nothing in ada2
3) swapoff -a as soon as it boots up
4) starting fresh re-imaging my USB thumb drive with the latest version
Finally I reimaged the USB drive with 9.2.1.6 and it boots cleanly now. However as soon as I import the zfs pool (using the web ui, or the command line) it reboots shortly after... There's nothing interesting in /var/log/messages. If I don't import the pool it stays up.
Note that I can perform I/O to the raw devices without issue, e.g. :
dd if=/dev/ada3 of=/dev/null
and I did manage to backup the important filesystems before taking it down for the disk replacement - so I *think* the hardware is fine.
As a result, it feels like there's a kernel panic(?) or similar causing it to reboot shortly after mounting the pool degraded. What's the best way to debug this? Should I expect /var/log/messages to persist across reboot?
Many thanks for any help.
Cheers,
James