April 21, 20251 yr I recently just moved my unraid drives to new Hardware. Everything seems to work well except occasionally I will get the following errors. Apr 21 12:08:13 Tower move: Cannot stat file /proc/19645/fd/205: Input/output error/. How do I go about troubleshooting this? tower-diagnostics-20250421-1935.zip
April 22, 20251 yr Community Expert Disk1 filesystem is panicking on mount: Apr 21 19:33:59 Tower kernel: VERIFY3(range_tree_space(smla->smla_rt) + sme->sme_run <= smla->smla_sm->sm_size) failed (17222721536 <= 17179869184) Apr 21 19:33:59 Tower kernel: PANIC at space_map.c:405:space_map_load_callback() Suggest backing up and reformatting that disk, but first, and since zfs is detecting data corruption on disk3: Apr 21 19:34:10 Tower emhttpd: pool: disk3 Apr 21 19:34:10 Tower emhttpd: state: ONLINE Apr 21 19:34:10 Tower emhttpd: status: One or more devices has experienced an error resulting in data Apr 21 19:34:10 Tower emhttpd: corruption. Applications may be affected. I would recommend running memtest.
April 25, 20251 yr Author On 4/22/2025 at 3:33 AM, JorgeB said: Disk1 filesystem is panicking on mount: Apr 21 19:33:59 Tower kernel: VERIFY3(range_tree_space(smla->smla_rt) + sme->sme_run <= smla->smla_sm->sm_size) failed (17222721536 <= 17179869184) Apr 21 19:33:59 Tower kernel: PANIC at space_map.c:405:space_map_load_callback() Suggest backing up and reformatting that disk, but first, and since zfs is detecting data corruption on disk3: Apr 21 19:34:10 Tower emhttpd: pool: disk3 Apr 21 19:34:10 Tower emhttpd: state: ONLINE Apr 21 19:34:10 Tower emhttpd: status: One or more devices has experienced an error resulting in data Apr 21 19:34:10 Tower emhttpd: corruption. Applications may be affected. I would recommend running memtest. Can you explain how you arrived at your recommended solutions from the quoted log outputs? I would like to get better at understanding and troubleshooting.
April 25, 20251 yr Community Expert zfs (or btrfs) detesting data corruption is most often the result of bad RAM, the disk1 panic on mount may also be related.
April 26, 20251 yr Author Started memtest and it failed early. Resated and started again. I think the first failure stated unexpected failure in CPU 3. I will post again if either pass after 24hr or a failure before then.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.