February 19, 20233 yr One of my drives just failed on me. It occured when I tried to start a Windows 10 VM (which didnt start and came up with an error message) - possibly related? I tried to reboot the system, but it locked up and I had to force power it off and restart. A load of error messages came up on the reboot, but it came up with a green message once I got to the GUI. I have also successfully rebooted it since the drive failed and think the only error is the failed drive - I did not see the same sort of error messages on the second restart. I ran a short smart test on the failed drive and no errors came back . Output attached. Should i run an extended smart test? I am going to address the VM issue seperatly as it was only used for testing so nothing lost. However I would be greatful for advise on next steps. Should I rebuild the array from the parity OR should I rebuild the parity on basis drive shows as disabled as it is out of sync (i.e. create a new array configuration)? unraid1-smart-20230219-0025.zip
February 19, 20233 yr Community Expert Better if you get diagnostics before rebooting, and preferably with the array started.
February 19, 20233 yr Author Hi, Diagnostics attached with array started. Also attached data from my syslog server which was running when drive failed. unraid1-diagnostics-20230219-0115.zip 2023-02-19.txt Edited February 19, 20233 yr by ezzys Uploaded latest syslog file
February 19, 20233 yr Community Expert The only thing I see in that syslog related to the disabled disk <4>Feb 19 00:03:20 UnRAID1 kernel: md: disk1 write error, sector=1954992192 <4>Feb 19 00:03:20 UnRAID1 kernel: md: disk0 write error, sector=1954992192 <1>Feb 19 00:03:20 UnRAID1 kernel: XFS (md1): log I/O error -5 <1>Feb 19 00:03:20 UnRAID1 kernel: XFS (md1): Filesystem has been shut down due to log error (0x2). <1>Feb 19 00:03:20 UnRAID1 kernel: XFS (md1): Please unmount the filesystem and rectify the problem(s). What is your syslog server and what do the numbers at the beginning of each line mean in your syslog server? Don't remember seeing that "Filesystem shut down" in other syslogs. I suspect it has something to do with failing to write filesystem metadata. It apparently failed to write parity at the same time, but it didn't get disabled since it had already disabled disk1. Not clear whether this was a disk problem, or a problem elsewhere. SMART for both looks OK. Both disks are on the same controller, but other disks are as well. Maybe these just happened to be the disks being written. Emulated disk1 is mounted, but I wonder if it might not be a good idea to check filesystem on emulated disk1 before rebuilding.
February 19, 20233 yr Community Expert Strange a write error for two disks at the same time without any controller related error before. 10 hours ago, trurl said: Don't remember seeing that "Filesystem shut down" in other syslogs. I suspect it has something to do with failing to write filesystem metadata. It apparently failed to write parity at the same time, but it didn't get disabled since it had already disabled disk1. Yep, that would be the reason, since it failed to write to parity it can't emulate the disk1 filesystem.
February 19, 20233 yr Author Thanks both, I ran "check file system" on disabled disk 1 - see below: Quote Phase 1 - find and verify superblock... - block cache size set to 1417872 entries Phase 2 - using internal log - zero log... zero_log: head block 1477701 tail block 1477701 - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - agno = 16 - agno = 17 - agno = 18 - agno = 19 - agno = 20 - agno = 21 - agno = 22 - agno = 23 - agno = 24 - agno = 25 - agno = 26 - agno = 27 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 3 - agno = 2 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - agno = 16 - agno = 17 - agno = 18 - agno = 19 - agno = 20 - agno = 21 - agno = 22 - agno = 23 - agno = 24 - agno = 25 - agno = 26 - agno = 27 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - agno = 16 - agno = 17 - agno = 18 - agno = 19 - agno = 20 - agno = 21 - agno = 22 - agno = 23 - agno = 24 - agno = 25 - agno = 26 - agno = 27 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. XFS_REPAIR Summary Sun Feb 19 12:24:03 2023 Phase Start End Duration Phase 1: 02/19 12:22:57 02/19 12:22:57 Phase 2: 02/19 12:22:57 02/19 12:22:58 1 second Phase 3: 02/19 12:22:58 02/19 12:23:39 41 seconds Phase 4: 02/19 12:23:39 02/19 12:23:39 Phase 5: Skipped Phase 6: 02/19 12:23:39 02/19 12:24:03 24 seconds Phase 7: 02/19 12:24:03 02/19 12:24:03 Total run time: 1 minute, 6 second It looks okay? Should I simply create a new array configuration and and rebuild parity? Edited February 19, 20233 yr by ezzys provide output from check disk
February 19, 20233 yr Community Expert If the emulated disk is mounting and contents look correct we usually recommend rebuilding the disk instead, it won't take longer than rebuilding parity.
February 19, 20233 yr Author Okay thanks - my approach was to use disk 1 that was disabled for the rebuild. Given it is not showing any errors does that sound okay? Also how to I do that - the disabled disk is not showing as an unassigned device nor when the array is started does it let me select that disk? I assume becuase it is mounted. Do I need to disconnect the disabled drive and reboot and then readd the drive in on a second reboot?
February 19, 20233 yr Community Expert Solution https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself
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.