fnwc

Members
  • Posts

    57
  • Joined

  • Last visited

Everything posted by fnwc

  1. I have this same issue, and I also have "System wakeup disabled by ACPI" even though I have S3 sleep support. Sleeping the unRAID server works fine, but waking up results in an unresponsive server, with no SMB shares mounted, and even a keyboard plugged directly into the box still results in no signal to the monitor. I basically have to hard reset the server at this point. I'll try rolling back to RC 14... are there any issues I need to be aware of in downgrading?
  2. I've modified the script to only use 1 sed command. I agree, although I have no idea on how to adjust the log level for the syslogd. Can you point me in the right direction? I found some filtering capabilities in syslogs, although they seem to come from differing variants of syslog, such as rsyslog or syslog-ng. I couldn't find anything about filtering messages in the "vanilla" syslogd. I'm a little confused. I see a file "/var/log/syslog" that grows... am I not looking in the right place?
  3. Thanks, I just figured this out and it seems to work (although it triggers an email from the unraid-status-email plugin, strangely enough).
  4. As a followup, I did a "lsof /var/log" to figure out if there was an open file handle (after the script was run) and I got this: COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME syslogd 1195 root 1w REG 0,13 151090 4605 /var/log/syslog (deleted) I'm guessing that "sed -i" must delete the file and then copy back... and somehow this causes the syslog daemon to lose the handle on the syslog file?
  5. Bear with me, I'm a Windows user. Ok, I tried to write a script and have it run every 5 minutes. I created a file: "/boot/custom/parsesylog": */5 * * * * sed -i '/Received response from host .* with invalid source port .* on interface/d' /var/log/syslog */5 * * * * sed -i '/Invalid legacy unicast query packet/d' /var/log/syslog In "/boot/config/go": cat /boot/custom/parsesyslog >> /var/spool/cron/crontabs/root The idea is that I remove the two offending lines that are spamming my syslog every 5 minutes with this script. When I run the commands normally, i.e., sed -i '/Received response from host .* with invalid source port .* on interface/d' /var/log/syslog sed -i '/Invalid legacy unicast query packet/d' /var/log/syslog The syslog is pruned successfully. However, once the script runs via cron, something weird happens and the it seems only the first removal works --- all the "Invalid legacy unicast query packet" lines remain. I've attached both syslogs, one which is a minute after boot, BEFORE cron runs the "parsesyslog" script, and one 5 minutes later, AFTER cron runs the "parsesyslog" script. Furthermore, it seems that the syslog is then "locked"... nothing else seems to write to the syslog properly. You'll see in file "syslog-2013-10-06-BEFORE.txt" on line 1431 it shows that I telnet in from my machine. Once the script runs, the syslog no longer seems to capture the telnet (I tried repeatedly, and the syslog never appends anything else). Note: even when running the /sbin/powerdown script, this normally captures a ton of stuff in the syslog, but once looking at the archived log file in /boot/logs, it doesn't show anything. So something is getting messed up. Does linux have file handles like Windows? Perhaps sed is causing the file to be locked? Does anyone know what I might be doing wrong here? syslog-2013-10-06.zip
  6. Looking at my latest 4.7 log on 10/4/2013, I don't see any of these messages.
  7. I just upgraded from 4.7 today, using Tom's recommended guidelines on his announcement post. I had no issues with any of the drives, but I was looking at the syslog and noticed this: So, 192.168.1.123 is a netgear powerline adapter. It's not causing any issues, but I don't want the syslog to get gigantic from the constant warning message in the syslog, which might fill the flash drive eventually (which *will* cause problems). I'm not really sure what to do about this. Any ideas? Edit: It seems like I might be able to modify "etc/syslog.conf" to filter these messages (so they don't ever appear in the syslog), but I'm unsure of the syntax. syslog-2013-10-05_2.zip
  8. Ah thanks, didn't realize that you could use an internal indexer. Sweet.
  9. Keep in mind that a bunch of the indexers are going down like sinking ships... I'm waiting a few weeks and seeing what rises from the ashes, but in the meantime SickBeard is basically kaput.
  10. Hmmmmm do you think I could order this and get my license adjusted from LimeTech to fit the new GUID?
  11. It makes me sad that these are a good deal now.
  12. Hi, I recently tried to upgrade disk1 from 1.5 TB to 2.0 TB. I had recently performed a parity check (no errors), so I stopped the array, unassigned the drive, and powered down. Screenshot *before* the upgrade: I installed the new drive in the same bay as the old one (disk 1), and started the array (blue ball), rebuilding the drive based on the previous parity. Screenshot *after* the upgrade: However, at *some* point during the rebuilding process, the server froze. I wasn't able to access it remotely, and it didn't even have an IP assigned on the router. I went to the console and logged in, but I was immediately logged out. I hard reset the server, and it came back up, although the parity was rebuilding. Since I wasn't 100% sure that disk1 had finished rebuilding, I didn't trust the parity (it had already found a bunch of errors). I stopped the rebuild of the parity, unassigned the drive, and powered the server down. I reinstalled the *old* 1.5 TB drive in disk1 and started the server, and reassigned it to disk1. Now I have this: This is what I think I have: Incorrect parity Good data for all of my disks (including disk1) How do I restore drive1 with the existing data on it? I basically want to start the array and rebuild parity, trusting that all of the data on the disks is correct. Thanks for the help! syslog-2011-11-07.txt
  13. Yeah, "(" was working most of the time. But I found that if I added files to the directory below "Some Directory With a (" later, it would split the files onto multiple disks. Oh well. I've changed it to split level 2 and this currently seems to be working.
  14. Hi, I have the following directory setup on my unRaid 4.7 server: disk1/Movies/A/Aliens (1986) disk2/Movies/A/Almost Famous (2000) and I wanted to keep all the movie files together on the same disk (everything at the movie name folder level and below). I have set my split level to "(" and that seemed to work, most of the time. However, I've been noticing that sometimes -- usually after I've already moved the files over to the server and sometime later add another file (such as a trailer) -- that the files end up fragmented. In the above example, I copied a trailer for the Aliens movie and it ended up in disk2 for some reason, whereas I expected it should have been stored on disk1 (there was plenty of room on disk1). Should I just change my split level to 2?
  15. I've noticed some issues in the smart view of myMain: http://img820.imageshack.us/i/316201131117am.png/ /dev/sda: I've looked up "multi_zone_error_rate" but haven't had much success in determining what this exactly is. Should I be worried? Smart report: http://pastebin.com/embed_js.php?i=3Q3H8ZDK /dev/sdo looks farked. This drive was preclearing using the preclear script. Are these errors possibly a result of a bad cable/connection, or are the errors definitely a drive issue? Smart report: http://pastebin.com/embed_js.php?i=VwQi85jW /dev/sdl and /dev/sdm are Seagate ST32000542AS. Any reason why they show up as "zzz"? Thanks in advance for anyone who can clarify these issues for me.
  16. Cool, thanks. I actually use a label maker to put the serials on the back of the drive so I can see them when I have the case off. This makes it a lot easier when I'm trying to find a particular physical drive and match it to my array.
  17. Hi, I'm planning to move a bunch of my cables between my onboard SATA ports and my 2 SATA cards from the drives in my array (for better cable management). I assume that if I mark the exact position of each drive (in particular the parity drive) in my array and restore them to the correct positions, this will not be an issue? I thought this was in the wiki somewhere but I've been unable to find it. Thanks in advance.
  18. Not to derail the thread, but, what do you mean by 'fix'?
  19. Can you tell me the exact setting you changed for this, and under which menu item? Much appreciated.
  20. I tried both: ethtool -s eth0 speed 1000 ethtool -s eth0 speed 1000 full duplex and mi-tool -F 1000baseT-FD eth0: negotiated 100baseTx-FD flow-control, link ok Still reporting 100 Mb/s. I even enabled "Load ethernet BIOS" on my GIGABYTE GA-MA74GM-S2 740G R (don't worry, HPA is disabled), but that didn't seem to help (I'm using the onboard NIC). Anyone else have an idea?
  21. Hmm, I'm getting something like this: Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: off Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes Seems like I'm not using the full potential of my network card... does fixing this require changing a BIOS setting somewhere? I was reading another site that suggests I use something called mii-tool to change the speed and duplex settings.
  22. I hate to be a thread necromancer, but is the wdidle procedure safe to do on an active unRaid array?
  23. Hmmmmm... I don't have unzip installed, but I tried it in 7-zip (windows) and lo and behold, it's there. Turns out it was hidden, forgot to check the obvious (windows default zip handler doesn't show it unless you have 'show hidden files/folders' on). At any rate, I think I got it working... is it necessary to keep these lines in /boot/config/go, once they're installed, or can I remove them once I've rebooted once? installpkg /boot/socat-1.7.0.0-i486-2bj.tgz (if you will be using Secure SMTP) installpkg /boot/unraid_notify-2.30-noarch-unRAID.tgz
  24. When I unzip the attachment you linked, there is a .tgz file in there too. I see 4 files root@Atlas /tmp #unzip -v unraid_notify-2.3.0.zip Archive: unraid_notify-2.3.0.zip Length Method Size Ratio Date Time CRC-32 Name -------- ------ ------- ----- ---- ---- ------ ---- 8665 Stored 8665 0% 01-21-09 19:12 ff4b1866 unraid_notify-2.30-noarch-unRAID.tgz 18326 Defl:N 6942 62% 10-01-08 13:17 5b2bff86 LICENSE.txt 1306 Defl:N 588 55% 01-21-09 19:16 535afc8d README.txt 3198 Defl:N 1462 54% 10-01-08 12:42 b7914541 unraid_notify.cfg -------- ------- --- ------- 31495 17657 44% 4 files What the heck....I unzipped it in Win7, maybe that's why? Umm... I'll try to do it directly through putty.