mgsvr

It was a bad idea. I'm glad UNRAID won't let the array startup. I will have to wait for WD's RMA. If we cannot SSH into UNRAID in a new session to see the previous issued "nohup rsync" process, is there a way to kill that rsync run then? For example, I issued a wrong rsync command and close the terminal. Later I SSH back into unraid and since I cannot see the running progress, can I kill the previous run?

I don't use Screen either. Would be nice to SSH into unraid again to see the running nohup rsync process. Looks like I have to wait for WD to send me another disk so I can do a rebuild. I tried unassigned both Disk 2 and 3, but unRAID won't let me start the array. I was planning to use the empty Disk 3 and change it into Disk 2 and rebuild. I guess that's because I only have 1 Parity.

Ok, I'm going to use my current empty Disk 3 and change into Disk 2 and have unRAID build it. Johnnie, when I SSH into UNRAID and run "nohup rsync -av &" command to backup my share disks into my backup 8TB disk. After I kill the terminal, is there a way to SSH into back into UNRAID to see the running rsync process? Same thing with Midnight Commander. How to login in again to see the process without using something like Screen? I normally log into my Windows 10 VM, and issue MC and leave the terminal open... Thank you again for your help.

What is better for me to do between having UNRAID rebuild the data versus copy the data from backup to a new drive? My unraid currently has 1 Parity, and 3x 4TB disks. I also have a 8TB disk mount on Unassigned Devices to backup Disk 1 and Disk2. I have not do any backup yet, though. I just bought and had the 8TB precleared with 2 cycles done, and I plan to do backup this weekend. Suck that I get a disk error today. That's my plan right now for back up because I don't have the money to build another UNRAID backup box yet.

Thank you, Johnnie. I will have the disk RMA back to WD. I noticed other disks have read disk errors with raw value between 2 to 6; however, UNRAID has not report them yet. For the failing Disk 2 disk read errors, will all my media files remain intact without any lost or altered bit? I have lots of ripped movies and it would be bad if I have to redo it again.

I precleared and have this 4TB WD Red running smoothly for two years already. I ran Parity Check many times throughout the years, but today's Parity Check (with parity-correction turned off) gave me disk read errors. Should I be concerned and copy all my data to another disk? Should I RMA this drive ASAP? I have attached my SMART log text file. Thank you 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 POSR-K 200 200 051 - 68 3 Spin_Up_Time POS--K 187 180 021 - 7608 4 Start_Stop_Count -O--CK 099 099 000 - 1677 5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0 7 Seek_Error_Rate -OSR-K 100 253 000 - 0 9 Power_On_Hours -O--CK 066 066 000 - 25394 10 Spin_Retry_Count -O--CK 100 100 000 - 0 11 Calibration_Retry_Count -O--CK 100 100 000 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 200 192 Power-Off_Retract_Count -O--CK 200 200 000 - 21 193 Load_Cycle_Count -O--CK 190 190 000 - 32749 194 Temperature_Celsius -O---K 120 108 000 - 32 196 Reallocated_Event_Count -O--CK 200 200 000 - 0 197 Current_Pending_Sector -O--CK 200 200 000 - 0 198 Offline_Uncorrectable ----CK 100 253 000 - 0 199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0 200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 0 ||||||_ K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568898920 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568898928 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568898936 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568898944 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568898952 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568898960 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568898968 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568898976 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568898984 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568898992 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568899000 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568899008 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568899016 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568899024 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568899032 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568899040 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568899048 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568899056 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568899064 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568899072 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568899080 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568899088 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568899096 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568899104 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568899112 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568899120 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568899128 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568899136 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568899144 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568899152 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568899160 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568899168 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568899176 Jul 17 22:22:47 unRAID kernel: md: disk2 read error, sector=3568899184 Jul 18 04:25:26 unRAID kernel: md: sync done. time=35008sec Jul 18 04:25:26 unRAID kernel: md: recovery thread: completion status: 0 WDC_WD40EFRX-68WT0N0_WD-WCC4E0394858-20180718-0708.txt

Anyone else knows about this?

Thank you, guys. So many ways to do stuff with unRAID. I'll make sure I capture an image of the main page before I do a new config. I'll post this here from user itimpi in case I need to upgrade to larger drive:

Is there any disadvantages by going with a New Config and check Retain settings turn on? Do I have to setup all the system and docker/VM settings again?

Thank you very much!

During Assign old Parity2 as a new disk, can I assign it as Disk 1? Also assign my current Disk 1 as Disk 2..etc? Parity 1 Disk 3 (used to be parity 2) Disk1 (current) Disk 2 (current) Or do I assign it as Disk 3. Once done clearing I can stop the array and reassign the slot to: Parity 1 Disk 1 (used to be parity2/Disk3) Disk 2 (used to be disk 1) Disk 3 (used to be disk 2) Thanks!

Hello everyone, I have been reading through the forum but I still need to get a confirmation on this. Here is my current setup: Parity 1 Partiy 2 Disk 1 Disk 2 I want to go back to use just 1 parity drive, and use the 2nd parity as Disk data. Is it ok for me to do a New Config and assign Parity 2 as Disk 1. Current Disk 1 as Disk 2; current Disk 2 -> Disk 3. Do I check the "Parity is valid" so Parity 1 does not need to rebuild? Please let me know what I do is correct. Thank you!

Hi guys, I've been reading all over the forum about Unraid and Time Machine. My Mac is High Sierra and APFS format. 1) If I drag an Apple Photos folder directly into an Unraid disk share (so no scattered files), will unRAID able to save everything? I read somewhere that Apple uses special meta/database files that other file system formats can't save correctly but Mac HFS+ or APFS. Is this true? If I unRAID can save the whole folder/file structure accordingly, I'll just backup my Apple Photos folder only. No need to use waste a disk slot to setup Time Machine share. 2) If create a share to use only one disk for Time Machine, can I use SMB instead of AFP? That is according to the link below https://support.apple.com/kb/ph25585?locale=en_US Thank you

Thank you for your answer.

I just upgraded to 6.4 and have set it to boot with UEFI mode. The array drives are GPT. Cache (SSD) is MBR for some reason... I changed my computer BIOS to boot using UEFI only. There is this flag called Storage OpROM policy, and it was set to Legacy by default. Is it alright if I change to UEFI for storage opROM policy? I'm not really sure what it is. I tried to google around but not able to find out much. Thank you

RobJ, I will upgrade to 6.2 then do a New Config as you suggested. My 3rd Data drive still have empty folders created from the User Share. Do I need to go into MC to delete them before I make the drive into a Parity? Hopefully Unraid will do a format on the Parity assigned drives then build. Thank you

I have the Asrock E3C224D4I-14S server motherboard with the following: 4 x SATA3 by Intel C224 support RAID 0,1,5,10 8 x SAS2 from 2 x mini SAS 8087 connector by LSI 2308 Does that mean Unraid 6.2 will not spin down my drives? SATA drives attached to your SAS ports should work ok. SAS drives attached to your SAS ports will be problematic. Note: SAS controllers typically support both SAS drives and SATA drives. All my drives are SATA. I use the Mini-SAS to SATA cable to connect the first 8 drives. Ok I will upgrade to 6.2 tonight. Hopefully everything works fine! Thanks

I have the Asrock E3C224D4I-14S server motherboard with the following: 4 x SATA3 by Intel C224 support RAID 0,1,5,10 8 x SAS2 from 2 x mini SAS 8087 connector by LSI 2308 Does that mean Unraid 6.2 will not spin down my drives?

Hello Lime-Technology forum, Currently I have 1 Parity and 3 Data drives. I've moved all files off the 3rd data drive to the first two drives via MC. My plan is to use the 3rd drive to be the 2nd Parity drive in Unraid 6.2. Here is my procedure: 1) unassigned the 3rd drive 2) do a new config in tool for parity rebuild 3) assign the 3rd drive as 2nd parity Please let me know if my method is correct. Also, do I need to do a pre-clear script for the 3rd drive before I make it into a Parity drive? I already did a pre-clear on the drive a year ago when I assigned it as a data drive... Thank you

Hello everyone, I just setup my docker for Deluge. At the config I entered all my provider's proxy settings exactly like the one I use on my desktop. The Deluge on my desktop would mask my IP; however, the unRAID docker version will always show my real IP. I use gfjardim's Repository and the default Bridge setting on Deluge. If anyone know why, please help me on this. Thank you

Thank you, trurl, that cleared all my questions!

I have another question. I will pre-clear all data drives, but do I need to pre-clear the Parity drive to make sure it's working well? I am doing a new config so I have yet to assign any drive. Taking from the above quote, I assume assigning a Parity Disk will make unRAID do its drive test anyway? Thanks

Hello trurl, I assume I need to use the console and run the Pre-Clear on all drives including Parity, Disk, and Cache (ssd). After I run Pre-Clear on each drive, and if no error report, do I need to restart the Parity-Sync again? Thanks

Hello, I just setup my Unraid v6 server followed the YouTube guide from Jon. After I assigned the Partiy, Disk, and Cache, I hit Start and the partity sync is progressing. I then do a Format on my 1 Disk drive and 1 Cache Drive. It takes around 10-20 minutes and it's done. While Parity is doing the sync the first time, does it run any test to make sure the HDD is good? Also, it looks like the data Disk drive takes only a couple minutes to do the Formatting, how should I run a test to make sure HDD is good? I read about Pre-Clearing the drive, but that is for testing and preparing the drive before put it into Unraid pool. What should I run to make sure both my Parity and Disk is in good status? Thank you.

Hello guys, I bought a E3C224D4I-14S and a Xeon E31231v3 couple days ago. I only need this Unraid to store my media files and as a Plex server with 2-3 streams. 1) For the E3C224D4I-14S mobo, do I need to flash the LSI to "IT mode" for Unraid? Is it better to use the Intel SAS controller for Parity + 3 drives. Then LSI SAS controller for the rest of the drives? 2) The latest BIOS for this board is 3.20. Is there any known conflict of this BIOS and Unraid? Thank you