'Unrecoverable Error' also part of the standard symptoms?
I'm now having this problem on a 1 week old 3 disc RaidZ array of new discs, on a fresh install of 8.2.0-RELEASE-p1 (not an upgrade). Is everyone else getting this full message?:
The volume Z1 (ZFS) status is UNKNOWN: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected.Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'.
(Meanwhile, you can see that the status of volumes in the main volumes page background shows the array as healthy. All the individual discs show as healthy in "Volume Status" as well.)
It's that "unrecoverable error" part that has me most worried. Getting this box together and running has been a very long background project, and I was quite excited to get the RaidZ array up and shared and my data transfered over the network onto what I thought would be a sorely needed, high reliability solution. So this is frustrating. Anyway, how can I locate the file(s) in which the error occured? I don't want the "clear" the error in case that would mean that I won't be able to locate the corrupted file(s), and I'm not going to trust anymore files to this system until I can at least sort that out.
If this helps, here is some detail of the events leading up to the error: Before adding the new discs to the array, I ran WD's "extened" test on each individual, unformatted disc under Windows 7 x64. After running the new install for about a week, in which I put about 2TB onto a (3) 3TB disc RaidZ array, I powered it down and added an additional Intel (on forum recommendation) PCIe NIC alongside my existing DLink PCI NIC (Marvell chipset). I left the Dlink in for possible future link aggregation, but for now I only have garden variety ethernet, so plugged that cable into the Intel NIC and booted back up. I was watching the boot sequence on a monitor, and after it got near the end, some error messages came up too quick to read, and the machine rebooted. The second reboot was stable, but I couldn't get Freenas to recognize a link on the new card, working on a physical keyboard and monitor on the machine. I moved the ethernet cable into the Dlink card, and got back online on that. This is on an old AMD S939 CPU and mobo with 1GB of RAM. Low RAM, I know, but I don't care about the performance nearly as much as the touted reliability of ZFS, and my research on the forums turned up a number of people running small arrays on low RAM.
I have 2GB of brand new RAM that just arrived that I ordered right after the new Intel NIC. I'm going to want to fix the NIC hardware problem before installing new RAM, and I need to fix the ZFS problem before dealing with the NIC problem.
