I just used the GUI to update from be89d82 to 67b83a7.
On reboot, /mnt/tank wasn't mounted. It's listed in the sidebar, but not in the "View Volumes" list. If I try to import it, I get the message "You already have a volume with same name".
The alert says "WARNING: The volume tank (ZFS) status is UNKNOWN".
zdb -C shows the pool. zfs list doesn't. A reboot didn't fix it. Rolling back to be89d82 didn't fix it. A power cycle didn't fix it.
zdb -C tank says:
WARNING: can't open objset for tank/timemachine
zdb: can't open 'tank': Input/output error
zpool import tank says:
cannot import 'tank': I/O error
Destroy and re-create the pool from
a backup source.
Ew. Not even complaints about bad metadata. These were just test drives (striped), so I'm not actually out any significant data, but it's a little puzzling.
SMART isn't showing any errors for either drive. It's a little surprising to me that there would be such a sudden failure.
Could an unclean reboot nuke the volume like this? (I don't see how it would result in I/O errors...) Is there any way to get more information about which drive is causing problems? Short self-tests passed, and I don't see any detail in /var/log/messages or dmesg about I/O errors anywhere.
On reboot, /mnt/tank wasn't mounted. It's listed in the sidebar, but not in the "View Volumes" list. If I try to import it, I get the message "You already have a volume with same name".
The alert says "WARNING: The volume tank (ZFS) status is UNKNOWN".
zdb -C shows the pool. zfs list doesn't. A reboot didn't fix it. Rolling back to be89d82 didn't fix it. A power cycle didn't fix it.
zdb -C tank says:
WARNING: can't open objset for tank/timemachine
zdb: can't open 'tank': Input/output error
zpool import tank says:
cannot import 'tank': I/O error
Destroy and re-create the pool from
a backup source.
Ew. Not even complaints about bad metadata. These were just test drives (striped), so I'm not actually out any significant data, but it's a little puzzling.
SMART isn't showing any errors for either drive. It's a little surprising to me that there would be such a sudden failure.
Could an unclean reboot nuke the volume like this? (I don't see how it would result in I/O errors...) Is there any way to get more information about which drive is causing problems? Short self-tests passed, and I don't see any detail in /var/log/messages or dmesg about I/O errors anywhere.