-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ZFS device contains corrupted data? #3581
Comments
It sounds as if ZFS initially had some trouble detecting the location of one of your drives. Subsequently it was able to successly locate it during the import. Did the drive names change perhaps? |
None of the drives in this array were modified physically or otherwise intentionally through software. Prior to this problem I peformed a reboot to the system after operating for 152 days which included a kernel update. ZFS also needed to coddled a bit to get working again on the new kernel: see #3580. Other changes include the addition of an H200A RAID card which uses the same chipset as the onboard controller. While in the BIOS configuration they seemed to talk to each other by updating an adapter list. I don't know if this was responsible for the problem or not and I'm not entirely prepared to bring this system down to try and reproduce the error. The array in question which showed as corrupted is connected to the onboard chipset. Also of note is that I'm now using a significantly different BIOS on the RAID card which would not provide an exact duplication of the process. Any thoughts? |
Close as stale. If it's actual - feel free to reopen. |
Upon calling
zpool status
I had a pool which reported:zpool import pool-name
thenzpool status
did not report any errors. Performing azpool export pool-name
and subsequentzpool status
then yielded no errors.Does the pool actually have an error on one of the devices?
The text was updated successfully, but these errors were encountered: