Hoopster

Members
  • Posts

    3769
  • Joined

  • Last visited

  • Days Won

    19

Everything posted by Hoopster

  1. @DigDug5002 The information above from @G Speed should be taken into consideration. I have never used a Dell server for unRAID but the H310 works fine with my non-Dell hardware. If G Speed has problems with the H310, perhaps one of his other suggestions is a better choice.
  2. Yes. That is exactly what I, and many others, use with UnRAID. Sent from my iPhone using Tapatalk
  3. RAID controllers are not recommended with unRAID. As the name suggests, RAID is not supported on array data drives. This thread is a discussion of disk controllers that are recommended for use with unRAID.
  4. Does not meet your GUI requirement as this runs via script, but once you set it up it is set it an forget it. I have been backing up one unraid server to another this way for about three years now. It is all automated via a User Scripts cron job. Also check out this option with LuckyBackup which is a combination of CLI and GUI: https://unraid.net/blog/unraid-server-backups-with-luckybackup
  5. Problem resolved. Something happened during the last appdata backup that resulted in it filling the disk (size was reported incorrectly). Previous backups were much smaller. I have moved appdata backup to a different location with lots of space for troubleshooting and removed it from the SYSLOG location. Syslog is functioning properly now and again writing to the syslog on the Micro SD card. The "no space left on device" errors have ceased.
  6. My syslog is written to a flash drive configured as an unassigned device. For some reason it says all space is used when it has very little actually stored on the card. This is a Micro SD card without a lock switch. Since the upgrade to 6.10.0 there have been lots of issues with the syslog. Currently, the syslog in RAM is filling up with the following errors: May 25 04:50:01 MediaNAS rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="26279" x-info="https://www.rsyslog.com"] rsyslogd was HUPed May 25 04:50:01 MediaNAS rsyslogd: rsyslogd[internal_messages]: 552 messages lost due to rate-limiting (500 allowed within 5 seconds) May 25 04:50:01 MediaNAS rsyslogd: file '/mnt/disks/SYSLOG/syslog-192.168.1.10.log'[9] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] May 25 04:50:01 MediaNAS rsyslogd: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] May 25 04:50:01 MediaNAS rsyslogd: file '/mnt/disks/SYSLOG/syslog-192.168.1.10.log'[9] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] May 25 04:50:01 MediaNAS rsyslogd: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] May 25 04:50:01 MediaNAS rsyslogd: file '/mnt/disks/SYSLOG/syslog-192.168.1.10.log'[9] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] May 25 04:50:01 MediaNAS rsyslogd: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] May 25 04:50:01 MediaNAS rsyslogd: file '/mnt/disks/SYSLOG/syslog-192.168.1.10.log'[9] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] May 25 04:50:01 MediaNAS rsyslogd: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] May 25 04:50:01 MediaNAS rsyslogd: file '/mnt/disks/SYSLOG/syslog-192.168.1.10.log'[9] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] May 25 04:50:01 MediaNAS rsyslogd: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] May 25 04:50:01 MediaNAS rsyslogd: file '/mnt/disks/SYSLOG/syslog-192.168.1.10.log'[9] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] May 25 04:50:01 MediaNAS rsyslogd: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] May 25 04:50:01 MediaNAS rsyslogd: file '/mnt/disks/SYSLOG/syslog-192.168.1.10.log'[9] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] May 25 04:50:01 MediaNAS rsyslogd: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] May 25 04:50:01 MediaNAS rsyslogd: file '/mnt/disks/SYSLOG/syslog-192.168.1.10.log'[9] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] May 25 04:50:01 MediaNAS rsyslogd: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] May 25 04:50:01 MediaNAS rsyslogd: file '/mnt/disks/SYSLOG/syslog-192.168.1.10.log'[9] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] May 25 04:50:01 MediaNAS rsyslogd: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] May 25 04:50:01 MediaNAS rsyslogd: file '/mnt/disks/SYSLOG/syslog-192.168.1.10.log'[9] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] May 25 04:50:01 MediaNAS rsyslogd: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] May 25 04:50:01 MediaNAS rsyslogd: file '/mnt/disks/SYSLOG/syslog-192.168.1.10.log'[9] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] May 25 04:50:01 MediaNAS rsyslogd: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] May 25 04:50:01 MediaNAS rsyslogd: file '/mnt/disks/SYSLOG/syslog-192.168.1.10.log'[9] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] May 25 04:50:01 MediaNAS rsyslogd: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] May 25 04:50:01 MediaNAS rsyslogd: file '/mnt/disks/SYSLOG/syslog-192.168.1.10.log'[9] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] May 25 04:50:01 MediaNAS rsyslogd: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] The flash drive for the syslog is definitely not out of space (it's 32GB) but rsyslogd is not writing anything to the syslog file on the flash drive. I even reformatted the flash drive. Immediately after this, the syslog file was written but it stopped after a few lines and has not been updated in a couple of days. My appdata backup also goes to the same flash UD flash drive and there are no issues with that process. [UPDATE: apparently this was the problem as the last appdata backup went crazy and filled the disk] While running unRAID 6.9.2 the syslog on the flash drive was written to without issue from Jan to May 24 when it suddenly stopped after the 6.10.0 upgrade. [It was the first appdata backup that happened shortly after upgrading that caused the problem so I though it was the upgrade that was the issue.] What could be causing rsyslogd to think the drive is full when it is not and failing to write to the syslog? Permissions look OK? medianas-diagnostics-20220527-0852.zip
  7. I just made the jump from controller version 5.14.23 all the way to 7.1.66 in one step. The upgrade went smoothly and everything came back online. This shows it is possible to skip the 6.x.x versions altogether and go straight to 7.x.x if you, like I was, are still running 5.14.23, It will take me a while to figure out where everything is now as things are organized differently. There was no compelling reason to do the upgrade other than fear of being left too far behind and making a future upgrade more difficult.
  8. You never met my wife. 😀 Other than that small point, the rest of your post is spot on. I am a firm believer that fewer larger drives is better than many smaller drives. I have consolidated twice. First it was 3TB to 8TB drives and now I am starting to move from 8TB to 14TB and 16TB drives.
  9. Not that I know of. The latest firmware that does support the iGPU is L2.35. Look toward the end of the linked thread for one of my posts in which I included the L2.35 BIOS.
  10. Yes, I should have caught that. The configuration of the disk was incorrect in UD after the upgrade. After mounting it manually, I did in fact unplug it without unmounting and removing from historical devices. A reboot of the server cleared everything up and it is working properly now. I was so used to just unplugging it after the backup and automatic unmount that I forgot to manually unmount. Thanks for pointing out the obvious as I missed that. 😀
  11. Since upgrading to unRAID 6.10.0 and the latest version of the UD plugin, my external backup drive (14TB Easystore NTFS) will not mount and run the backup script. I deleted it from historical devices, plugged it in and configured it again. No change. Worked great in unRAID 6.9.2 and prior to updating UD. If I plug it in to a WIndows PC, everything appears as it should. medianas-diagnostics-20220518-2003.zip
  12. The high MB temps and crashing with CPU_CATTERR is back with the 6.10.0 unRAID release. Shortly after upgrading to 6.10.0, the MB temp reading soared, the CPU temp hit sustained 70C+ temps and the system locked up with a CPU_CATTER. With 6.9.2 I have been stable for over four months with Turbo Boost enabled. After restarting the server, I disabled Turbo Boost and it has been running well for 14 hours. The MB temp is reporting 83C which I had not seen in many months with 6.9.2. There must be some Linux kernel issues related to all this. For now, I will stay on 6.10.0 with Turbo Boost disabled and see what happens long term. [UPDATE 5/24] Been running 6.10.0 with Turbo Boost disabled for 6 days now with no errors/lockups and normal MB temps in the 20/30s C.
  13. Yes, I am running an older version of the controller. I am glad you found the equivalent setting in the latest version and that it appears to have helped resolve your issue.
  14. As mentioned several times in this and other forums, the adoption loop issue can often be resolved by enabling the "Override inform host with controller hostname/IP" setting in Controller settings. Give that a try and see if it helps. Basically, this is a permanent "set-inform http://UNRAIDIP:8080/inform" command
  15. The combination of the unRAID UI/Docker/Plugin system, built-in WireGuard (or the MyServers plugin) and IPMI on my server motherboards makes remote management of the server and its contents ridiculously easy. One of my unRAID servers is powered on 24x7 and the other is off until needed; powered on via User Scripts for specific purposes or via IPMI manually when I need to do something with it. I have been away from home for 12 days now and have accessed media on the server and done a few maintenance tasks several times now remotely, including powering on the "off" server and updating it to 6.10.0 rc8 It is so easy that it would be easy to forget I am not home. Of course, there are ways other than IPMI to remotely power on a server, but IPMI sure makes it easy via an HTML 5 web interface. I was doing some remote management from my laptop when a friend asked what I was doing. When I explained it and showed him how I was accessing my home servers, he was dumbfounded. He considered himself technically literate but was astounded how easy this all is. Hopefully, I sold him on unRAID as well.
  16. I just changed the battery in my APC UPS last month. UnRAID APC daemon was warning me it was bad and I was able to change it with no issues and no APC software required. Sent from my iPhone using Tapatalk
  17. Setup the syslog server so the logs are persistent. Otherwise they are lost on reboot as they are only in RAM.
  18. Yes, they were referring to the software. You don't need any APC software for unRAID. Just configure it as desired in Settings --> UPS Settings.
  19. That would certainly get it blacklisted.
  20. When you registered your USB flash drive, it was the first to be registered with that GUID. Your USB flash apparently does not have a unique GUID and now someone else has attempted to register a USB flash drive for unRAID with the same GIUID. That is what gets it blacklisted. Each new release of unRAID has a new list of blacklisted GUIDs updated since the last release. You should make sure you get a USB flash drive with a unique GUID and transfer your license to that.
  21. Sorry, I misunderstood. Yes, the drives attached to my H310 spin down according to the unRAID spin down settings. I cannot comment on the ASM1166 card. That probably depends more on the motherboard slot. Of course, the Dell H310 will not fit in a PCIe x1 slot. In a physical x8 or x16 slot it will use the full 8 lanes unless the slot can have fewer lanes assigned. In a physical x4 slot, it will use 4 PCIe lanes unless fewer lanes can be assigned to the slot. The board you linked only has one PCIe slot in which the Dell H310 would fit. According to the board specs, even though it is a physical x16 slot, it appears it only supports 1 PCIe lane so that is all the Dell H310 could use. Personally, I have never heard of a Dell H310 that supports up to 8 drives being used with just one PCIe lane; however, it may be possible if not practical. At x1, I doubt you could use more than 2 drives with it without noticing throttled bandwidth.
  22. I assume you mean PCIe 3.0? The Dell H310 is a PCIe 2.0 card. I have one of these and it works great in IT mode with unRAID. PCIe 2.0 bandwidth at x8 is 4000 GB/s (really figure on ~3-3.2 after overhead or about 400 MB/s per PCIe lane). PCIe 2.0 bandwidth is more than enough for up to 8 HDDs which rarely get up to 200 MB/s. Some even use this card in a x4 slot. For SSDs, you could run into bandwidth issues; however, it is not recommended to attach SSDs to most HBAs anyway as they do not support TRIM. I have SSDs attached to motherboard SATA ports and HDDs to the Dell H310.
  23. Most APC and CyberPower UPS units work with unRAID natively. I am using the APC Back-Ups Pro 1000S (1000 VA/600 W). It works great and has gracefully shut down my unRAID server during a couple of power outages. Of course the VA/W rating you need in a UPS is dependent upon your unRAID server specs. I don't know what it might cost in the UK but I got mine for about US$140 a couple of years ago. The software is just for setup and monitoring on a Windows PC. It is not required for the unit to function in unRAID.
  24. And I am still running 5.14.23. The horrible experience most had with the early 6.x.x versions put me off upgrading since none of my current equipment requires a version beyond 5.14.23. I may finally take the plunge soon since I don't want to get left too far behind.