Hi,

 

I physical installed a new 8TB disk in Unraid server (But did not add to the array) and also took the time to lightly cable tie a few sata cable more neatly. When first powering up the server I then noticed that Disk 5 was not available and thought I may have knocked a cable lose so powered down and checked and push on a few connectors to ensure seated. I power up and disk 5 was available and the array started with out issue.

 

I then started a parity with check correct errors ticked. After checking back after around 20 minutes there appeared to lots of party errors, I stopped the party check. 32196539 party errors are show in the party history.

At this point I wondered if bunching a number sata cable together had caused the issue and powered down to remove the cable ties, the cables were not connect to disk 5.

After powering up again I restarted the parity check but this time after a few minutes disk 5 showed read errors, I then powered down and swapped the sata cable (connected to the motherboard) to a spare sata cable connected to a another a pci card rather than the motherboard. Once |I then powered up disk 5 showed 'XFS Unmountable: Unsupported or no file system'

I tried swapping to another spare sata cable and then back to the original cable the disk had always been connected too but the error on the drive remains the same.

 

At no time did I try and add the new 8TB disk to the array, I also unplugged the new disk just to ensure this wasn't causing any issues.

When performing the first party check I also used the 'Fix Common Problem' plugin but stopped using this when I noticed that writing was also taking place while the party check was being performed.

After looking at the Parity History there looks to have been several short party check initiated over the last few months also showing parity errors, possibly this happed automatically and were cancelled when I shutdown the server.

Disk 5 was showing 1 pending sector in the smart report and I think some 14 UDMA errors

 

I suspect I've made a number of blunders above, thanks in advance for your help.

hmnetworkstore-diagnostics-20241122-2132.zip

Run the file system check against disk 5. https://docs.unraid.net/legacy/FAQ/check-disk-filesystems/?utm_source=google&utm_medium=cpc&utm_campaign=p-max-targeted-us-can&utm_content=&utm_term=&gad_source=1&gclid=CjwKCAiA9IC6BhA3EiwAsbltOAmKATlNgIX081zi2Gyh-KeUMdv8g81U89mplAq2KwMkwz4ZdQ8FaRoCZK8QAvD_BwE

 

Hi,

 

Thanks for the help.

 

I've started the file system check with the -nv option.  It fairly quickly displayed the text below and has since been running for around 5h now, it's  is continuing with lots of reads from all disks.

 

Phase 1 - find and verify superblock... couldn't verify primary superblock - not enough secondary superblocks with matching geometry !!! attempting to find secondary superblock... ...found candidate secondary superblock... unable to verify superblock, continuing... ....found candidate secondary superblock... unable to verify superblock, continuing... ...................................................

Did you use the GUI or CLI? If the latter post the command used.

I just used the GUI

In that case, it suggests disk5 doesn't have a valid filesystem, which is not very surprising from what you described, since parity is likely not valid, you can see if the actual disk mounts.

The check is still running with no new additional information, shall I wait till the check finishes or just abort now?

 

Can you just explain, has the check been running against the emulated disk 5? Which is why the reading from all drives while has been running?

 

The array is in maintenance mode with the check running, Disk 5 shows a red cross.

 

Thanks

Edited November 23, 20241 yr by Kez

You can abort, if it didn't find anything yet, it won't.

 

2 hours ago, Kez said:

has the check been running against the emulated disk 5?

Yep.

 

Stop the array, unassign disk5, see if it mounts with the UD plugin

 

Hi,

 

So I installed the UD plug in, stopped the array and unassigned disk 5.

 

I’ve now mounted the disk and can see the contents by browsing the disk using the plugin.

 

What should I do next?

 

Also when I started the array the following errors appeared for Disk 5, although I think these were already flagged in the smart when I first had issues.

23-11-2024 19:11Unraid device dev1 SMART health [199]Warning [HMNETWORKSTORE] - udma crc error count is 13 WDC_WD40EZRX-00SPEB0_WD-WCC4E1133206 (dev1)warning

23-11-2024 19:11Unraid device dev1 SMART health [197]Warning [HMNETWORKSTORE] - current pending sector is 1 WDC_WD40EZRX-00SPEB0_WD-WCC4E1133206 (dev1)

Edited November 23, 20241 yr by Kez

I would recommend doing a new config, reassigning disk5 and try to resync parity, if there are any disk errors during the sync post new diags.

I selected New Config and preserved all the assignments. Then reassigned disk 5 in the array devices list.

 

The disk has a blue square on it, in red on the right it indicates ‘All existing data on this device will be overwritten when array is started’

 

I have NOT started the array, have I missed a step as I don’t want to lose the contents of disk 5?

 

I also ran the check on Disk 5 with no modify from the UD plugin, the check completed very quickly:

FS: xfs

Executing file system check: /sbin/xfs_repair -n '/dev/sdc1' 2>&1
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
- 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
- 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
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
- traversing filesystem ...
- traversal finished ...
- moving disconnected inodes to lost+found ...
Phase 7 - verify link counts...
No modify flag set, skipping filesystem flush and exiting.

No file system corruption detected!

Edited November 23, 20241 yr by Kez

2 hours ago, Kez said:

The disk has a blue square on it, in red on the right it indicates ‘All existing data on this device will be overwritten when array is started’

This means the new config wasn't done correctly, all disks should have a blue icon, and the only warning will be for the parity disk, make sure you clicked "apply"

Thank you, you’re correct I missed clicking apply.

 

Parity is now rebuilding with disk 5 correctly mounted.

 

Thank you for your help

Party sync is now around 50% done with no errors.

 

Assuming this compete ok, I’m still a title puzzled how I ended up having this issue. What should I do next to isolate what caused the issue?

 

Should I do a second party check with write correction unticked, just to confirm I get no further parity errors?

I still haven’t connect the power to the new drive could this have been the cause? I think my power supply is around 800W running the 10/11 drives + ssd, i7-3960X and basic pci graphic card, which I thought would be plenty.

The sata cable originally connected to Disk 5 remains unconnected, should I replace this anyway.

I did have some sata cables tied together but have since removed the ties, so could cross talk just have caused this.

 

thanks

 

 

Edited November 24, 20241 yr by Kez

Best to way to try and see what caused the problem is to see new diags, if it happens again, but I would suspect a power/connection issue.