Help Requested with Error Report

[ClownFeet]

So, what is going on here?

Yggdrasil.192.168.2.177 changes in mounted filesystems:
8c8
< freenas-boot/ROOT/FreeNAS-9.3-STABLE-201503270027 / zfs rw,noatime,nfsv4acls 0 0
---
> freenas-boot/ROOT/FreeNAS-9.3-STABLE-201504100216 / zfs rw,noatime,nfsv4acls 0 0
Yggdrasil.192.168.2.177 kernel log messages:
> vboxdrv: fAsync=0 offMin=0x35c offMax=0xdf4
> pid 2014 (syslog-ng), uid 0: exited on signal 6 (core dumped)
> (da2:mps0:0:2:0): READ(10). CDB: 28 00 30 9f 14 e0 00 00 88 00
> (da2:mps0:0:2:0): CAM status: SCSI Status Error
> (da2:mps0:0:2:0): SCSI status: Check Condition
> (da2:mps0:0:2:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error)
> (da2:mps0:0:2:0): Info: 0x309f14f8
> (da2:mps0:0:2:0): Error 5, Unretryable error
> pid 3906 (syslog-ng), uid 0: exited on signal 6 (core dumped)
> GEOM_ELI: Device da2p1.eli destroyed.
> FreeBSD 9.3-RELEASE-p13 #3 r281084+fbfa186: Thu Apr 9 19:18:25 PDT 2015
> CPU: Intel(R) Core(TM) i3-2130 CPU @ 3.40GHz (3400.09-MHz K8-class CPU)
> avail memory = 33129824256 (31595 MB)
> SMP: AP CPU #2 Launched!
> Timecounter "TSC-low" frequency 1700046116 Hz quality 1000
> Trying to mount root from zfs:freenas-boot/ROOT/FreeNAS-9.3-STABLE-201504100216 []...
> vboxdrv: fAsync=0 offMin=0x318 offMax=0xe10
> pid 2016 (syslog-ng), uid 0: exited on signal 6 (core dumped)
-- End of security output --

 

[BigDave]

check your boot device via the GUI.

 

[BigDave]

On second thought, please post results of # zpool status

 

[cyberjock]

On second thought, please post results of # zpool status

Eh, skip that. Post a debug file. The zpool status will be in there. ;)


For all of you that are regulars on the forum, you ever look at the debug files? There's tons of stuff in there that we use for TrueNAS diagnosis. If you don't use it, I'd recommend you check it out. You use it a few times and you'll be in love with the debug files.

 

[ClownFeet]

These instructions for getting a debug file no longer work: The FreeNAS® GUI provides an option to save debugging information to a text file using System → Settings → Advanced → Save Debug.

So I opened a terminal window and did a debug on the boot volume. This came up: List of Checksum Mismatches:

/conf/base/etc/resolv.conf

In the GUI, my boot volume status lists as good:

Boot Volume Condition: HEALTHY

Last Scrub Run on: Mon Mar 30 03:47:56 2015

Size: 7.4 GiB

Used: 3.1 GiB (41%)

Scrub

Status: Completed

Errors: 0 Repaired: 64K Date: Sun Apr 5 03:25:31 2015

Jormungandr 0 0 0 ONLINE

raidz2-0 0 0 0 ONLINE

da3p2 0 0 0 ONLINE

da2p2 0 0 0 ONLINE

da1p2 0 0 0 ONLINE

da0p2 0 0 0 ONLINE

ada5p2 0 0 0 ONLINE

ada4p2 0 0 0 ONLINE

ada3p2 0 0 0 ONLINE

ada2p2 0 0 0 ONLINE

ada1p2 0 0 0 ONLINE

ada0p2 0 0 0 ONLINE


What next?

 

[SweetAndLow]

These instructions for getting a debug file no longer work: The FreeNAS® GUI provides an option to save debugging information to a text file using System → Settings → Advanced → Save Debug.

So I opened a terminal window and did a debug on the boot volume. This came up: List of Checksum Mismatches:

/conf/base/etc/resolv.conf

In the GUI, my boot volume status lists as good:

Boot Volume Condition: HEALTHY

Last Scrub Run on: Mon Mar 30 03:47:56 2015

Size: 7.4 GiB

Used: 3.1 GiB (41%)

Scrub

Status: Completed

Errors: 0 Repaired: 64K Date: Sun Apr 5 03:25:31 2015

Jormungandr 0 0 0 ONLINE

raidz2-0 0 0 0 ONLINE

da3p2 0 0 0 ONLINE

da2p2 0 0 0 ONLINE

da1p2 0 0 0 ONLINE

da0p2 0 0 0 ONLINE

ada5p2 0 0 0 ONLINE

ada4p2 0 0 0 ONLINE

ada3p2 0 0 0 ONLINE

ada2p2 0 0 0 ONLINE

ada1p2 0 0 0 ONLINE

ada0p2 0 0 0 ONLINE


What next?

The directions for the debug file work when freenas was used to create your pool. But since it looks like you didn't use freenas to create your pool you are going to have a tough time using the GUI. I suggest rebuilding your pool so it actually works correctly. The error you're seeing has been fixed in an update.

 

[danb35]

These instructions for getting a debug file no longer work: The FreeNAS® GUI provides an option to save debugging information to a text file using System → Settings → Advanced → Save Debug.

Where did you get those instructions, and what do you mean by "no longer work"? If that's from the current manual, it needs to be fixed--the current path is System -> Advanced -> Save Debug (there's no "settings" any more). If you found the button but it doesn't create and save the debug file (and it takes a little while to do so), what happens when you try?

What do you mean when you say you "did a debug on the boot volume"? Did you use the freenas-debug utility? See http://doc.freenas.org/9.3/freenas_cli.html?highlight=debug#freenas-debug if you want to use it from the command line.

 

[ClownFeet]

"System -> Advanced -> Save Debug" - Ok. Found it. Yes, manual has old path.

Debug file is attached.

Also received a new error today:

Yggdrasil.192.168.2.177 kernel log messages:
> ugen1.6: <CP1350PFCLCD> at usbus1 (disconnected)
> ugen1.6: <CP1350PFCLCD> at usbus1
> ugen1.6: <CP1350PFCLCD> at usbus1 (disconnected)
> ugen1.6: <CP1350PFCLCD> at usbus1
> ugen1.6: <CP1350PFCLCD> at usbus1 (disconnected)
> ugen1.6: <CP1350PFCLCD> at usbus1
> ugen1.6: <CP1350PFCLCD> at usbus1 (disconnected)
> ugen1.6: <CP1350PFCLCD> at usbus1
> ugen1.6: <CP1350PFCLCD> at usbus1 (disconnected)
> ugen1.6: <CP1350PFCLCD> at usbus1
> ugen1.6: <CP1350PFCLCD> at usbus1 (disconnected)
> ugen1.6: <CP1350PFCLCD> at usbus1
-- End of security output --

 

[danb35]

"System -> Advanced -> Save Debug" - Ok. Found it. Yes, manual has old path.

Which manual, and where? If you're using an old (9.2.x or before) manual, that's on you--things change. If that's in the current manual (I've looked but couldn't find it--but the search feature is clearly missing some stuff), then filing a bug report would likely get it fixed in short order. A link to where you're seeing that path would be helpful.

 

[ClownFeet]

Link:

http://olddoc.freenas.org/index.php/Freenas-debug

So, clearly deprecated. Old instructions. That's on me.

In other news, does anybody know what the error messages are?

 

[danb35]

The original post looks primarily like your system rebooted after installing an update. That's normal. The SCSI Status Error isn't normal, but not a major concern--you might want to check the cable and power connections for da2, possibly replace the cable if you have a spare.

The more recent errors look like a flaky connection to your UPS. Check that the cable is connected securely, or maybe try replacing that cable.