umirza85

Sorry I didnt get a chance to test earlier, was really late at night. Figured I'd give it a try before work: I put the sky.ko file in root and ran the commands you said & they ran without error. I then put the server to sleep and it went to sleep and I could see the link was active. But I still couldn't get the server to wake. I can see the activity lights on the router also flashing when I send the WOL signal a few times in a row. I then tried the commands again and this time restarted ther server, but still the same result. Sorry maybe I am doing something wrong?

Thanks so much, you're awesome!! -rc16 Ill test and comment back here to verify. This is my only issue with Unraid since I keep the server so far from my tv and I usually dont keep the server on.

https://bugzilla.kernel.org/show_bug.cgi?id=13764 I found this link talking about a fix (starting from comment #30) Someone says that "The problem was quite silly: Y2_HW_WOL_ON and Y2_HW_WOL_OFF were used backward." The last comments are that they have fixed the issue. I was wondering how I would edit these lines they are talking about? Im assuming this would be out of my hands as I would need to edit the sky2.c file then 'make' it? (This is another post that seems to have a similar solution http://lkml.indiana.edu/hypermail/linux/kernel/1111.0/00568.html )

I have this chip "Marvell PCIe 88E8053 Gigabit/ LAN Controller" and no matter what I do I cant get WOL to work. I booted up in windows and confirmed that WOL does work in windows flawlessly. Just when I put my Unraid server to sleep it wont wake - I am using the command that sets the 'g' flag before sleep.

Also i enaled debugging for the sleep plugin - here is the log: Jun 16 13:05:40 Tower logger: /usr/sbin/rpc.nfsd 8 Jun 16 13:05:40 Tower logger: /usr/sbin/rpc.mountd Jun 16 13:05:40 Tower mountd[19356]: Kernel does not have pseudo root support. Jun 16 13:05:40 Tower mountd[19356]: NFS v4 mounts will be disabled unless fsid=0 Jun 16 13:05:40 Tower mountd[19356]: is specfied in /etc/exports file. Jun 16 13:05:40 Tower emhttp: shcmd (278): /usr/local/sbin/emhttp_event svcs_restarted Jun 16 13:05:40 Tower emhttp_event: svcs_restarted Jun 16 13:06:40 Tower logger: s3_sleep: Disk activity detected. Reset all counters Jun 16 13:06:42 Tower s3_sleep: ============================================== Jun 16 13:06:42 Tower s3_sleep: command-args=-q Jun 16 13:06:42 Tower s3_sleep: action mode=sleep Jun 16 13:06:42 Tower s3_sleep: check array=no Jun 16 13:06:42 Tower s3_sleep: exclude cache=- Jun 16 13:06:42 Tower s3_sleep: check network=no Jun 16 13:06:42 Tower s3_sleep: check device= Jun 16 13:06:42 Tower s3_sleep: check SSH=no Jun 16 13:06:42 Tower s3_sleep: check TTY=no Jun 16 13:06:42 Tower s3_sleep: version=2.1.0 Jun 16 13:06:42 Tower s3_sleep: ---------------------------------------------- Jun 16 13:06:42 Tower s3_sleep: killing s3_sleep process 19271 Jun 16 13:06:42 Tower s3_sleep: ============================================== Jun 16 13:06:42 Tower s3_sleep: command-args=-C 1 -a -m 1 -e eth0 -F -w g -D 1 Jun 16 13:06:42 Tower s3_sleep: action mode=sleep Jun 16 13:06:42 Tower s3_sleep: check array=yes Jun 16 13:06:42 Tower s3_sleep: exclude cache=- Jun 16 13:06:42 Tower s3_sleep: check network=no Jun 16 13:06:42 Tower s3_sleep: check device= Jun 16 13:06:42 Tower s3_sleep: check SSH=no Jun 16 13:06:42 Tower s3_sleep: check TTY=no Jun 16 13:06:42 Tower s3_sleep: version=2.1.0 Jun 16 13:06:42 Tower s3_sleep: ---------------------------------------------- Jun 16 13:06:42 Tower s3_sleep: s3_sleep process ID 20139 started, To terminate it, type: s3_sleep -q Jun 16 13:06:42 Tower logger: s3_sleep: Disk activity detected. Reset all counters Jun 16 13:06:51 Tower emhttp: Spinning down all drives... Jun 16 13:06:51 Tower kernel: mdcmd (37): spindown 0 Jun 16 13:06:52 Tower kernel: mdcmd (38): spindown 1 Jun 16 13:06:53 Tower kernel: mdcmd (39): spindown 2 Jun 16 13:06:54 Tower kernel: mdcmd (40): spindown 3 Jun 16 13:07:42 Tower logger: s3_sleep: Disk activity detected. Reset all counters Jun 16 13:08:42 Tower logger: s3_sleep: Disk activity detected. Reset all counters

Ive upgraded to the latest rc15. Within simpleFeatures it says ive got "s3_sleep version: 2.1.0" and I have - 'Wait for array inactivity' to 'Yes' - 'Extra delay after array inactivity' to '1'. - 'Wait for network inactivity' to 'No' - 'Wait for user login inactivity' to 'No' I manually spin down the drives and wait but the server wont shutdown. Doing it this way to test sleep used to work everytime but for some reason since rc12 its stopped working. I can manually put the server to sleep and it goes to sleep/wakes up perfectly - not sure why Unraid wont send the sleep command? I tried changing the spin down times in the actual disk, then also changing them back to 'use default' which is 15 mins - but that shouldnt matter since when I refresh the page even after 20 mins its showing the drives as asleep. Also does it matter if I have a drive attached thats not in the array? I am using that as a backup?

Just doing a parity check, will change spin-down time from 'default' to '15 mins' for all disks manually and see if that makes a difference. Though Ive noticed that on default, and setting the global spin-down time to 15mins that all my disks are spun-down since the green ball is flashing. But its worth a shot I guess.

Im not really sure what happened after i upgraded to rc12. Ive always had simplefeatures installed with the sleep plugin and ive never had an issue with my array going to sleep x amount of time after the drives spin down. Now when I turn on sleep and set it to sleep 15mins after drive inactivity the server never sleeps. Does anybody else have ths issue or know why the sleep function stopper working? I can use sleep from the simpleFeatures main menu and it puts my server to sleep so i know that sleep does work. Thanks

Good point, I agree. Thanks for the input.

I got a red balled drive today I ran a SMART short test and got this back. Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed: read failure 90% 181 I had a spare already precleared so i am currently rebuilding my array with the spare. I know I can preclear the second drive while my array is being rebuilt, but the question is should I? will it affect the performance of the rebuild? Also if anyone has any info on that SMART error it would be appreciated, do you think I can just run a preclear on this drive and use it as my warm-standby? Thanks

I just had a red ball, ive pulled a smart report i was wondering if someone can help me decipher whats wrong. I just restarted the server after it being off all day while i was at work. Im assuming I should ren a preclear on it and then give the drive one more chance in my array. Its a WD 1.5tb EADS but as you can tell by the lifetime i dont use it very often until i put it in my array a few weeks ago. === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green family Device Model: WDC WD15EADS-00P8B0 Serial Number: WD-WMAVU0233657 Firmware Version: 01.00A01 User Capacity: 1,500,301,910,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: Thu Apr 25 19:32:34 2013 EDT 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: (0x85) Offline data collection activity was aborted 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: (36300) 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: (0x303f) 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 0x002f 200 200 051 Pre-fail Always - 407 3 Spin_Up_Time 0x0027 183 175 021 Pre-fail Always - 5850 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1186 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 098 098 000 Old_age Always - 2131 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 - 667 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 385 193 Load_Cycle_Count 0x0032 198 198 000 Old_age Always - 8241 194 Temperature_Celsius 0x0022 125 100 000 Old_age Always - 25 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 001 000 Old_age Always - 57021 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 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 2131 - # 2 Extended offline Aborted by host 90% 2131 - # 3 Extended offline Aborted by host 90% 2131 - # 4 Short offline Completed without error 00% 2104 - 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.

Maybe Im just not reading correctly how Btrfs works. So what it sounds like you're saying is that is makes a backup of your cache drive until it has the chance to transfer to the array then it would spin down the array and go back to using the cache + cache backup?

I happened upon this post http://lime-technology.com/forum/index.php?topic=21007.0 about WD drives and autoparking. Im wondering if this is still an issue on EADS drives and if I should run the wdidle? or should I not worry about it.

That escalated off-topic quickly so im assuming butterfs can support multiple drive failures, but it would keep all the disks spun up all the time? wouldnt that go against one of the main pros of unraid of only spinning up disks you need? I would think it would just be easier to implement a second parity.

Could a 64bit version of Unraid support multiple parity drives? and would this be a sought after feature for anybody else?

So currently I have a 32bit cpu, I was just waiting until 5.0 to move to 64 bit (since im assuming thats when 64bit support will be added). Since this rc is the last one before 5.0 final would it be a good time to upgrade now? or do i still have some time?

Great thanks thats all I was looking for.

I have a build that is pretty much exactly this, except I will be using an ivy bridge Intel Celeron G1620 (Dual core) as this CPU is almost $75 cheaper. I know this cpu is more than enough to have a few streams going at once, but what would the performance be like transcoding streams or running sab??

Thanks, great to know i can just switch CPU's. As for my motherboard its a P5AD2-E Premium, here is the list of supported cpus not sure if its been updated lately but it doesnt seem to supposrt and of the core 2 duos, this board was one of the first socket 775's....guess I jumped the gun back then Would you be able to check if there is any better choice of CPU than I picked? http://www.asus.com/Motherboard/P5AD2E_Premium#support_CPU heres a list of P4s went with that once since it just has a lower TDP and is the same as my current P4 550 - which even underclocked runs like an oven http://en.wikipedia.org/wiki/List_of_Intel_Pentium_4_microprocessors#Prescott_.2890.C2.A0nm.29_2

I found im able to upgrade my P4 Socket 775 to a cpu that supports 64 bit. Since it seems like Unraid will be moving to a 64 bit platform soon i might as well make this upgrade. Im just wondering for my current installation (latest rc) if i change my cpu will i need to change anything within unraid - or do i just switch the cpu and turn on and everything is the same? And will this cpu be sufficient? Pentium 4 HT 650 SL8Q5 (R0) 3.4 GHz L2Cache:2MB FSB:800 MT/s TDP:84 W LGA 775 The tdp is lower than my current p4 550 (115w) so this will also hopefully give me some cooler temps (along with underclocking it) Thanks,

I plan on staying with 32 bit until my motherboard dies. I havent seen anything with 8 on board sata ports that is cheap. Like was just mentioned if all you want is a file server i guess its possible to stick with 5.0, and im sure there are a lot of people using Unraid who are using it because they can re-purpose their old computers - would almost be a shame to cut them off. Im sure alot of the extra tweaks/mods and fixes are also done by people who are on old machines and are looking for ways to tweak every extra little bit of functionality. On the other hand the improvements that are supposedly possible with 64 bit do seem exciting. Guess we're at that point with hardware where its hard to decide whether its time to move on or keep supporting older tech.

No, not broken. I was using NFS with 4.7 and all was good, when I moved to v5RC8a, I started having the stale file handle issue. Never researched it more than people saying it was still happening and to switch to SMB so I did... What exactly is the stale file issue?

thanks again dgaschk will try it out tonight. I havent had any problems with NFS other than not being able to figure out how to access a private share properly. But the Secure share works great as a Read Only, its noticeably faster than when I was using SMB.

The SimpleFeatures plugin lets you enter rules after you select private for a share under NFS. It seems to just add the lines to the default entry in the exports file. Should I just not enter anything?

Is there a reason the NFS rules box will only allow a certain amount of characters, is there a way to remove this limit?