reggierat

Having the same issue with cadvisor. have also tried manually added the file to the images folder on the flash and it is not getting picked up from there either.

I'm running 2 instances of couch potato without any problems, one is for kids movies and the other is for the rest. The kids couch potato pushes movies into a different share which is then updated by a second instance of kodi-headless. Works flawlessly

In the end i modified the s3 sleep script to spin up all my drives when the server comes out of sleep. This is atleast a work around for the issue

I realise it is not officially supported, but this was working perfectly up until b14. The 'disk activity' that occurs prevents the server from going back to sleep if the above conditions have been met. ie server wakes up but a particular drive has not been spun up before the server is due to go back to sleep. if i could just get a post wake command to spin all drives up as a work around this would atleast get it behaving as it was before the bug started occurring

Is there any format the post sleep commands should take, I have tried to add a command to spin up all drives after waking as a bandaid for the bug I'm experiencing but it doesn't seem to run the command. Looking in syslog it doesn't look like post run commands are being run http://lime-technology.com/forum/index.php?topic=39355.0

As a bandaid Im thinking I just spin up all drives on wake. Could someone help me with the custom command to do this i tested this from the console which spins up all drives for disknum in 0 `ls /dev/md* | sed "sX/dev/mdXX"`; do /root/mdcmd spinup $disknum; done but adding this to the area for commands after wake does nothing

here is a syslog with docker disabled and all plugins removed except s3_sleep. I have kept this installed as this is what im using to check on the mystery disk activity In this syslog, rebooted server, waited 5mins, manually spun down all disks, observed that disks were spun down, manually put server to sleep, manually woke up using WOL, checked all disks were still showing as spun down. At 7.05am enabled s3 debug logging and disks are still spun down but disk activity is being reported. This is in fact before any temps have been taken so this may have just been confusing the issue previously. To summarize the issue occurs if a disk has not been spun up after waking from sleep. Even though the disk is spun down in the gui it incorrectly is reporting disk activity for some reason. Manually spinning the drive(s) up always fixes the issue. syslog.zip

issue still persists, all disks will be spun down in the GUI, but 1 disk (sde) will still be reporting 'disk activity' according to the debug for s3_sleep. Does anyone have any idea how this is possible if the disk is spun down?

I have the same issue as above with plugin update messages not being displayed. Browser cache has been cleared. I also have an issue that if a drive is not spun up the first time polling attributes timer runs after waking the server from sleep, and if the drive is not subsequently spun up that the drive will continue to report 'disk activity' according to the s3 sleep debug log. The drive will be clearly spun down in the GUI but will be reporting temp and showing disk activity according to the debug log. This behavior persists until the drive is manually spun up or is spun up by the os

I'm just confused by the behavior I'm seeing, a disk spun down in the GUI is preventing sleep from occurring due to disk activity. The only clue I have is that it is still reporting temperature

how does s3_sleep determine disk activity? the reason im curious is that i'm experiencing an issue where if all my drives are spun down but anyone of them are still reporting a temperature reading in the GUI then the log for s3_sleep is reporting disk activity for that drive, as far as i can tell there is no actual disk activity since the drive is spun down. to resolve the issue i have to spin up the affected drive manually and then once it spins down again it will stop reporting temperature. http://lime-technology.com/forum/index.php?topic=39355.0 http://lime-technology.com/forum/index.php?topic=39145.0

Just observing things again today, I don't understand the inner workings enough to know for sure but it seems the disk is getting out of sync with the others in regards to its temp and spun up/down status. When the server is woken up after a period of time all the disks are getting spun up except disk 3 (because its currently empty and the mover hasn't chosen to start writing to it yet). After the polling_attribute timer all disk temps are read including the disk that is spun down (disk 3). Now after some inactivity all disks will be spun down and temps will stop being reported by the GUI. The drive that was not spun up will continue to report its temp until I finally spin it up manually and either let it spin down on its own or spin it foen manually.

The issue first popped up in B14 after doing some maintenance on my array. 2 x 4TB drives were purchased, one of these was used to replace by 3tb parity drive, and then my two oldest drives were replaced with these 2 drives, the 3tb and 4tb. I also used this opportunity to migrate all array disks to XFS. It was only after moved to XFS that i started noticing the problem, up until then b14 had been very good. I have now moved to beta15 and the issue still persists. As you can see from the attached screenshot all array drives are spun down, disk 3 is still reported it's temperature and it is also reporting 'disk activity' in the syslog when i turn on debugging for s3 sleep. All cabling has been doubled checked, and i replaced the sata cable on disk 3 If i manually spin up all drives and then manually spin them down then the issue goes away. It was is most often reported on disk 3 but occasionally disk 1 and disk 2 so i don't really think the drive is at fault. smart report for affected drive Disk 3 attached to port: sde ID# ATTRIBUTE NAME FLAG VALUE WORST THRESH TYPE UPDATED FAILED RAW VALUE 1 Raw Read Error Rate 0x000b 100 100 016 Pre-fail Always Never 0 2 Throughput Performance 0x0005 136 136 054 Pre-fail Offline Never 93 3 Spin Up Time 0x0007 135 135 024 Pre-fail Always Never 406 (Average 407) 4 Start Stop Count 0x0012 099 099 000 Old age Always Never 7950 5 Reallocated Sector Ct 0x0033 100 100 005 Pre-fail Always Never 0 7 Seek Error Rate 0x000b 100 100 067 Pre-fail Always Never 0 8 Seek Time Performance 0x0005 146 146 020 Pre-fail Offline Never 29 9 Power On Hours 0x0012 097 097 000 Old age Always Never 24437 10 Spin Retry Count 0x0013 100 100 060 Pre-fail Always Never 0 12 Power Cycle Count 0x0032 100 100 000 Old age Always Never 1380 192 Power-Off Retract Count 0x0032 094 094 000 Old age Always Never 7951 193 Load Cycle Count 0x0012 094 094 000 Old age Always Never 7951 194 Temperature Celsius 0x0002 200 200 000 Old age Always Never 30 (Min/Max 8/46) 196 Reallocated Event Count 0x0032 100 100 000 Old age Always Never 0 197 Current Pending Sector 0x0022 100 100 000 Old age Always Never 0 198 Offline Uncorrectable 0x0008 100 100 000 Old age Offline Never 0 199 UDMA CRC Error Count 0x000a 200 200 000 Old age Always Never 378 syslog.zip

Clear cache fixed mine. Celeron G1610 is not throttling at all

All installed, looks good so far

ROFL!!!

How about now? Too soon?

itching for a new beta/rc.. just wondering if there have been any changes that may affect the spin down issue i've been having since migrating my disks to XFS. Since doing this i'm getting disk showing activity in the log even though they are showing spun down in the interface http://lime-technology.com/forum/index.php?topic=39145.msg365359#msg365359

Just had success spinning all drives up and back down again, seems to have reset something. On a whim I have also disabled cAdvisor as it's a recent install

I am running the latest Beta. Apr 11 07:43:44 Tower s3_sleep: Disk activity on going: sde Apr 11 07:43:44 Tower s3_sleep: Disk activity detected. Reset timers. Apr 11 07:44:44 Tower s3_sleep: Disk activity on going: sde Apr 11 07:44:44 Tower s3_sleep: Disk activity detected. Reset timers. anyway to tell what this Disk activity, the drive shows spun down whilst this message is being logged, but temperature still being reported. whether it's coincidence or not this drive is almost totally empty, except for the one file i copied to it to make sure i could write to it ok, at what point does the mover decide to start using the drive? all shares are set to high-water i believe [edit] and for the sake of thoroughness i have swapped my sata cable over

I will reboot my server tomorrow and confirm which settings I am using. After ditching the realtek Nic it's been working flawlessly.

Hmm bit at a loss with this. Have rebooted several times, issue usually occurs with disk 3 but a couple of times it affected disk 2. Disk appears spun down in the GUI but temp is still being reported and s3_sleeps debug shows disk activity to the drive. Disk 3 has only one file on it so I doubt it is actual file access

i find it strange that this has only popped up now though. I recently replaced my two oldest drives in the array, then decided it was a good time to migrate the file systems. Other then these two events things have been working flawlessly. I did have some issues with the server waking from sleep but that was fixed by purchasing an Intel NIC and not using my MB's onboard Realtek adaptor.

Disk 3 attached to port: sde Model Family: Hitachi Deskstar 5K3000 Device Model: Hitachi HDS5C3020ALA632 Serial Number: ML0220F30DYRWD LU WWN Device Id: 5 000cca 369c5e416 Firmware Version: ML6OA580 User Capacity: 2,000,398,934,016 bytes [2.00 TB] Sector Size: 512 bytes logical/physical Rotation Rate: 5940 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, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Mon Apr 6 05:24:44 2015 AEST SMART support is: Available - device has SMART capability. SMART support is: Enabled SMART overall-health : PASSED ID# ATTRIBUTE NAME FLAG VALUE WORST THRESH TYPE UPDATED FAILED RAW VALUE 1 Raw Read Error Rate 0x000b 100 100 016 Pre-fail Always Never 0 2 Throughput Performance 0x0005 136 136 054 Pre-fail Offline Never 92 3 Spin Up Time 0x0007 135 135 024 Pre-fail Always Never 405 (Average 406) 4 Start Stop Count 0x0012 099 099 000 Old age Always Never 7915 5 Reallocated Sector Ct 0x0033 100 100 005 Pre-fail Always Never 0 7 Seek Error Rate 0x000b 100 100 067 Pre-fail Always Never 0 8 Seek Time Performance 0x0005 144 144 020 Pre-fail Offline Never 30 9 Power On Hours 0x0012 097 097 000 Old age Always Never 24314 10 Spin Retry Count 0x0013 100 100 060 Pre-fail Always Never 0 12 Power Cycle Count 0x0032 100 100 000 Old age Always Never 1350 192 Power-Off Retract Count 0x0032 094 094 000 Old age Always Never 7916 193 Load Cycle Count 0x0012 094 094 000 Old age Always Never 7916 194 Temperature Celsius 0x0002 222 222 000 Old age Always Never 27 (Min/Max 8/46) 196 Reallocated Event Count 0x0032 100 100 000 Old age Always Never 0 197 Current Pending Sector 0x0022 100 100 000 Old age Always Never 0 198 Offline Uncorrectable 0x0008 100 100 000 Old age Offline Never 0 199 UDMA CRC Error Count 0x000a 200 200 000 Old age Always Never 378 even though the default poling time is 30mins, this drive is still reporting temp several hour after everything has been spun down. Will reseat cable next

Last week i have finished my conversion of all ReiserFS drives over to XFS. Since doing that one of my drives, Disk 3 will sometimes continue to report it's temperature to the system long after it has been spun down. This same drive is also preventing my server from sleeping due to 'disk activity' [Edit] It definitely effects other drives, but this one seems more often syslog.zip