Jacko_

PreClear has completed.

Parity check has completed ok, just waiting on this new disk to be ready.

Just to add, the new drive is at 4% Zeroing. I decided not to stop parity check, thought best to see what you suggest as a remedy. Thanks.

Yes that's right on both points.

Hi trurl, Here's the diagnostics. Ok understood I won't do anything for now. Very glad of your assistance on this and I'll ready the wiki. tower-diagnostics-20230101-0844.zip

Not really sure what the best approach is for sorting this so thought i would ask for a bit of advice. I had a drive (Disk 3) that looked like it was starting to fail (bad sectors), so i replaced it (Disk 6). I've still got a shadow of Disk 3 in the array devices which i would like to remove but i'm a little apprehensive about doing so, in case i lose data - will it delete data from the parity / what is the best way to remove this stub without losing data? Secondly i have another drive (Disk 5) which is now showing bad sectors, which i have bought another drive to replace. I have just started a preclear on the new drive to replace Disk 5, so this will take a little while. I was wondering if this was still the most up to date process before adding a drive to the array and what the best process is to replace a failing drive. I guess i could just pull it, add the new drive into the Disk 5 slot and let the array rebuild, but this would put me at risk should parity drive fail during this process. I think this is why i didn't chose this way to replace Disk 3 at the time. I'm hoping to then use these two 12TB drives in another server once i have removed them from this one - the plan is to use them for a NVR project, if i get the time - maybe spin up another unraid server for this and have something i can play around with a little more without fear of breaking it / losing a lot of data. Thanks

Yep. it's down to shared pcie lane - slot i wanted to use is shared with m.2. So i have to rethink my GPU options. Thanks for the help.

I tried it and the drives were not showing, it's a x8 slot and it's a x4 card. I'll have another play, but it might be down to nvme slots sharing the bus. I need to dig out the mobo specs and see.

I need to move my HBA to another PCI-e slot to make way for a GPU, just wondering if my disks will still show if i just move it or if i need to do any reconfiguration in order to see the drives and use as them as configured previously?

Looking promising, but only 7% through pre-clear.

Just my luck. 😆 I guess i have to keep those fingers crossed it passes the pre-clear. I guess this is where it pays you to buy proper drives in the first place - longer warranty and better endurance.

Interesting - i'll do some digging on the WD site to see what it says. Ah ok. So currently i have used file manager to move data to another drive. I then stopped the array, removed the offending drive (disk 3) and restarted the array, so the data now exists on a new disk (disk 6). In this scenario, what are my options without the array trying to rebuild from parity?

Well this has been a seamless process so far. Interestingly, when i stopped the array to remove the offending disk i removed the partition and could pre-clear (or at least kick it off) without issue. Something strange happening with MBR on the new drive that meant it couldn't be pre-cleared for whatever reason. So now the long wait and hopefully no failures along the way with this older drive and it passes the test and i can re-introduce it to the array. Failing that, maybe i need to see if i can RMA it but it's a shucked drive so no idea which serial number caddy it came out of. I have this little green tick where Disk 3 used to be. In the file manager i can delete the drive but will it re-order the remaining drives keeping them sequential? It will annoy me if it doesn't. I could wait to see if the drive passes pre-clear and reintroduce at Disk 3 i guess...

Thanks both, that certainly looks easiest route. New disk is installed and its currently clearing so hopefully i'll be able to get the 'failing' drive out of the pool and cleared successfully. What's a bit strange is i couldn't use the disk preclear to do a first pass on the disk before adding it to the pool - it didn't like the MBR sig for whatever reason. So rather mess about i just added it to the pool and unraid is clearing the disk - kind of like the belt and braces approach but hopefully this is enough. I just hope i can pre-clear the old drive using the plugin before re-adding it to the pool if successfully passes. Wish me luck. #################################################################################################### # Unraid Server: verifying Preclear State of disk 5QJLTU0B. # # Verifying disk '5QJLTU0B' for Unraid's Preclear State. # # # # Step 1 of 2 - Verifying Unraid's signature: FAIL # # # # # # # # # # # # # # # #################################################################################################### # Cycle elapsed time: 0:00:01 | Total elapsed time: 0:00:01 # #################################################################################################### #################################################################################################### # S.M.A.R.T. Status (device type: default) # # # # ATTRIBUTE INITIAL STATUS # # Reallocated_Sector_Ct 0 - # # Power_On_Hours 0 - # # Temperature_Celsius 32 - # # Reallocated_Event_Count 0 - # # Current_Pending_Sector 0 - # # Offline_Uncorrectable 0 - # # UDMA_CRC_Error_Count 0 - # # # # # #################################################################################################### # # #################################################################################################### --> RESULT: FAIL! /dev/sdl DOESN'T have a valid Unraid MBR signature!!!

Hi both, Thanks for input on this. I'll need to figure out how to remove copy the data off the drive so i'l do some research on that.

I thought i did an extended test but i must have hit the wrong button. I've attached the extended test results. tower-smart-20220825-1309.zip

Hi JorgeB I attached the SMART results in the previous message. It looks to be passing the test i don't know if i'm missing something i should be reviewing and taking note of.

Hey JorgeB, just wanted to thank you for your assistance. I managed to replace the cache drives successfully a little while ago.

Would someone be able to tell me if my HDD is in need of being replaced or if this is something that can be fixed? I think i caused this issue when i pulled a drive by mistake. I've looked through the SMART test but i don't really know what i'm looking for - would be good to understand the issue and resolution. I'm wondering if it's worth replacing the drive and then zero fill formatting this one. I don't think it's a HW issue with the drive - i think it's my fault by removing the drive. Doh. Many thanks tower-smart-20220825-0939.zip tower-diagnostics-20220825-0942.zip

Thanks, JorgeB. I'll get some larger SSDs ordered.

tower-diagnostics-20220623-1042.zip

I've ran mover and it's down a little - is it enough?

Does anyone know the procedure for changing two cache SSDs for larger capacity ones? I've tried the wiki and it's been deleted Version: 6.10.3 I think the GUI upgrade was a little broken in previous OS versions but i'm not sure if that is still the case or not and i'm not sure if i just need to flush the cache to disk and replace.

Hi all, I've got an issue with a disks MBR and i'm not able to format the drive in unassigned devices. I'm up-to-date with all plugins and unraid etc. The disk is 12TB and i've managed to format the other drive ok. I did try a preclear and this also failed. Jun 18 11:32:03 preclear_disk_ZHZ4ALSM_10243: Disk blocks: 23437770752Jun 18 11:32:03 preclear_disk_ZHZ4ALSM_10243: Blocks (512 bytes): 23437770752Jun 18 11:32:03 preclear_disk_ZHZ4ALSM_10243: Block size: 512Jun 18 11:32:03 preclear_disk_ZHZ4ALSM_10243: Start sector: 0Jun 18 11:32:03 preclear_disk_ZHZ4ALSM_10243: verifying unRAID's signature on the MBR ...Jun 18 11:32:10 preclear_disk_ZHZ4ALSM_10243: Signature: failed test 1: MBR signature is not valid, byte 3 [00000] != [00170]Jun 18 11:32:10 preclear_disk_ZHZ4ALSM_10243: array 'sectors'Jun 18 11:32:10 preclear_disk_ZHZ4ALSM_10243: 0 -> 00000Jun 18 11:32:10 preclear_disk_ZHZ4ALSM_10243: 1 -> 00000Jun 18 11:32:10 preclear_disk_ZHZ4ALSM_10243: 2 -> 00000Jun 18 11:32:10 preclear_disk_ZHZ4ALSM_10243: 3 -> 00000Jun 18 11:32:10 preclear_disk_ZHZ4ALSM_10243: 4 -> 00000Jun 18 11:32:10 preclear_disk_ZHZ4ALSM_10243: 5 -> 00000Jun 18 11:32:10 preclear_disk_ZHZ4ALSM_10243: 6 -> 00000Jun 18 11:32:10 preclear_disk_ZHZ4ALSM_10243: 7 -> 00000Jun 18 11:32:10 preclear_disk_ZHZ4ALSM_10243: 8 -> 00000Jun 18 11:32:10 preclear_disk_ZHZ4ALSM_10243: 9 -> 00000Jun 18 11:32:10 preclear_disk_ZHZ4ALSM_10243: 10 -> 00000Jun 18 11:32:10 preclear_disk_ZHZ4ALSM_10243: 11 -> 00000Jun 18 11:32:10 preclear_disk_ZHZ4ALSM_10243: 12 -> 00000Jun 18 11:32:10 preclear_disk_ZHZ4ALSM_10243: 13 -> 00000Jun 18 11:32:10 preclear_disk_ZHZ4ALSM_10243: 14 -> 00000Jun 18 11:32:10 preclear_disk_ZHZ4ALSM_10243: 15 -> 00000Jun 18 11:32:10 preclear_disk_ZHZ4ALSM_10243: 16 -> 00000Jun 18 11:32:10 preclear_disk_ZHZ4ALSM_10243: 17 -> 00000Jun 18 11:32:10 preclear_disk_ZHZ4ALSM_10243: 18 -> 00000Jun 18 11:32:10 preclear_disk_ZHZ4ALSM_10243: 19 -> 00000Jun 18 11:32:10 preclear_disk_ZHZ4ALSM_10243: 20 -> 00000Jun 18 11:32:10 preclear_disk_ZHZ4ALSM_10243: fail - Unraid preclear signature invalid!Jun 18 11:32:10 preclear_disk_ZHZ4ALSM_10243: error encountered, exiting... How can the MBR signature be rebuilt? I'll do some digging myself, just trying to understand if this is a software bug, or hardware issue. smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.10.28-Unraid] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org /dev/: Unable to detect device type Please specify device type with the -d option. Use smartctl -h to get a usage summary I'm unsure how to specify the device type - never had to do this before... Thanks