chaz4070

Thanks for bringing this to unRaid. Is it possible to get this updated to the latest version of Jackett? Or is it possible to add the variable to let users select which version they want? Appreciate it!

I was thinking the same thing. I have attached the long test results. Threshold of "36" and I have 34808. Now I need to find the enclosure I ripped this out of to see if I still have a warranty... Anybody ever played with Seagate's "SeaTools"? Not sure if I should run it before asking for a return. smart.txt

Hi everyone. Had a couple of 3TB Seagates that I got on sale last year that were in an enclosure for a bit. The enclosure failed so I'm claiming the drives for my unRaid. Ran the pre clear on the first with no issue... The second gives what I think are a rather large number of re-allocated sectors but it says everything passed. I only ran the one pass on it and am now in process of running a long SMART test but wanted to post the results here to see what you think. ** Changed attributes in files: /tmp/smart_start_sdd /tmp/smart_finish_sdd ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 114 118 6 ok 74683984 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Reported_Uncorrect = 1 1 0 near_thresh 762 Airflow_Temperature_Cel = 56 60 45 In_the_past 44 Temperature_Celsius = 44 40 0 ok 44 No SMART attributes are FAILING_NOW 120 sectors were pending re-allocation before the start of the preclear. 64 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 8 sectors are pending re-allocation at the end of the preclear, a change of -112 in the number of sectors pending re-allocation. 34808 sectors had been re-allocated before the start of the preclear. 34808 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. Is 34808 a lot for a 3TB? Cause for concern? Thanks for any insight you can provide.

Hi everyone, Been using unRaid now for a while with mostly no issues. Rocking 10 data drives and a parity and cache... Two days ago I had a quick power outage (not on a battery backup which is a horrible oversight I have already corrected) and since then I've had a couple of issues. Disk 4 is disabled. The data is there as I can see it when using telnet and browsing the disk. Disk 6 is "unformatted" and does not show up in /mnt directory. Disk 4 was disabled right after the power outage but I think Disk 6 was ok until yesterday. I am using simple features and the web interface is taking forever or not even loading some pages. When I click on System log I get nothing in the web interface. I used "tail -f --lines=100 /var/log/syslog" to get the attached log. Any and all help is appreciated. My current plan would be to manually copy items off Disk 4 to another disk so I don't lose them and basically sacrifice contents of disk 6... Hopefully somebody here has a better suggestion. Wanted to add that I do have Plex Media Server running in case the logs reflect something regarding it. Thanks for taking a look. Chaz_syslog.txt

Hi all. When I first set up my unRaid I didn't have a lot of forethought and set up different shares for TV Shows and Movies. I have recently added an "Odds & Ends" share and broke out an "Animated Shows" share. Now I want to add a "Christmas Stuff" share. All this would be great but I keep having to add the auto mounts in my login items on my Mac and now I'm thinking it would be *much* easier to have a "Media" share that has folders for all the previous shares. Thoughts? Then the how to of it? I don't have enough space to copy everything first so I'm gonna be stuck using the mv command I think? Plan would be something like this: Create Media share. Create folders for Movies, TV Shows, etc. telnet in and "mv" contents of share Movies to folder Movies in the Media share Is there a better or smarter way to do this? Any help is appreciated! Thanks

I appreciate the heads up - some of the things in the report scared me such as lots of "old age" and "pre-fail." I have another disk that I will replace it with. I attached the report below. Would these errors be causing my original posted issue of the Movies share not expanding to the new data drive? I'm still having a hard time figuring it out as the TVShows and Data shares both added the drive without issue. Thanks again for any help, Chaz Smart report is as follows: Statistics for /dev/sdc 00W2B0_WD-WMAY00266356 smartctl -a -d ata /dev/sdc smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Black family Device Model: WDC WD2001FASS-00W2B0 Serial Number: WD-WMAY00266356 Firmware Version: 01.00101 User Capacity: 2,000,398,934,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sun Nov 13 23:25:15 2011 EST 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: ( 118) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: (29760) 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: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3037) 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 188 187 051 Pre-fail Always - 54610 3 Spin_Up_Time 0x0027 155 154 021 Pre-fail Always - 14208 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 554 5 Reallocated_Sector_Ct 0x0033 192 192 140 Pre-fail Always - 62 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 089 089 000 Old_age Always - 8150 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 46 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 21 193 Load_Cycle_Count 0x0032 190 190 000 Old_age Always - 31951 194 Temperature_Celsius 0x0022 109 091 000 Old_age Always - 43 196 Reallocated_Event_Count 0x0032 139 139 000 Old_age Always - 61 197 Current_Pending_Sector 0x0032 199 197 000 Old_age Always - 361 198 Offline_Uncorrectable 0x0030 200 195 000 Old_age Offline - 123 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 197 155 000 Old_age Offline - 625 SMART Error Log Version: 1 ATA Error Count: 21717 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 21717 occurred at disk power-on lifetime: 8136 hours (339 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 28 70 4b 00 e0 Error: UNC 40 sectors at LBA = 0x00004b70 = 19312 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 28 4f 4b 00 e0 08 3d+11:21:49.315 READ DMA ef 10 02 00 00 00 a0 08 3d+11:21:49.315 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 3d+11:21:49.311 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 3d+11:21:49.311 SET FEATURES [set transfer mode] Error 21716 occurred at disk power-on lifetime: 8136 hours (339 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 28 70 4b 00 e0 Error: UNC 40 sectors at LBA = 0x00004b70 = 19312 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 28 4f 4b 00 e0 08 3d+11:21:47.500 READ DMA ef 10 02 00 00 00 a0 08 3d+11:21:47.500 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 3d+11:21:47.496 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 3d+11:21:47.496 SET FEATURES [set transfer mode] Error 21715 occurred at disk power-on lifetime: 8136 hours (339 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 28 70 4b 00 e0 Error: UNC 40 sectors at LBA = 0x00004b70 = 19312 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 28 4f 4b 00 e0 08 3d+11:21:45.686 READ DMA ef 10 02 00 00 00 a0 08 3d+11:21:45.686 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 3d+11:21:45.682 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 3d+11:21:45.682 SET FEATURES [set transfer mode] Error 21714 occurred at disk power-on lifetime: 8136 hours (339 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 28 70 4b 00 e0 Error: UNC 40 sectors at LBA = 0x00004b70 = 19312 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 28 4f 4b 00 e0 08 3d+11:21:43.871 READ DMA ef 10 02 00 00 00 a0 08 3d+11:21:43.871 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 3d+11:21:43.867 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 3d+11:21:43.867 SET FEATURES [set transfer mode] Error 21713 occurred at disk power-on lifetime: 8136 hours (339 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 28 70 4b 00 e0 Error: UNC 40 sectors at LBA = 0x00004b70 = 19312 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 28 4f 4b 00 e0 08 3d+11:21:42.056 READ DMA ef 10 02 00 00 00 a0 08 3d+11:21:42.056 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 3d+11:21:42.052 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 3d+11:21:42.052 SET FEATURES [set transfer mode] SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed: read failure 60% 8150 7 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.

Sorry about that - I should have added all that first time around... Syslog attached. System specs: Core i3 540 with 8GB of ram. unRaid Plus 5.0-beta12a. 5 data disks in the array plus one parity and one cache drive, pic included of Shares and drives. Thanks again for any assistance, Chaz chazsyslog.txt.zip

Hi everyone, I've found different answers as well as different fixes while looking around the forums/wiki. My dilemma is this: I just added another disk (disk5) to my array as the others were very close to full. I have three shares: TVShows, Data, and Movies. Both TVShows and Data were added as folders on the new drive but I cannot figure out why Movies is not adding. I currently have movies on the cache drive and when I execute the mover script the log shows an error with device full message. I have tried manually adding every disk in the included list and taking them out. I have tried all methods of allocation. I have tried it with 2 as the split level, 7, 99 and just leaving it blank. My current min size free is set to 50GB and the new disk is the only one with enough space to cover that. I have tried setting it up just like TVShows that is working but that didn't work either. Edit: oops forgot to say running 5.0beta12a if that helps. I have seen it here in a few places that adding the Movies folder manually to disk5 may fix this? Any other suggestions? And if this is the fix, would someone be kind enough to post the commands? Disk5 became sda in my array. I can telnet in with no issue but I am not familiar enough navigating with linux/slackware to create a new folder on the correct disk. Edit 2: Figured out to create the directory and it did not fix my issue. Just ran the mover script again and got the same error "Nov 12 20:05:36 Tower shfs/user0: shfs_write: write: (28) No space left on device" so now I'm really stuck. As always, thanks for any help/insight anyone can provide, Chaz

Just filled up my array this weekend and needed another drive... looked around and was shocked by some of the increased prices Thanks for posting, ordered one for in store pickup.

I'm having a similar issue. Posted mine here: http://lime-technology.com/forum/index.php?topic=16301.0 I think I may have stumbled upon the solution - running the mover now to see. I would welcome any suggestions.

Thanks for the quick reply. I have not modified the default settings on the Cache drive - I included a screenshot to show the current settings. Also, when I forced a move, the log showed "Nov 5 09:41:06 Tower logger: *** Skipping any contents from this failed directory *** Nov 5 09:41:06 Tower logger: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1042) [sender=3.0.7] Nov 5 09:41:06 Tower logger: ./TV Shows/Terra Nova/Season 1/Terra.Nova.S01E05.720p.HDTV.X264-DIMENSION.mkv Nov 5 09:41:06 Tower shfs/user0: shfs_mkdir: assign_disk: TV Shows/Terra Nova (28) No space left on device Nov 5 09:41:06 Tower logger: cd+++++++++ TV Shows/Terra Nova/ Nov 5 09:41:06 Tower logger: rsync: recv_generator: mkdir "/mnt/user0/TV Shows/Terra Nova" failed: No space left on device (28) Nov 5 09:41:06 Tower logger: *** Skipping any contents from this failed directory *** Nov 5 09:41:06 Tower logger: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1042) [sender=3.0.7] Nov 5 09:41:06 Tower logger: mover finished Nov 5 10:01:01 Tower crond[1170]: ignoring /var/spool/cron/crontabs/root- (non-existent user)" and nothing was moved. I also just noticed that another user seemed to have a similar issue: http://lime-technology.com/forum/index.php?topic=16303.0 As I was looking around right now I realized that I have both my "Movies" and "TV Shows" shares set to high-water with a minimum 100GB of space. I had assumed this would apply to the share and that if the share spanned multiple disks it would count them all but now I'm thinking it applies to each disk in the share? I have reduced my minimum to 10GB and I am trying the mover again. EDIT: That seems to have worked for me but Oh S**t now I'm almost out of space! Time to invest in another drive.

Hi all. I'm running 5.0 beta12a and just recently got errors saying my drive was full when trying to copy items over. I have 340+GB free in my array but it appears my cache drive is full... its like the mover script isn't working anymore. Also, I thought if the cache was full it would bypass and write straight to the array disks? I hit the "Log" button in the upper right of the WebUI and here is the only output I received: "Nov 5 07:01:01 Tower crond[1170]: ignoring /var/spool/cron/crontabs/root- (non-existent user) Nov 5 08:01:01 Tower crond[1170]: ignoring /var/spool/cron/crontabs/root- (non-existent user) Nov 5 08:42:17 Tower shfs/user: cache disk full Nov 5 08:42:17 Tower shfs/user: shfs_create: assign_disk: Movies/V For Vendetta (2006)/airline-V.pour.vendetta_1080p.mkv (28) No space left on device Nov 5 08:42:17 Tower shfs/user: cache disk full Nov 5 08:42:17 Tower shfs/user: shfs_create: assign_disk: Movies/V For Vendetta (2006)/airline-V.pour.vendetta_1080p.mkv (28) No space left on device Nov 5 08:43:10 Tower shfs/user: cache disk full Nov 5 08:43:10 Tower shfs/user: shfs_create: assign_disk: Movies/V For Vendetta (2006)/airline-V.pour.vendetta_1080p.mkv (28) No space left on device Nov 5 08:43:10 Tower shfs/user: cache disk full Nov 5 08:43:10 Tower shfs/user: shfs_create: assign_disk: Movies/V For Vendetta (2006)/airline-V.pour.vendetta_1080p.mkv (28) No space left on device" I've attached screenshot of my main page as well. Edit: Found where to force the mover to run but any ideas on why it didn't run automatically? It has been working great for me. Thanks for any help/suggestions!

I wanted to say thanks for such a quick reply. Upgraded last night with no issues.

Hi everyone. Been running 4.6 for while now with no issues. I run Plex which uses the folder time stamp on quick scans so I *really* want to move up to 5.08 or later that has this fixed. I went ahead and updated to 4.7 but I am confused by the wiki upgrade instructions to go to 5. I am assuming I will have to follow step 4) "Go to Utils/New Permissions and execute that utility to change file ownership and permission settings. This is necessary for proper operation of the 5.0 security model" but its not listed under any versions other than the first beta as it says "with the exception of step 4 (because presumably you already did this)" So to jump right to 5.12 I should run the util correct? Thanks for any help, Charlie