July 10, 201312 yr This is an unauthorized mod of the SimpleFeatures S3 Sleep Plugin. There will be no support by the original developers! I made this for myself and thought I would share it for people who have the same or a similar problem, which made me do the mod. If you test this, you do this on your own risk! If you have problems, report them in this thread only and not in the SimpleFeatures one. If speeding_ant is interested the mod might be incorporated into SimpleFeatures in the future, but until then it is a development testing release. So why did I write the mod?: I wanted to have plex, but that killed s3 sleep on my system, because plex is constantly accessing the drive it is installed on. As it is not recommended to install on the flash drive (too many writes will kill the drive really quick), I decided to put plex on a ssd outside of the array. I was assuming drives outside the array would not be included in the inactivity checks, so s3 sleep would have worked again. This proved to be a false assumption. The SimpleFeatures plugin checks all drives. As the ssd always reported a state of active/idle my system now didn't sleep anymore, even if plex was deactivated. I really did shoot myself in the feet, there. Long story short, I decided to change the S3 Sleep plugin to make it work again. So what does it do?: The modified plugin gives the user the ability to exclude drives outside the array from the activity check. You may choose to don't exclude drives outside the array, exclude only selected drives, exclude all but the selected drives or exclude all drives outside the array. Option 2 and 3 are not yet perfect, as the used "sdx" identification is not a permanent one and might change on boot. Installation: At the moment you will have to download both files and place them in the correct folders. Make Backups of your original files! If you don't know where they belong, you should wait with testing until I think it's save enough to make installation a bit easier. Download links: simpleFeatures.s3.sleep-1.0.10-i486-1.txz simpleFeatures.s3.sleep-1.0.10-noarch-1.plg
July 11, 201312 yr It installed fine last night which is good. I haven't seen my server go to sleep yet though. I have debugging turned on and pointed it to the flash drive, but I do not see any logs. Here are the last few lines of my syslog showing drives spinning down early this morning. At some point in that time I would have expected the server to sleep. It appears drives 0,1,2,4 spundown, but not drive 3? Jul 11 03:17:41 Tower logger: mover finished Jul 11 03:33:21 Tower kernel: mdcmd (65): spindown 0 Jul 11 03:33:22 Tower kernel: mdcmd (66): spindown 4 Jul 11 03:48:33 Tower kernel: mdcmd (67): spindown 1 Jul 11 03:48:34 Tower kernel: mdcmd (68): spindown 2 Jul 11 03:55:45 Tower emhttp: shcmd (56): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Jul 11 04:30:48 Tower emhttp: shcmd (57): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Jul 11 05:05:52 Tower emhttp: shcmd (58): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Jul 11 05:40:45 Tower emhttp: shcmd (59): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Jul 11 06:50:53 Tower emhttp: shcmd (60): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Jul 11 07:25:56 Tower emhttp: shcmd (61): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Jul 11 07:58:50 Tower kernel: mdcmd (69): spindown 1 Jul 11 08:00:50 Tower emhttp: shcmd (62): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Jul 11 08:35:54 Tower emhttp: shcmd (63): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Jul 11 09:15:48 Tower emhttp: shcmd (64): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Jul 11 09:42:11 Tower kernel: mdcmd (70): spindown 2 Jul 11 09:43:32 Tower kernel: mdcmd (71): spindown 1 Jul 11 09:47:52 Tower emhttp: shcmd (65): /usr/sbin/hdparm -y /dev/sdg &> /dev/null
July 12, 201312 yr So, my server is not sleeping and I am not getting the log on the flash drive as I chose in the settings. This is all I see in the log: Jul 12 03:51:22 Tower emhttp: shcmd (86): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Jul 12 04:26:16 Tower emhttp: shcmd (87): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Jul 12 05:01:20 Tower emhttp: shcmd (88): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Jul 12 05:36:03 Tower emhttp: shcmd (89): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Jul 12 06:11:17 Tower emhttp: shcmd (90): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Jul 12 06:46:20 Tower emhttp: shcmd (91): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Jul 12 07:21:14 Tower emhttp: shcmd (92): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Jul 12 07:56:17 Tower emhttp: shcmd (93): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Jul 12 08:39:41 Tower emhttp: shcmd (94): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Jul 12 09:48:39 Tower emhttp: shcmd (95): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Jul 12 10:16:11 Tower emhttp: shcmd (96): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Jul 12 10:51:55 Tower emhttp: shcmd (97): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Jul 12 11:26:29 Tower emhttp: shcmd (98): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Jul 12 12:16:13 Tower kernel: mdcmd (101): clear
July 12, 201312 yr Author Try setting the log to syslog. Thats the only mode I tested. It should provide info on which drive is blocking the sleep. I'll have a look at the flash logging mode.
July 12, 201312 yr Author Flash logging mode works fine for me. Did you look in /boot/logs/s3_sleep.log? The log should show something like this: Fri Jul 12 18:26:20 CEST 2013: Devicelist: /dev/sdb /dev/sdd /dev/sde /dev/sdf /dev/sdg Fri Jul 12 18:26:20 CEST 2013: /dev/sdb drive state is: active/idle Fri Jul 12 18:26:20 CEST 2013: Disk activity detected. Reset all counters Devicelist is the list of devices that are checked for disc activity. And then the active drives and their state message will be displayed.
July 12, 201312 yr Yeah, I looked there. I got nothing. That folder is empty. Currently I have it set to Syslog and Flash. I'm not sure if it is even logging to the Syslog properly. I just now stopped it, changed setting to exclude the cache and restarted it. Let's see what happens. Jul 12 12:24:40 Tower s3_sleep: --- !!! unauthorized mod by SlrG !!! --- Jul 12 12:24:40 Tower s3_sleep: command-args=-C 1 -a -c -m 30 -e eth0 -p /usr/local/bin/postRun-D 1 Jul 12 12:24:40 Tower s3_sleep: action mode=sleep Jul 12 12:24:40 Tower s3_sleep: check array=yes Jul 12 12:24:40 Tower s3_sleep: exclude flash=yes (/dev/sdc) Jul 12 12:24:40 Tower s3_sleep: exclude cache=/dev/sdg Jul 12 12:24:40 Tower s3_sleep: exclude outside=no () Jul 12 12:24:40 Tower s3_sleep: check network=no Jul 12 12:24:40 Tower s3_sleep: check device= Jul 12 12:24:40 Tower s3_sleep: check SSH=no Jul 12 12:24:40 Tower s3_sleep: check TTY=no Jul 12 12:24:40 Tower s3_sleep: version=2.1.1 Jul 12 12:24:40 Tower s3_sleep: ---------------------------------------------- Jul 12 12:24:40 Tower s3_sleep: s3_sleep process ID 27158 started, To terminate it, type: s3_sleep -q
July 13, 201312 yr Author Just tested logging to syslog and flash. Works fine for me. The snippet you posted looks alright so far, but it only shows the start of the script. There should appear devicelist and state lines like I posted before. If you only want to exclude the cache drive, you don't need the modified version. The original plugin supports this, too.
July 14, 201312 yr I plan on adding some other non array drives as well. The old plugin was not sleeping even when ignoring the cache for some reason. I wonder why my logging is not working properly for me. That snippet of my log was all that was there. Sent from my SPH-D710 using Tapatalk 2
July 16, 201312 yr After ignoring my cache drive, the system is sleeping just fine. Oddly though I am still not getting logs on the flash drive even though I have it set to both syslog and flash. Below is the log from syslog from the time mover finishe until the last entry after I woke the server this morning at 11:46. Does it contain what you would expect? Jul 16 03:09:44 Tower logger: mover finished Jul 16 03:42:18 Tower kernel: mdcmd (40): spindown 3 Jul 16 03:42:18 Tower kernel: mdcmd (41): spindown 4 Jul 16 04:02:30 Tower emhttp: shcmd (48): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Jul 16 04:37:33 Tower emhttp: shcmd (49): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Jul 16 05:12:36 Tower emhttp: shcmd (50): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Jul 16 05:47:50 Tower emhttp: shcmd (51): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Jul 16 07:06:47 Tower emhttp: shcmd (52): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Jul 16 07:11:31 Tower kernel: md: sync done. time=24996sec Jul 16 07:11:31 Tower kernel: md: recovery thread sync completion status: 0 Jul 16 07:26:39 Tower kernel: mdcmd (42): spindown 0 Jul 16 07:26:40 Tower kernel: mdcmd (43): spindown 1 Jul 16 07:26:40 Tower kernel: mdcmd (44): spindown 2 Jul 16 07:33:11 Tower emhttp: shcmd (53): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Jul 16 07:56:21 Tower kernel: PM: Syncing filesystems ... done. Jul 16 11:46:52 Tower kernel: Freezing user space processes ... (elapsed 0.01 seconds) done. Jul 16 11:46:52 Tower kernel: Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. Jul 16 11:46:52 Tower kernel: Suspending console(s) (use no_console_suspend to debug) Jul 16 11:46:52 Tower kernel: sd 5:0:0:0: [sdg] Synchronizing SCSI cache Jul 16 11:46:52 Tower kernel: sd 5:0:0:0: [sdg] Stopping disk Jul 16 11:46:52 Tower kernel: sd 4:0:0:0: [sdf] Synchronizing SCSI cache Jul 16 11:46:52 Tower kernel: sd 3:0:0:0: [sde] Synchronizing SCSI cache Jul 16 11:46:52 Tower kernel: sd 4:0:0:0: [sdf] Stopping disk Jul 16 11:46:52 Tower kernel: sd 2:0:0:0: [sdd] Synchronizing SCSI cache Jul 16 11:46:52 Tower kernel: sd 1:0:0:0: [sdb] Synchronizing SCSI cache Jul 16 11:46:52 Tower kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Jul 16 11:46:52 Tower kernel: sd 3:0:0:0: [sde] Stopping disk Jul 16 11:46:52 Tower kernel: sd 1:0:0:0: [sdb] Stopping disk Jul 16 11:46:52 Tower kernel: sd 0:0:0:0: [sda] Stopping disk Jul 16 11:46:52 Tower kernel: sd 2:0:0:0: [sdd] Stopping disk Jul 16 11:46:52 Tower kernel: serial 00:06: disabled Jul 16 11:46:52 Tower kernel: pcieport 0000:00:1c.5: wake-up capability enabled by ACPI Jul 16 11:46:52 Tower kernel: pcieport 0000:00:1c.4: wake-up capability enabled by ACPI Jul 16 11:46:52 Tower kernel: PM: suspend of devices complete after 500.323 msecs Jul 16 11:46:52 Tower kernel: PM: late suspend of devices complete after 0.134 msecs Jul 16 11:46:52 Tower kernel: ehci_hcd 0000:00:1d.7: wake-up capability enabled by ACPI Jul 16 11:46:52 Tower kernel: uhci_hcd 0000:00:1d.2: wake-up capability enabled by ACPI Jul 16 11:46:52 Tower kernel: uhci_hcd 0000:00:1d.1: wake-up capability enabled by ACPI Jul 16 11:46:52 Tower kernel: uhci_hcd 0000:00:1d.0: wake-up capability enabled by ACPI Jul 16 11:46:52 Tower kernel: ehci_hcd 0000:00:1a.7: wake-up capability enabled by ACPI Jul 16 11:46:52 Tower kernel: uhci_hcd 0000:00:1a.2: wake-up capability enabled by ACPI Jul 16 11:46:52 Tower kernel: uhci_hcd 0000:00:1a.1: wake-up capability enabled by ACPI Jul 16 11:46:52 Tower kernel: uhci_hcd 0000:00:1a.0: wake-up capability enabled by ACPI Jul 16 11:46:52 Tower kernel: PM: noirq suspend of devices complete after 47.902 msecs Jul 16 11:46:52 Tower kernel: ACPI: Preparing to enter system sleep state S3 Jul 16 11:46:52 Tower kernel: PM: Saving platform NVS memory Jul 16 11:46:52 Tower kernel: Disabling non-boot CPUs ... Jul 16 11:46:52 Tower kernel: CPU 1 is now offline Jul 16 11:46:52 Tower kernel: CPU 2 is now offline Jul 16 11:46:52 Tower kernel: CPU 3 is now offline Jul 16 11:46:52 Tower kernel: Extended CMOS year: 2000 Jul 16 11:46:52 Tower kernel: ACPI: Low-level resume complete Jul 16 11:46:52 Tower kernel: PM: Restoring platform NVS memory Jul 16 11:46:52 Tower kernel: Extended CMOS year: 2000 Jul 16 11:46:52 Tower kernel: Enabling non-boot CPUs ... Jul 16 11:46:52 Tower kernel: Booting Node 0 Processor 1 APIC 0x2 Jul 16 11:46:52 Tower kernel: Initializing CPU#1 Jul 16 11:46:52 Tower kernel: CPU1 is up Jul 16 11:46:52 Tower kernel: Booting Node 0 Processor 2 APIC 0x1 Jul 16 11:46:52 Tower kernel: Initializing CPU#2 Jul 16 11:46:52 Tower kernel: CPU2 is up Jul 16 11:46:52 Tower kernel: Booting Node 0 Processor 3 APIC 0x3 Jul 16 11:46:52 Tower kernel: Initializing CPU#3 Jul 16 11:46:52 Tower kernel: CPU3 is up Jul 16 11:46:52 Tower kernel: ACPI: Waking up from system sleep state S3 Jul 16 11:46:52 Tower kernel: uhci_hcd 0000:00:1a.0: wake-up capability disabled by ACPI Jul 16 11:46:52 Tower kernel: uhci_hcd 0000:00:1a.1: wake-up capability disabled by ACPI Jul 16 11:46:52 Tower kernel: uhci_hcd 0000:00:1a.2: wake-up capability disabled by ACPI Jul 16 11:46:52 Tower kernel: ehci_hcd 0000:00:1a.7: wake-up capability disabled by ACPI Jul 16 11:46:52 Tower kernel: uhci_hcd 0000:00:1d.0: wake-up capability disabled by ACPI Jul 16 11:46:52 Tower kernel: uhci_hcd 0000:00:1d.1: wake-up capability disabled by ACPI Jul 16 11:46:52 Tower kernel: uhci_hcd 0000:00:1d.2: wake-up capability disabled by ACPI Jul 16 11:46:52 Tower kernel: ehci_hcd 0000:00:1d.7: wake-up capability disabled by ACPI Jul 16 11:46:52 Tower kernel: PM: noirq resume of devices complete after 1.100 msecs Jul 16 11:46:52 Tower kernel: PM: early resume of devices complete after 0.063 msecs Jul 16 11:46:52 Tower kernel: uhci_hcd 0000:00:1a.0: setting latency timer to 64 Jul 16 11:46:52 Tower kernel: usb usb3: root hub lost power or was reset Jul 16 11:46:52 Tower kernel: uhci_hcd 0000:00:1a.1: setting latency timer to 64 Jul 16 11:46:52 Tower kernel: usb usb4: root hub lost power or was reset Jul 16 11:46:52 Tower kernel: uhci_hcd 0000:00:1a.2: setting latency timer to 64 Jul 16 11:46:52 Tower kernel: usb usb5: root hub lost power or was reset Jul 16 11:46:52 Tower kernel: ehci_hcd 0000:00:1a.7: setting latency timer to 64 Jul 16 11:46:52 Tower kernel: uhci_hcd 0000:00:1d.0: setting latency timer to 64 Jul 16 11:46:52 Tower kernel: uhci_hcd 0000:00:1d.1: setting latency timer to 64 Jul 16 11:46:52 Tower kernel: uhci_hcd 0000:00:1d.2: setting latency timer to 64 Jul 16 11:46:52 Tower kernel: usb usb6: root hub lost power or was reset Jul 16 11:46:52 Tower kernel: usb usb7: root hub lost power or was reset Jul 16 11:46:52 Tower kernel: pci 0000:00:1e.0: setting latency timer to 64 Jul 16 11:46:52 Tower kernel: usb usb8: root hub lost power or was reset Jul 16 11:46:52 Tower kernel: ehci_hcd 0000:00:1d.7: setting latency timer to 64 Jul 16 11:46:52 Tower kernel: ahci 0000:00:1f.2: setting latency timer to 64 Jul 16 11:46:52 Tower kernel: pcieport 0000:00:1c.4: wake-up capability disabled by ACPI Jul 16 11:46:52 Tower kernel: e1000e 0000:02:00.0: Disabling ASPM L0s L1 Jul 16 11:46:52 Tower kernel: pcieport 0000:00:1c.5: wake-up capability disabled by ACPI Jul 16 11:46:52 Tower kernel: e1000e 0000:03:00.0: Disabling ASPM L0s L1 Jul 16 11:46:52 Tower kernel: e1000e 0000:02:00.0: irq 44 for MSI/MSI-X Jul 16 11:46:52 Tower kernel: e1000e 0000:03:00.0: irq 45 for MSI/MSI-X Jul 16 11:46:52 Tower kernel: e1000e 0000:02:00.0: irq 46 for MSI/MSI-X Jul 16 11:46:52 Tower kernel: e1000e 0000:03:00.0: irq 47 for MSI/MSI-X Jul 16 11:46:52 Tower kernel: e1000e 0000:02:00.0: irq 48 for MSI/MSI-X Jul 16 11:46:52 Tower kernel: e1000e 0000:03:00.0: irq 49 for MSI/MSI-X Jul 16 11:46:52 Tower kernel: e1000e 0000:02:00.0: eth0: MAC Wakeup cause - Magic Packet Jul 16 11:46:52 Tower kernel: serial 00:06: activated Jul 16 11:46:52 Tower kernel: usb 5-2: reset full-speed USB device number 2 using uhci_hcd Jul 16 11:46:52 Tower kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jul 16 11:46:52 Tower kernel: ata6.00: configured for UDMA/133 Jul 16 11:46:52 Tower kernel: sd 5:0:0:0: [sdg] Starting disk Jul 16 11:46:52 Tower kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Jul 16 11:46:52 Tower kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jul 16 11:46:52 Tower kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jul 16 11:46:52 Tower kernel: ata4.00: configured for UDMA/133 Jul 16 11:46:52 Tower kernel: sd 3:0:0:0: [sde] Starting disk Jul 16 11:46:52 Tower kernel: ata3.00: configured for UDMA/133 Jul 16 11:46:52 Tower kernel: sd 2:0:0:0: [sdd] Starting disk Jul 16 11:46:52 Tower kernel: ata1: link is slow to respond, please be patient (ready=0) Jul 16 11:46:52 Tower kernel: ata5: link is slow to respond, please be patient (ready=0) Jul 16 11:46:52 Tower kernel: ata2: link is slow to respond, please be patient (ready=0) Jul 16 11:46:52 Tower kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jul 16 11:46:52 Tower kernel: ata2.00: configured for UDMA/133 Jul 16 11:46:52 Tower kernel: sd 1:0:0:0: [sdb] Starting disk Jul 16 11:46:52 Tower kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jul 16 11:46:52 Tower kernel: ata5.00: configured for UDMA/133 Jul 16 11:46:52 Tower kernel: sd 4:0:0:0: [sdf] Starting disk Jul 16 11:46:52 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jul 16 11:46:52 Tower kernel: ata1.00: configured for UDMA/133 Jul 16 11:46:52 Tower kernel: sd 0:0:0:0: [sda] Starting disk Jul 16 11:46:52 Tower kernel: PM: resume of devices complete after 9193.838 msecs Jul 16 11:46:52 Tower kernel: Restarting tasks ... done. Jul 16 11:46:52 Tower kernel: mdcmd (45): spindown 0 Jul 16 11:46:53 Tower kernel: mdcmd (46): spindown 1 Jul 16 11:46:53 Tower kernel: mdcmd (47): spindown 2 Jul 16 11:46:54 Tower kernel: mdcmd (48): spindown 3 Jul 16 11:46:54 Tower kernel: mdcmd (49): spindown 4 Jul 16 11:47:18 Tower crond[1096]: time disparity of 231 minutes detected
July 16, 201312 yr Author The syslog doesn't contain any logging from the plugin. This is quite mysterious. Could you issue the following command in shell? logger -t test testmessage Does this show in syslog? I suspect it will. Propably the logging doesn't really get called on your system. I'll have to investigate and report back.
July 16, 201312 yr It did show up in the syslog: Jul 16 19:13:17 Tower test: testmessage[/Code] Sent from my SPH-D710 using Tapatalk 2
July 17, 201312 yr Author Looking at your syslog from when you started the plugin, I think I see the problem. The -D 1 parameter which defines the logging gets added without a space before it after the postRun script. This will propably cause it to be ignored and will also cause the postRun to fail. For me logging works, because I have no postRun defined. I'll try to fix it and post a new version in the next days. The error must have been present in the original plugin, too.
July 17, 201312 yr I think the post run is working. I've had to check that a few times in the past to make sure. I'll check again to confirm. Thanks for taking time to look at it.
July 18, 201312 yr Author I fixed the missing spaces and uploaded a new .txz package to my github account. The link from the first post stays the same. Could you download and try the fixed package? The .plg file wasn't modified and doesn't need to be replaced.
July 19, 201312 yr Author I commited a better fix for the problem, that the drives were detected as not spinning after boot. The problem was caused, because the disks.ini file I parsed to get the array drives was sometimes not yet present when the s3_sleep was executed. The script now waits until this file is created.
July 22, 201312 yr Author The "better" fix made me notice that my approach on determining array disks by reading the disks.ini file is a wrong one. The disk.ini seems to be created by emhttp on first access to the management page. So if the user doesn't access this, the file would never be created. Anybody out there who knows a better way to identify array disks devices (/dev/sda, ...) on unraid?
July 22, 201312 yr I'm guessing there are not to many followers of this thread. You might need to ask in the main support forum. I was camping all weekend and did not have a chance to try out the newer version yet. Should I wait until you find out the answer to your last question? Or would you like me to test out the new version anyhow for logging purposes?
July 23, 201312 yr Author @kricker The question was asked knowing very well, that I would propably have to find my own answer. I did and a new version is uploaded. Whats left now, is to rewrite the selection mechanism for excludes or includes other then all. The device names used are not fixed and it will give problems if they change. Sadly this is more complicated to do, than it sounds.
July 23, 201312 yr Author Yes. Sadly they might. The script will not start to ignore array drives, but it will stop to ignore a drive you set to be ignored if this drive gets a new device name.
July 24, 201312 yr I grabbed the new version and I am going to check to see if the logging works for me now. I'll let you know what happens.
July 24, 201312 yr Yeah! I got a log on the flash drive now! Wed Jul 24 12:35:22 EDT 2013: Devicelist: /dev/sda /dev/sdb /dev/sdd /dev/sde /dev/sdf /dev/sdg Wed Jul 24 12:35:22 EDT 2013: /dev/sdb drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 12:35:22 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 12:35:32 EDT 2013: Devicelist: /dev/sda /dev/sdb /dev/sdd /dev/sde /dev/sdf /dev/sdg Wed Jul 24 12:35:32 EDT 2013: /dev/sdb drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 12:35:32 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 12:35:47 EDT 2013: Devicelist: /dev/sda /dev/sdb /dev/sdd /dev/sde /dev/sdf /dev/sdg Wed Jul 24 12:35:47 EDT 2013: /dev/sdb drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 12:35:47 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 12:36:12 EDT 2013: Devicelist: /dev/sda /dev/sdb /dev/sdd /dev/sde /dev/sdf /dev/sdg Wed Jul 24 12:36:12 EDT 2013: /dev/sdb drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 12:36:12 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 12:37:14 EDT 2013: /dev/sdb drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 12:37:14 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 12:38:14 EDT 2013: /dev/sdb drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 12:38:14 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 12:39:14 EDT 2013: /dev/sdb drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 12:39:14 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 12:40:14 EDT 2013: /dev/sdb drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 12:40:14 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 12:41:14 EDT 2013: /dev/sdb drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 12:41:14 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 12:42:14 EDT 2013: /dev/sdb drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 12:42:14 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 12:43:14 EDT 2013: /dev/sdb drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 12:43:14 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 12:44:14 EDT 2013: /dev/sdb drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 12:44:14 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 12:45:14 EDT 2013: /dev/sdb drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 12:45:14 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 12:46:14 EDT 2013: /dev/sdb drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 12:46:14 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 12:47:14 EDT 2013: /dev/sdb drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 12:47:14 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 12:48:14 EDT 2013: /dev/sdb drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 12:48:14 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 12:49:15 EDT 2013: /dev/sdb drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 12:49:15 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 12:50:15 EDT 2013: /dev/sdb drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 12:50:15 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 12:51:15 EDT 2013: /dev/sdb drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 12:51:15 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 12:52:15 EDT 2013: /dev/sdb drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 12:52:15 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 12:53:15 EDT 2013: /dev/sda drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 12:53:15 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 12:54:15 EDT 2013: /dev/sda drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 12:54:15 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 12:55:15 EDT 2013: /dev/sda drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 12:55:15 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 12:56:15 EDT 2013: /dev/sda drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 12:56:15 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 12:57:15 EDT 2013: /dev/sda drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 12:57:15 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 12:58:16 EDT 2013: /dev/sda drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 12:58:16 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 12:59:16 EDT 2013: /dev/sda drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 12:59:16 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 13:00:16 EDT 2013: /dev/sda drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 13:00:16 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 13:01:16 EDT 2013: /dev/sda drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 13:01:16 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 13:02:16 EDT 2013: /dev/sda drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 13:02:16 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 13:03:16 EDT 2013: /dev/sda drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 13:03:16 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 13:04:17 EDT 2013: /dev/sda drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 13:04:17 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 13:05:17 EDT 2013: /dev/sda drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 13:05:17 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 13:06:17 EDT 2013: /dev/sda drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 13:06:17 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 13:07:17 EDT 2013: /dev/sda drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 13:07:17 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 13:08:17 EDT 2013: /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 13:08:17 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 13:09:17 EDT 2013: /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 13:09:17 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 13:10:17 EDT 2013: /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 13:10:17 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 13:11:17 EDT 2013: /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 13:11:17 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 13:12:17 EDT 2013: /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 13:12:17 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 13:13:18 EDT 2013: /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 13:13:18 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 13:14:18 EDT 2013: /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 13:14:18 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 13:15:18 EDT 2013: /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 13:15:18 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 13:16:18 EDT 2013: /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 13:16:18 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 13:17:18 EDT 2013: /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 13:17:18 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 13:18:18 EDT 2013: /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 13:18:18 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 13:19:18 EDT 2013: /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 13:19:18 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 13:20:18 EDT 2013: /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 13:20:18 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 13:21:19 EDT 2013: /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle Wed Jul 24 13:21:19 EDT 2013: Disk activity detected. Reset all counters Wed Jul 24 13:22:22 EDT 2013: /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle ... I haven't taken the time to review it yet, but at least now I have a log! Thank you.
July 26, 201312 yr Well, now it appears my server will not sleep. The cache drive is preventing standby even though I have it set to ignore the cache drive. Fri Jul 26 11:16:24 EDT 2013: /dev/sdg drive state is: active/idle Fri Jul 26 11:16:24 EDT 2013: Disk activity detected. Reset all counters That was the last bit of the log. Sdg is my Cache drive. Cache ST380811AS_3PS0EGGC (sdg)
Archived
This topic is now archived and is closed to further replies.