DingHo

Hi, I un-ticked the 'allow external access' box, and now I can't access the webpage anymore. I assumed external was referring to 'from the internet' and not localhost. Anyway to get back in, or am I gonna have to setup my docker from scratch? Thanks for any help.

The other controllers I get the errors whenever trim runs. I get this when it's on the 'good' controller: Apr 18 15:40:07 Scour root: /etc/libvirt: 1022.5 MiB (1072185344 bytes) trimmed Apr 18 15:40:07 Scour root: /var/lib/docker: 16.6 GiB (17835913216 bytes) trimmed

Tried multiple cables. It is not the issue. I'm able to reproduce it when I invoke TRIM. Switched the drive to another controller, invoked TRIM, and the issue did not reoccur. I think the other controller did not support TRIM.

Update: After the pre-clears finished, I rebooted the server. The array started successfully. The cache drive and shares are accessible and the dockers are functional. I successfully made a copy of everything on the cache drive without any errors. SMART short, and extended test ran without errors. All the errors started at 2am, which is when the SSD trim is scheduled for the cache drive. Perhaps the controller doesn't support TRIM?

Added them. Thanks.

Hello, I transferred my array to a new system yesterday. Everything seemed fine, booted up no problem and array started without issue, as did all docker containers. I added some new drives to begin preclearing last night before bed. I went to check this morning, and noticed several problems. The dockers' version is marked 'not available'. Running Fix Common problems yielded, "unable to write to cache", "unable to write to docker image", and "call traces found on your server". In the Shares tab, all shares are missing. The data still seems to be there if I look on the data disks. My new system is an Asus P8V77-V, i5-3570k, unraid v6.3.5. In order to add more drives, I also added a Supermicro AOC-SAS2LP-MV8. I've noticed people have issues with this controller. However, the cache disk is not connected to that controller. I've attached the syslog. Please let me know what else would be helpful to diagnose. Any help is greatly appreciated. scour-diagnostics-20180418-0732.zip

Thanks for the info!

Hello, I had a unexpected shutdown a couple days ago: Jan 2 18:20:46 Tower root: Fix Common Problems: Error: unclean shutdown detected of your server I started a parity check this morning and it resulted in 768 errors. Looking in the log: Jan 4 17:09:46 Tower kernel: md: recovery thread: P corrected, sector=5087241624 Jan 4 17:09:46 Tower kernel: md: recovery thread: P corrected, sector=5087241632 Jan 4 17:09:46 Tower kernel: md: recovery thread: P corrected, sector=5087241640 Jan 4 17:09:46 Tower kernel: md: recovery thread: P corrected, sector=5087241648 These same errors continue in what seem to be sequential sectors. The array seems to be working fine. Is this anything to be concerned about before I move on with my plan of shrinking the array by removing an HDD and replacing it with an SSD for a cache drive? Thanks for any help!

Ran another parity check overnight, game back with 0 sync errors corrected. Looks like everything is OK. I'll go ahead an update to 5.06 before adding the 4TB drive. Thanks for the guidance!

I saw today I had a parity sync error, so I ran a parity check with correct errors enabled. Upon completion it says"Parity updated 1921 times to address sync errors." I recently experienced a power outage while transferring a large amount of data (~100GB) to my unRAID server. I suspect this may be the cause of so many errors. After the outage, I re-copied the data to the unRAID server again. Everything seems to be working fine. I'm just concerned as I'm about to upgrade from 5.05 to 5.06 and swap out the 2TB parity drive to a 4TB drive. Can anyone offer any advice if I have any issue? Thank you!

My setup has Ubuntu on a small SSD, and media storage on a large HDD. I've currently got newznab working on the SSD, but in the future, can I install to somewhere besides /var/www/newznab, or will that confuse the other dependent applications? Any suggestions on the best way to go about this?

Hi Auggie, I have the same board, several 2TB drives w/ SATA cables zip tied together, and I'm considering adding some 3TB drives whenever unRAID 5.0 goes gold. How did you see read errors you mentioned? i.e. Where did you see the errors being reported?

Why not upgrade to 4.7 and stop worrying about jumpers? Seems easier to me. I'm considering the upgrade to 4.7 or 5.0b14 now. If I already have all my WD20EARS drives with the jumper on them, do I need to remove them before or after upgrading? Or not at all?

Hello, Sorry if this has been asked and answered, but I can't find it. I currently have a PLUS license, running 4.5.6. I'm curious if version 5 will be a free or paid upgrade? Regards

I'm still on 4.5.6 (holding out until 5.0 to upgrade). So I guess I'd have to jumper it?

Do the EARX drives still need the jumper?

Does anyone have any experience using this MSI mini-ITX board with unRAID? Any potential problems for a small 4 drive build? http://www.msi.com/product/mb/H61I-E35--B3-.html

Rob, We've got almost identical rigs except for the RAM and HDs. I'm getting quite similar parity creation performance w/ a variety of WD Green 2TB and 1TB drives. Just curious... what are your drive temperature running? Are you still on stock Lian Li fans? I changed the fan on the top of the case to an Antec running at a little higher RPM, and was thinking of upgrading the front fan as well.

Thanks Orbi, What I'm also concerned about is, "Offline data collection activity was suspended by an interrupting command". What is this about?

I just finished a the preclear script of 1 drive and had some questions. I was preclearing this drive, and another simultaneously. I get the message about "suspended by an offline command from host" and was just making sure everything is ok. I also attached smartctl report below, taken just after preclear finished. =========================================================================== = unRAID server Pre-Clear disk /dev/sdd = cycle 1 of 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Testing if the clear has been successful. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 42C, Elapsed Time: 16:54:58 ============================================================================ == == Disk /dev/sdd has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 19,20c19,20 < Offline data collection status: (0x82) Offline data collection activity < was completed without error. --- > Offline data collection status: (0x84) Offline data collection activity > was suspended by an interrupting command from host. ============================================================================ root@Scour:/boot# Device Model: WDC WD1001FALS-00K1B0 Serial Number: WD-WMATV1553669 Firmware Version: 05.00K05 User Capacity: 1,000,204,886,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Wed Sep 8 16:03:21 2010 SGT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. 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: (19200) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. 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: ( 221) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x303f) SCT Status 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 FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 229 226 021 Pre-fail Always - 8516 4 Start_Stop_Count 0x0032 098 098 000 Old_age Always - 2172 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 093 093 000 Old_age Always - 5172 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 773 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 123 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 2172 194 Temperature_Celsius 0x0022 108 102 000 Old_age Always - 42 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] 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.

Hi All, Just an update that I've got my new system (mostly) up and running. I was finally able to pick up the Lian Li PC-Q08 that I've been waiting quite some time to become available here. My system consist of: SuperMicro X7SPA-HF 2GB Kingston RAM (whatever was mentioned earlier) Lian Li PC-Q08 Corsair 400W (although modular PSU would have certainly been handy for this small case) 2x WD EARS 2TB 1x WD EADS 2TB 1x WD ?? 1TB Drive temps ~37-41C while writing Transfer rates of ~50MB/s (w/o Parity) Parity build of 50+MB/s Currently parity is quietly building in the background while flawlessly streaming to my WDTV. Anything else I should do besides running smartctl on each drive before adding my old data disk to my unRAID array? Thanks!

Hi Auggie, I'm about to build a similar system to yours. I have the X7SPA-HF, and I'm considering getting the Supermicro AOC-SASLP-MV8 as well. I'm a bit confused about how this add on card works... Are the ports on the card SAS or SATA, it seems some secondary board is necessary for SATA? Did you have to install any driver for this to work w/ unRAID? Did you add this card in later, or have it installed from the beginning. Any other useful info?