gnollo

OK so once I have finished this project I will set it back to auto

Yes absolutely, will turn all dockers off when doing this, 11 drives to move, 52TBs of data. MIght even start the server in safe mode. If I do so can I still connect from another PC to it?

Interesting, thank you I just changed that setting. Any drawbacks from doing that?

Thank you, I got to browse it that way I found disk12\appdata\EmbyServer with the following folders labelled as <SHARE> under the size column 1) Cache 2) Data 3) Logs I guess written by the emby docker before I removed the drive from the shares (116KB when I selected and clicked on calculate) disk12\unraid\emby windows server backups\Emby Server Databases - 2026-01-24 00.11.10 also I guess written by the emby docker (306MB)

Is that because Export is set to NO under SMB securities settings for that drive, I guess that is because I excluded the drive from the shares?

Quick question. Stats shows 2% data on disk12 is that right? Have not started moving anything yet. Also I tried reaching the drive to see what files are on it, with \\tower\ in windows explorer but I cannot see disk 12. Also tried \\tower\disk12, no can do.

Yep I like lists, I hope it helps others that will go through this process

So I will run the emby docker over the weekend and start the procedure on Sunday late night. 1) click on the terminal icon on the unraid web interface 2) as my other largest (10TB) drive in the array is disk4, type: rsync -avPX /mnt/disk4/ /mnt/disk12/ 3) prompt should return at the end with no errors showing 4) as I am paranoid, will check integrity with typing: rsync -avhPX/mnt/disk4/ /mnt/disk12/ 5) if all goes well it will just return to prompt 6) stop the array 7) Click on Tools, then New Config, then Preserve current Assignments 8) select All, then check Yes I want to do this, click Apply then Done (if unmountable disk(s) appear then I need to select the correct file system for those disk(s) whichh in my case would be rfs for all but one disk) 9) I go back to the Main page and click on the dropdown for disk12 (the xfs drive) and unassign it (I click on "unassigned" or "no device") 10) I click on the dropdown for drive 4 (the one I already copied), and unassign it (make a note of the drive details) so I can then reassign it as disk 12 11) I click on the dropdown for the drive 12 and reassign it as the physical rfs drive I have just copied across 12) Click on each drive name and swap also the file system format of the drive - if it's ReiserFS change it to XFS, if it's XFS change it to ReiserFS [this was not possible on my version of the OS as reiserfs is grayed out as an option, thankfully all drives were recognised as rfs except the one I just converted to XFS) 13) All array disks are with blue icons, on the main Tab scroll to the bottom and click on the check box for Parity is already valid, then click on start 14) stop the array and click the disk 12, and change the format to XFS, then click Apply and Done 18. Start the array; at the bottom of the Main tab, you will get a warning Unmountable disk present: tick the Yes I want to do this box under the message "Format will create a file system in all Unmountable disks." A warning box will popu up, click on OK then click on the Format button for disk 12

Thank you, Rsynch it is. Stopped array. Settings / Global Share settings Enable disk shares: Yes Enable user sharres: Yes Included disks: all Excluded disks: disk 12 Permit exlusive shares: No Tunable (support hard links): Yes Tunable (enable direct IO): Auto Number of fuse filee descriptors: 40960 Apply / Start Array

Just out of curiosity, what is the advantage of using rsynch instead of just moving all the files from one drive to the other with midnight commander?

Found the format button at the bottom of the webpage, ticked the box and now it is formatting and creatign a file system. Disk is XFS.

Event: Unraid Disk-Clear Subject: Notice [TOWER] - Disk-Clear finished (0 errors) Description: Duration: 17 hours, 27 minutes, 41 seconds. Average speed: 159.1 MB/s Importance: normal Disk is unmountable

Also I cannot do the step of excluding the drive from the global share settings as Array must be Stopped to change, and I can't stop it until the disk-clearing procecss has completed I guess

Total size: 10 TB Elapsed time: 29 minutes Current position: 364 GB (3.6 %) Estimated speed: 211.9 MB/sec Estimated finish: 12 hours, 38 minutes Mmmh seems to be taking a lot longer than a couple of hours

New parity build process complete. Added back the old parity in a different slot. Started the unraid server Stopped the array after the boot completed Added the old parity as disk 12. Start will bring the array on-line and start Disk-Clear of new data disk(s). Started the array Disk12 is blue as Disk-Clear in progress.

Thank you for the quick response. A replacement 14TB parity drive is going through Parity-synch for a couple of day. When that has completed, the first steps will be, from my understanding and readign the pdf 1) I stop the array 2) I add the old parity drive back in, my array has 11 drives so I will add it as drive 12 and start the array (I guess I don't have to empty it as it will happen when I format it to XFS?) 3) I have enabled User Shares so I go to Settings -> Global Share Settings and add my ex parity disk to ' Excluded disk(s) ' 4) I click on the disk name of the old parity drive, now disk 12 and change the format to XFS then click Apply and Done 5) I start the array; disk12 should show as `Unmountable', and a Format button will be present 6) I click the check box for formatting, then click the Format button; when done, array should show an additional drive, almost completely empty, formatted with XFS (how do I make sure it does not format it as RFS again?) Now the drive should be ready for the rsync mirror procedure

Smart short self-test completed without errors Downloaded smart report smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.6.68-Unraid] (local build) Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Ultrastar (He10/12) Device Model: WDC WD100EMAZ-00WJTA0 Serial Number: 1EGG5LHZ LU WWN Device Id: 5 000cca 27ec67234 Firmware Version: 83.H0A83 User Capacity: 10,000,831,348,736 bytes [10.0 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Form Factor: 3.5 inches Device is: In smartctl database 7.3/5625 ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.2, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Tue Jan 20 09:11:18 2026 +01 SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM level is: 164 (intermediate level without standby) Rd look-ahead is: Enabled Write cache is: Enabled DSN feature is: Unavailable ATA Security is: Disabled, NOT FROZEN [SEC1] Wt Cache Reorder: Unknown === START OF READ SMART DATA SECTION === SMART Status not supported: Incomplete response, ATA output registers missing SMART overall-health self-assessment test result: PASSED Warning: This result is based on an Attribute check. General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 93) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: (1229) minutes. SCT capabilities: (0x003d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate PO-R-- 100 100 016 - 0 2 Throughput_Performance --S--- 129 129 054 - 112 3 Spin_Up_Time POS--- 169 169 024 - 408 (Average 368) 4 Start_Stop_Count -O--C- 097 097 000 - 12412 5 Reallocated_Sector_Ct PO--CK 100 100 005 - 0 7 Seek_Error_Rate -O-R-- 100 100 067 - 0 8 Seek_Time_Performance --S--- 128 128 020 - 18 9 Power_On_Hours -O--C- 093 093 000 - 50452 10 Spin_Retry_Count -O--C- 100 100 060 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 151 22 Helium_Level PO---K 100 100 025 - 100 192 Power-Off_Retract_Count -O--CK 043 043 000 - 68484 193 Load_Cycle_Count -O--C- 043 043 000 - 68484 194 Temperature_Celsius -O---- 185 185 000 - 35 (Min/Max 15/47) 196 Reallocated_Event_Count -O--CK 100 100 000 - 0 197 Current_Pending_Sector -O---K 100 100 000 - 0 198 Offline_Uncorrectable ---R-- 100 100 000 - 0 199 UDMA_CRC_Error_Count -O-R-- 200 200 000 - 0 ||||||_ K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning General Purpose Log Directory Version 1 SMART Log Directory Version 1 [multi-sector log support] Address Access R/W Size Description 0x00 GPL,SL R/O 1 Log Directory 0x01 SL R/O 1 Summary SMART error log 0x02 SL R/O 1 Comprehensive SMART error log 0x03 GPL R/O 1 Ext. Comprehensive SMART error log 0x04 GPL R/O 256 Device Statistics log 0x04 SL R/O 255 Device Statistics log 0x06 SL R/O 1 SMART self-test log 0x07 GPL R/O 1 Extended self-test log 0x08 GPL R/O 2 Power Conditions log 0x09 SL R/W 1 Selective self-test log 0x0c GPL R/O 5501 Pending Defects log 0x10 GPL R/O 1 NCQ Command Error log 0x11 GPL R/O 1 SATA Phy Event Counters log 0x12 GPL R/O 1 SATA NCQ Non-Data log 0x13 GPL R/O 1 SATA NCQ Send and Receive log 0x15 GPL R/W 1 Rebuild Assist log 0x21 GPL R/O 1 Write stream error log 0x22 GPL R/O 1 Read stream error log 0x24 GPL R/O 256 Current Device Internal Status Data log 0x25 GPL R/O 256 Saved Device Internal Status Data log 0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log 0x80-0x9f GPL,SL R/W 16 Host vendor specific log 0xe0 GPL,SL R/W 1 SCT Command/Status 0xe1 GPL,SL R/W 1 SCT Data Transfer SMART Extended Comprehensive Error Log Version: 1 (1 sectors) No Errors Logged SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 50452 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. SCT Status Version: 3 SCT Version (vendor specific): 256 (0x0100) Device State: Active (0) Current Temperature: 35 Celsius Power Cycle Min/Max Temperature: 23/39 Celsius Lifetime Min/Max Temperature: 15/47 Celsius Under/Over Temperature Limit Count: 0/0 SCT Temperature History Version: 2 Temperature Sampling Period: 1 minute Temperature Logging Interval: 1 minute Min/Max recommended Temperature: 0/65 Celsius Min/Max Temperature Limit: -40/70 Celsius Temperature History Size (Index): 128 (72) Index Estimated Time Temperature Celsius 73 2026-01-20 07:04 34 *************** ... ..( 45 skipped). .. *************** 119 2026-01-20 07:50 34 *************** 120 2026-01-20 07:51 35 **************** ... ..( 5 skipped). .. **************** 126 2026-01-20 07:57 35 **************** 127 2026-01-20 07:58 34 *************** ... ..( 22 skipped). .. *************** 22 2026-01-20 08:21 34 *************** 23 2026-01-20 08:22 33 ************** 24 2026-01-20 08:23 33 ************** 25 2026-01-20 08:24 34 *************** ... ..( 12 skipped). .. *************** 38 2026-01-20 08:37 34 *************** 39 2026-01-20 08:38 33 ************** ... ..( 7 skipped). .. ************** 47 2026-01-20 08:46 33 ************** 48 2026-01-20 08:47 34 *************** ... ..( 9 skipped). .. *************** 58 2026-01-20 08:57 34 *************** 59 2026-01-20 08:58 35 **************** ... ..( 11 skipped). .. **************** 71 2026-01-20 09:10 35 **************** 72 2026-01-20 09:11 34 *************** SMART WRITE LOG does not return COUNT and LBA_LOW register SCT (Get) Error Recovery Control command failed Device Statistics (GP Log 0x04) Page Offset Size Value Flags Description 0x01 ===== = = === General Statistics (rev 1) 0x01 0x008 4 151 --- Lifetime Power-On Resets 0x01 0x010 4 50452 --- Power-on Hours 0x01 0x018 6 134132243325 --- Logical Sectors Written 0x01 0x020 6 403924017 --- Number of Write Commands 0x01 0x028 6 334968294324 --- Logical Sectors Read 0x01 0x030 6 511442836 --- Number of Read Commands 0x01 0x038 6 181629452050 --- Date and Time TimeStamp 0x03 ===== = = === Rotating Media Statistics (rev 1) 0x03 0x008 4 38188 --- Spindle Motor Power-on Hours 0x03 0x010 4 38188 --- Head Flying Hours 0x03 0x018 4 68484 --- Head Load Events 0x03 0x020 4 0 --- Number of Reallocated Logical Sectors 0x03 0x028 4 0 --- Read Recovery Attempts 0x03 0x030 4 0 --- Number of Mechanical Start Failures 0x04 ===== = = === General Errors Statistics (rev 1) 0x04 0x008 4 0 --- Number of Reported Uncorrectable Errors 0x04 0x010 4 0 --- Resets Between Cmd Acceptance and Completion 0x05 ===== = = === Temperature Statistics (rev 1) 0x05 0x008 1 35 --- Current Temperature 0x05 0x010 1 34 N-- Average Short Term Temperature 0x05 0x018 1 32 N-- Average Long Term Temperature 0x05 0x020 1 47 --- Highest Temperature 0x05 0x028 1 15 --- Lowest Temperature 0x05 0x030 1 46 N-- Highest Average Short Term Temperature 0x05 0x038 1 16 N-- Lowest Average Short Term Temperature 0x05 0x040 1 39 N-- Highest Average Long Term Temperature 0x05 0x048 1 25 N-- Lowest Average Long Term Temperature 0x05 0x050 4 0 --- Time in Over-Temperature 0x05 0x058 1 65 --- Specified Maximum Operating Temperature 0x05 0x060 4 0 --- Time in Under-Temperature 0x05 0x068 1 0 --- Specified Minimum Operating Temperature 0x06 ===== = = === Transport Statistics (rev 1) 0x06 0x008 4 721 --- Number of Hardware Resets 0x06 0x010 4 225 --- Number of ASR Events 0x06 0x018 4 0 --- Number of Interface CRC Errors 0xff ===== = = === Vendor Specific Statistics (rev 1) |||_ C monitored condition met ||__ D supports DSN |___ N normalized value Pending Defects log (GP Log 0x0c) No Defects Logged SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 2 0 Command failed due to ICRC error 0x0002 2 0 R_ERR response for data FIS 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 R_ERR response for host-to-device data FIS 0x0005 2 0 R_ERR response for non-data FIS 0x0006 2 0 R_ERR response for device-to-host non-data FIS 0x0007 2 0 R_ERR response for host-to-device non-data FIS 0x0008 2 0 Device-to-host non-data FIS retries 0x0009 2 3 Transition from drive PhyRdy to drive PhyNRdy 0x000a 2 2 Device-to-host register FISes sent due to a COMRESET 0x000b 2 0 CRC errors within host-to-device FIS 0x000d 2 0 Non-CRC errors within host-to-device FIS

my parity settings are Attribute=5 Reallocated sectors count Attribute = 187 Reported uncorrectable errors Attribute = 188 Command time-out Attribute = 197 Current pending sector count Attribute = 198 Uncorrectable sector count Attribute = 199 UDMA CRC error rate Exactly as your screenshot, how did you know

Looks like I will be upgrade the parity drive with a larger disk, and then can I use the old parity as the first drive to be used for the process? Do I have to preclear it?

Checked my other drives and I can see tape on some of them, so I tried one final time, removed parity and inserted the drive, this time taped with black electric tape so it would not move. Tape did not move but the drive was not recognised so I just sent it back to Amazon. Will buy a drive that has no issues with the third pin to save me the hassle. I chose a WD Ultrastar DC HC530 (WUH721414ALE6L4).

I have emailed Norco's support email to have a confirmation but that is why I remember that I had to tape drives in the past

this one was AI generated by google, when I asked if the NorcoSS500 suffer from 3rd pin issue "The 3rd pin issue on the Norco SS-500, commonly associated with "shucked" Western Digital white-label hard drives, occurs because of the SATA 3.3 specification, which uses the 3rd pin (3.3V) for the Power Disable (PWDIS) feature. When a modern 3.3V-capable drive is inserted into a standard power supply connector (or older backplane) that sends 3.3V to this pin, the drive detects it as a shutdown signal and refuses to spin up. " So I still need to be careful about which drives I put in the system.

Plan to test it today in my PC today. Funny thing is that I remember having to tape up a drive before, but can't remember if it was before I installed the Norcos... https://norco.com.sg/pdfs/SS-500_5_bay_Hot_Swap_Module.pdf The pdf clearly states that the Norcos (I have 4) have molex redundant power connectors, so in this case it has gotta be a drive issue? In your opinion I can buy any drive to replace this as I will not be restricted by the 3.3V pin issue?

also have an option of sending the drive back, and get one that does not have the third pin issue. What about a Synology HAT3320-8T, can I use it in an unraid server? It appears it doesn't suffer from the third pin issue, or would anyone else recommend a different 8TB drive? On Amazon most drives are showing deliveries to JULY! Must be the GenAI bubble generating incredible demand?

Cut the 3.3V Wire (Permanent): If you have a modular power supply, you can identify the 3.3V wire (usually orange) on the SATA cable and cut it, or remove the pin from the connector. Do I just cut the orange wire and tape it up?