drcos

Members
  • Posts

    30
  • Joined

  • Last visited

Everything posted by drcos

  1. Sleep plugin issue (ignoring array disks) persists in Unraid 6.9.1. Costanza solution still working.
  2. I will try that and if it works we will call it the Costanza solution. -EDIT- The Costanza solution works.
  3. UPDATE - Fixed 3/13 in plugin update. Thanks! s3 sleep is broken in Unraid 6.9.0. Snippet from log - - - - - - - - - - - - Mar 2 16:04:49 htserv s3_sleep: version=3.0.7 Mar 2 16:04:49 htserv s3_sleep: ---------------------------------------------- Mar 2 16:04:49 htserv s3_sleep: included disks= Mar 2 16:04:49 htserv s3_sleep: excluded disks=sda sdb sdc sdd sde sdf sdg sdh sdi sdj sdk sdl Mar 2 16:04:49 htserv s3_sleep: ---------------------------------------------- Mar 2 16:04:49 htserv s3_sleep: s3_sleep process ID 30890 started, To terminate it, type: s3_sleep -q - - - - - - - - Wait for array is set to Yes, exclude cache - cache is sdi. Array goes to sleep after timeout even though disks are in use. Plugin worked in 6.8.3. Any thoughts?
  4. Zonediver's fix works for me on 6.8.3 now (at least the first try) . . .
  5. Same problem for me with 6.8.2. Now probably need to downoad 6.7.2. Any other suggestions?
  6. Had to set sleep plugin to 'Disable' during a preclear. Is this normal? The sleep plugin was set to monitor the specific disk outside the array which was being precleared. When I caught that the device had gone to sleep (twice), waking it up resumed the preclear. Not a problem, just an annoyance.
  7. How do you check this? With the system sleeping, neither LED on the ethernet port is on.
  8. Same problem with 6.7 (no WOL) and ethtool eth0 says pumbg for 'Supports wake-on' and g for Wake-on. Pushing the power button did wake up the system.
  9. Array activity seems to be fixed with 6.4.1 (works for me)
  10. Thanks SSD, never thought to do the HOSTS thing. Also, changed out a bad controller card, and have to rebuild parity again...
  11. I had a controller card flake out on me, and thought I lost my array (mini heart attack). Fortunately, I realized it was three drives (parity, cache, and one array drive) on the card. (Slight) problem once I got things fixed, my parity was disabled and I had to rebuild parity even though I had not changed anything in the array from before the problem. What I did: 1. PANIC (array wouldn't start, missing parity and cache drive (not assigned) and drive 7 (showed ID) 2. Determine problem, fix problem, reboot. 3. Array starts with parity disabled (red X on parity drive) 4. Stop array, restart...parity disabled. 5. Reboot. Array starts...parity disabled. 6. Stop array. Unassign parity. Re-assign parity (no option for 'parity is valid'). Restart array, parity rebuild. Not a huge issue, as rebuilding parity took about an hour longer than checking parity. One remaining issue, Windows no longer sees the unRaid by name on the network. Can still access by IP. (edit - this seems to be a Windows issue, don't know why it started suddenly)
  12. What I use is a Pi, running Minimserver to listen to music across my home network. Working on automatically syncing between it and my unRaid.
  13. Same problem with Sleep plugin. From syslog: Jan 21 08:23:39 htserv s3_sleep: ---------------------------------------------- Jan 21 08:23:39 htserv s3_sleep: included disks=sdh sdj Jan 21 08:23:39 htserv s3_sleep: excluded disks=sda sdb sdc sdd sde sdf sdg sdi sdk sdl The plugin is excluding discs that should be included ...
  14. Thanks, I did search in the forum but did not find it ..? I'll go back to my old sleep script. (edit - which works well in 6.4) **mods please delete this redundant thread thx** Especially now that it's fixed and appears to be working in UR 6.4.1
  15. Not working properly in 6.4...as apparent in syslog Jan 21 08:23:39 htserv s3_sleep: ---------------------------------------------- Jan 21 08:23:39 htserv s3_sleep: included disks=sdh sdj Jan 21 08:23:39 htserv s3_sleep: excluded disks=sda sdb sdc sdd sde sdf sdg sdi sdk sdl Haven't changed settings since update to 6.4 ... ? Plugin version is 2017.05.12a
  16. Thanks, I must have installed Simple Features a while ago and forgot about it. I'll play with it this evening and be sure.
  17. No, the unMenu screen still shows that. I'm talking about the 'Main' screen (xx.xx.xx.xx/Main), the default page when I type in the server IP. I used to have Device, Identification, Temp, Size, Used, Free, Reads, Writes, Errors, View and a line for Total Array of seven protected disks (between the Cache line and Flash line). Now 'Used' is gone, View is gone (the folder icon is next to the Device), and the Total... line is gone. I have printed screenshots from previous updates (5.0-rc10 in my hand) with the Used column and Total line. I just don't know what happened between then and now. My server has been pretty much static except for adding media files and updating unRaid...
  18. No, I am confused. Up until rc16b my Main screen had the 'Used' column between Size and Free, and the 'Total' line between my cache drive and my flash drive. All I did was update the three files on the flash drive and restart, and now the Used column and the Total line are gone. Any ideas on how to get them back?
  19. Seem to be missing 'Used' column and 'Total' row in Device Status on the .../Main GUI screen in 5.0-rc16c (it was missing in 16b also) Haven't changed anything except my bzimage, bzroot, syslinux.cfg files on the stick.
  20. 'New config' worked. Tested the 'sleep' command found in other threads, it seems to work also, which is important for how I use my unRaid (video/music/file server). Tentatively solved, I am running Utils/New Permissions which I hope will fix my inability to access some of my shares. Once that is done, we are good. [Edit] New permissions (and a Windoze reboot) took care of the problems.
  21. The pic shows the 5 drives assigned after I manually assigned them, per the previous list I saved. To me, it looked like 5.0 did not see the drives the same as 4.7, but I was lost at that point and did not want to risk losing my array. I have attached the 4.7 files super.dat and disk.cfg. If I delete them and 'start new' as you suggest, do I risk losing my data, or will unRaid see the data already there? I think that the worst case would be it would have to rebuild the parity disk, yes? If I get a chance to re-try later today, I will. I have a backup of the entire flash drive for 4.7, if I try and fail again, I will be sure to copy the failed 5.0rc4 files for examination. disk.cfg super_dat.zip
  22. Followed upgrade instructions on main rc4 download page. Started with 5.0-rc4, no drives assigned. Manually assigned drives correctly (see attached), but too many 'wrong' drives. Did not change hardware, anything. Removed all customizations from go before starting. Re-checked and rebooted, same results as screenshot. Didn't know what to do, so back to 4.7 (there is a lot of data on my unraid I do not want to lose). Any thoughts? I see this thread (http://lime-technology.com/forum/index.php?topic=15385.15) but that would preclude me from going backwards, yes? (Sorry for the lack of syslog.txt, I had already reverted to get my array back online)
  23. If you are doing this via telnet, install 'screen' from unMenu first. Then telnet into your server and run screen. Screen lets you use your FKeys and such in the telnet window. Then use Midnight Commander (mc). In the left window, go to mnt, then disk1. Hit TAB to go to the right window. There go to mnt, then disk2. TAB back to the left window, select the files to copy and hit F6. You can keep the date/time info when copying. There are more excellent how-to's using MC (http://lime-technology.com/wiki/index.php?title=Transferring_Files_Within_the_unRAID_Server), but this is what I've been doing. It reminds me of XTree pro (showing my age). Remember if you telnet in and use screen, you have to 'exit' twice to log off. If not using telnet (right on the server), just use MC.
  24. OK never mind, fixed me own problem. Went back to 4.7 Using echo 3 > /proc/acpi/sleep, works (from http://lime-technology.com/wiki/index.php?title=Setup_Sleep_%28S3%29_and_Wake_on_Lan_%28WOL%29) So a beta bug. Another note for the fine beta folks... not only did the sleep scripts not work with anything after the actual command, the actual commands would only work ONCE. The second time I would try to sleep the system, it would stop and freeze (fan/power lite, no response to WOL, no response to keyboard etc). This happened with s2ram, pm-suspend, echo -n mem >/sys/power/state For the record, it's a Gigabyte GA-MA785M-US2H mobo