tr0910

On the docker setup page?? Here is what mine looks like.

I am just playing around. I understood that the folder name is just a text description, so it doesn't matter.

I'm trying to get my unRaid files recognized, however owncloud "red lines" my typing /mnt/disk1 or /mnt/user/usershare. See this:

What is the biggest OwnCloud project you've tried using local unRaid storage 1. How many TB? 2. How many files? I want to put several TB out there with a hundred thousand files. Clients are Windows or Mac. Some files I would want to sync (Adobe Lightroom catalog) but most raw image files should not to be synced to the users client owncloud folder. It would be too extreme Does it scale?

Just installed s3 sleep on 6b14 test server with an Areca 1280 24 port drive controller. It seems to work fine. However last night it was doing a parity check, and went to sleep 30% through the check (one hour was set before sleep). It woke up and continued the parity check as if nothing had happened. Should it go to sleep in the middle of a parity check?? Is that not activity that would keep it from activating sleep? MB: Gigabyte GA-880GA-UD3H with AMD Phenom II X6 1055T with 16GB ram

That is great. Plugin or Docker??

Just tried Dynamix 64bit S3 sleep ver 3.0.0 on this, and was surprised that it seems OK. Anybody else using S3 sleep on an Areca? ============= Update last night the parity check went to sleep in the middle of the check. Once it woke back up and resumed without issue, but the second time it invalidated parity. I wonder if hdparm is being used to determine if there is array activity before going to sleep?? All the drives are on the Areca.

Yes, that worked, see the output below. I'll update my previous posts with updated images showing the correct way... ================ smartctl -a -d areca,4/1 /dev/sg6 (disk8) smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.18.5-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Hitachi Deskstar 7K1000.C Device Model: Hitachi HDS721010CLA332 Serial Number: JP2921HQ098U3A LU WWN Device Id: 5 000cca 35dc43869 Firmware Version: JP4OA25C User Capacity: 1,000,204,886,016 bytes [1.00 TB] Sector Size: 512 bytes logical/physical Rotation Rate: 7200 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 2.6, 3.0 Gb/s Local Time is: Wed Mar 18 15:09:03 2015 CDT 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: ( 9929) 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 166) 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 FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 134 134 054 Pre-fail Offline - 102 3 Spin_Up_Time 0x0007 131 131 024 Pre-fail Always - 271 (Average 308) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 432 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 1 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 132 132 020 Pre-fail Offline - 34 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 3899 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 300 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 472 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 472 194 Temperature_Celsius 0x0002 193 193 000 Old_age Always - 31 (Min/Max 15/43) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 1 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0 SMART Error Log Version: 0 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 3189 - # 2 Short offline Completed without error 00% 3187 - 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.

Like this?? (note how the formatting gets smashed when I save it) Note correct way to fill in this screen below (per bjp999 & bobphoenix) No problem, I like it already, but will like it much more if we are able to get it to behave transparently under the GUI with temperatures and spin status showing correctly. (I am testing an Areca 1280 with this code)

In the first post you refer to changing the mymain custom attributes in unmenu: >> 9 - Click on one of the drive ID columns for a drive connected to the Areca controller. It contains the last 4 characters of your serial number. It should bring up a configuration panel of drive attributes. In the "custom attributes" section (under Other Notes), you need to configure two custom attributes. smartopt -d areca,X/Y /dev/sgZ (you need to specify the X, Y, and Z based on the instructions in step 5 above) spinind -1 Yet, on my version of unmenu (latest 1.6) I don't show custom attributes. I show (see attached image where I have mucked around in the red area):

Yes, you tell unRaid to spin down all the drives, and the green balls all go silent on the GUI, but the drives attached to the Areca are still spinning unless you update the Areca bios options to match the unRaid options.

Just for the benefit of those following, and wondering why their drives don't spin down. Just setting it in unRaid will have no affect. You need to update the setting in the raid card bios too. System controls / HDD power management / Time To Spin Down Idle HDD / change from disabled to 60 minutes (if that is what you want.)

I created a 4tb = 2x2tb raid0 parity, and passed through the rest of the slots. I also have a 4tb new drive that I wanted to test with this setup. Size = 3,907,018,532 (mymain unmenu detail view size in K) But the 2x2tb raid0 volume I create with Areca is smaller and won't work for parity (created with >2tb vol support 64bit lba, default 64k stripe size, write back cache, and tagged command queuing enabled.) Size = 3,906,249,696 Found the problem was the Areca volume truncation setting. Once this was fixed its all golden.... New size is 3,907,028,448 Make sure that you change the Areca settings System Controls / System Config / Disk Capacity Truncation Mode - to No Truncation. Otherwise the arrays you create will be chopped, and if you want to use them for parity, this will be a problem. Testing for HPA doesn't seem to work on the Areca using the normal way. hdparm -N /dev/[hs]d[a-z] gives /dev/sda: SG_IO: bad/missing sense data, sb[]: f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SG_IO: bad/missing sense data, sb[]: f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 max sectors = 0/1, HPA is enabled /dev/sdb: SG_IO: bad/missing sense data, sb[]: f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SG_IO: bad/missing sense data, sb[]: f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 max sectors = 0/1, HPA is enabled /dev/sdc: max sectors = 1465149168/1465149168, HPA is disabled /dev/sdd: max sectors = 1465149168/1465149168, HPA is disabled /dev/sde: SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 14 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 14 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 max sectors = 0/1, HPA is enabled /dev/sdf: SG_IO: bad/missing sense data, sb[]: f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SG_IO: bad/missing sense data, sb[]: f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 max sectors = 0/1, HPA is enabled /dev/sdg: SG_IO: bad/missing sense data, sb[]: f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SG_IO: bad/missing sense data, sb[]: f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 max sectors = 0/1, HPA is enabled /dev/sdh: SG_IO: bad/missing sense data, sb[]: f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SG_IO: bad/missing sense data, sb[]: f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 max sectors = 0/1, HPA is enabled SDC and SDD are hooked to mb Sata ports not the Areca.

Thanks for the clarification on the firmware update process. Works like a charm. However with the Areca 1280 in the AMD motherboard, it no longer will boot from USB. Rechecked the mb bios and it is set to boot from Yes a different usb port solved it....

The 1280 was what i tried first and it has a net jack too, which i plugged into my router. My network has 10.x.x.x numbering but the card IP I saw in the bios was 192.168.x.x. So I can come in via browser from any laptop attached to the same network once I get the IP fixed ?

I have received a 1280 and the 1231 referenced above. Put it into my unraid box with some fresh 2tb drives and it sees them in the bios. But it has 1.47 firmware. Need to figure how to update the firmware. Is it easy to do in an unRaid box? I've downloaded the drivers but need to figure out the easiest way to get them on to a non windows server.

@weebo, @bonienl, @jbartlett Seeing you creating tools for advancing the stability and reliability of our data is the work of giants. We will all thank you for this later. I want to thank you now.

Think of hard drives like disposable cutlery. When you are done with it, toss it. My 2tb and 3tb drives will never be replaced. They will be upgraded to 4tb and 6tb when necessary. DOA is the only exception to this.

Gary and I have a friendly dispute over whether to pay more for NAS hard drives. I subscribe to the back blaze strategy. Buy the cheapest highest capacity drives available that you are comfortable buying. It looks like back blaze wanted to test their strategy hence the fact that they have any NAS drives at all. Interesting results.

I think it is certain that the 2 drives are close cousins if not identical twins. Manufacturing costs favor very similar designs. I have seen the WD greens being very questionable quality wise, but I don't have enough of them to be statistically significant. I have no reds.

My theory is that the 3tb Reds are just greens with a red sticker. That is why I was looking for the data on 3tb greens. Or maybe a better way of saying it is the greens are likely even worse than the Reds from a quality standpoint. My very limited data would suggest that. Bjp999, I also have been waiting for better deals. Do you have a price projection for 4tb this year at BF?

I wonder if the learning here is that the 3tb drives, (all of them) were the low point of the quality curve. Remember how cheap they were? Perhaps it's simply a case of you get what you pay for.

I thought they had some WD Green 3tb in their pods? Maybe not enough to be statistically significant? What's going on with the WD Reds? I can confirm that the 3tb Seagates are not as good as the Hitachi drives, but the Reds should have done better.

There is a known issue with Win7 and the explorer ribbon of death, where directory listing randomly take a long time to come up. What version of unRaid / osx?

Will this port to Android too at some point? Sent from my Nexus 7 using Tapatalk