StrangeWill
Cadet
- Joined
- May 5, 2016
- Messages
- 4
So far I've received two kernel panics since updating, they both show the same error:
The Backup vdev is a single disk that is used by a VM. These panics are causing the entire system to reboot and the VMs to freak out for a bit while it comes back up. The drive is a SATA3 disk that isn't showing any errors or anything (SMART tests pass).
Currently on FreeNAS-9.10.1-U2 (f045a8b), did anything change with drive response times that may cause this? It is heavily loaded for a single disk (for now I'll back up directly to the offsite device that is part of this backup chain).
Code:
[root@freenas-01] /data/crash# vi info.2 Dump header from device /dev/dumpdev Architecture: amd64 Architecture Version: 1 Dump Length: 303616B (0 MB) Blocksize: 512 Dumptime: Mon Oct 31 14:55:02 2016 Hostname: freenas-01 Magic: FreeBSD Text Dump Version String: FreeBSD 10.3-STABLE #0 r295946+0ea9076(9.10-STABLE): Mon Oct 3 06:51:23 UTC 2016 root@gauntlet:/freenas-9.10-releng/_BE/objs/freenas-9.10-releng/_BE/os/sys/F reeNAS.amd64 Panic String: I/O to pool 'Backup' appears to be hung on vdev guid 17134512670 929153145 at '/dev/gptid/e96d289f-80f8-11e5-a467-002590f58ff4'. Dump Parity: 751047731 Bounds: 2 Dump Status: good
The Backup vdev is a single disk that is used by a VM. These panics are causing the entire system to reboot and the VMs to freak out for a bit while it comes back up. The drive is a SATA3 disk that isn't showing any errors or anything (SMART tests pass).
Currently on FreeNAS-9.10.1-U2 (f045a8b), did anything change with drive response times that may cause this? It is heavily loaded for a single disk (for now I'll back up directly to the offsite device that is part of this backup chain).