Community Developer
  • Posts

  • Joined

  • Last visited

  • Days Won


Community Answers

  1. Squid's post in libvirtd is missing was marked as the answer   
    It's something with the script that he's got running to set stuff up.  No idea.  Post in the support thread.
  2. Squid's post in Extremely Slow Read/Writes with SSDs was marked as the answer   
    sdd (disk 1) seems to have connection problems and is suffering from device resets slowing everything down.  Reseat the cabling
  3. Squid's post in Folder permissions issue was marked as the answer   
    Look in your download client for an option to set permissions (advanced view?)  Then change it to 0777
  4. Squid's post in Logs are filling up! New to UNraid and looking for assistance. was marked as the answer   
    Can't see where it all started, but a ton of write errors to the cache pool.  But, the one drive (...3042) isn't showing as being online in the SMART reports, so you might want to check cabling etc (or maybe it just died). 
    @JorgeB will be able to assist in any recovery operation
  5. Squid's post in unable to see GUI, nor shares, but VM started fine was marked as the answer   
    Does your VM's attached monitor (you're obviously doing a GPU passthrough) normally display the bootup sequence from the BIOS of the server itself?
    Since you had to go into the BIOS to set the date and time, it implies your battery (probably a CR2032) is shot and the primary GPU you're using for the server (I'm assuming you have 2 -> one for passthrough, and the other (iGPU / cheapie card) is used for Unraid.  You've got to set the primary video card to be iGPU / el cheapie.  Then we'll be able to make some more progress
  6. Squid's post in Ran out of memory and processes (potentiallyP have stopped. was marked as the answer   
    My first thought when I did the text was "FIRE FIRE FIRE BEES!", but decided to settle on what is there now.
    Surprisingly, the webGUI itself (and the underlying emhttp) required memory, none was available so Linux killed off some Plex on Jan 3 (which was based upon what it needed / was last used was the best candidate).  Looks like you possibly noticed that and restarted the array since
    Currently, nothing is any unusual amount of memory so its possible that on 1/3 something was just going nuts (without really diving into every file) with download / transcoding to RAM, etc etc.  
    Suffice it to say that the system operated as intended and killed off what was required for it to stay running as the linux programmers designed.  It doesn't appear to be a common issue for you, so you're probably going to be safe from the bees (or anaphylactic shock)
  7. Squid's post in Two parity drives, same size, different manufactures. Anything to be concerned about? was marked as the answer   
    Unlike "typical" RAID solutions, Unraid does not work any better (or worse) with matching sets of drives, so nothing to worry about 
  8. Squid's post in Constant Disabled disks was marked as the answer   
    Quick google search said to avoid the card if possible, but what @itimpi was referring to was the internal power connections coming from the powersupply.  All too often people don't consider that every molex splitter is 
    Another point of failure terrible quality to begin with, regardless if you paid $1 or $20 for them And also quite often do not consider the power draw on individual rails coming from the power supply vs the amount of components plugged into them
    Another possibility depending upon how you're connecting the drives is the SATA connected to the drives.  Reseat.
    Not saying that any of this is your particular problem.
  9. Squid's post in New Install No Drives Showing was marked as the answer   
    01:00.0 RAID bus controller [0104]: Broadcom / LSI MegaRAID SAS 2008 [Falcon] [1000:0073] (rev 03) Subsystem: Dell PERC H310 [1028:1f78] Kernel modules: megaraid_sas You've got the controller set up in IR mode.  You still have to tell the controller in IT's bios (CTRL-S IIRC) to either switch to JBOD or create 4x RAID pools composed of a single drive each.
    Since it's a Perc H310, you'll actually have by far the best results on Unraid (or any NAS) for that matter by cross flashing it to be the generic LSI HBA
    Lots of information on that in the internet (just search H310 crossflash to IT), and a rather long thread here https://forums.unraid.net/topic/12114-lsi-controller-fw-updates-irit-modes/
  10. Squid's post in Parity check running very slow (kb/s) was marked as the answer   
    You've got to reseat the cabling to both ST10000VN0004-1ZD101  ZA29CF7E (disk 10),  and ST10000VN0004-1ZD101   ZA2AJ2XJ (disk 11)
    Sata is finicky at times and it doesn't take much for continual resets to happen on a slightly misaligned cable (or a bad cable)
  11. Squid's post in [Help] Can't boot unraid suddenly was marked as the answer   
    Restore the USB from a backup (or manually download the OS version and save all of the bz* files in the zip to the flash drive).  Worse case scenario you would have to set up a new boot device
  12. Squid's post in [Solved] System logs not displaying through web GUI was marked as the answer   
    Actually, that display is correct at the time the diagnostics were taken.  The syslog has a total size of 0 bytes.  Have you by chance deleted /var/log/syslog (or doing anything with it)
  13. Squid's post in Web Interface dosent load anymore was marked as the answer   
    Jan 16 07:52:26 Potti root: nginx: [emerg] cannot load certificate "/etc/ssl/certs/unraid_bundle.pem": PEM_read_bio_X509_AUX() failed (SSL: error:0909006C:PEM routines:get_name:no start line:Expecting: TRUSTED CERTIFICATE)  
     I suspect that this is the root of your problems.
    Delete the contents of /config/ssh and /config/ssl on the flash drive and reboot
    This could be flash drive corruption, as the system isn't reading the key file correctly (or at all), but that shouldn't affect being able to hit the UI
  14. Squid's post in Should a parity check significantly affect system performance while running? was marked as the answer   
    Most people use the Parity Check Tuning plugin so that the scheduled checks run in batches during off hours (ie: mine run between midnight (when I go to sleep) and 4 am (when the wife gets up) and resumes the next day until its completed).  But, yes since there's competing bandwidth depending upon how much bandwidth is required by the media, pauses etc may result
  15. Squid's post in Lost Dockers/VM on reboot+adding new disk was marked as the answer   
    Stop the VM service and docker service in Settings (VM Settings and Docker Settings).  Then
    mv /mnt/cache/system/libvirt.img /mnt/cache/system/libvirt.img.new mv /mnt/cache/system/docker.img /mnt/cache/system/docker.img.new Restart the VM service
    Do the VMs show back up again?  If it does (and it should in theory), then 
    rm /mnt/cache/system/libvirt.img.new rm /mnt/cache/system/docker.img.new  
    Followed by stopping the each of the services again.  Then change the system share's settings to use Cache: prefer, then Main, run Mover.  After its done, restart each of the services.
    Other comments.  The usual setting for use Cache on the appdata share is prefer, for far better performance (and make a backup via the appdata backup plugin)
  16. Squid's post in Machine Check Events related to CPU was marked as the answer   
    MCE was issued during processor initialization and affects some combinations of hardware and is safe to ignore
  17. Squid's post in Swapped 2080 for 6900XT and now can't access GUI was marked as the answer   
    There's no link being detected on any of your NICs.  You sure the cable is plugged in? (Both ends).  Any lights on the NIC or the switch?
  18. Squid's post in LOG flushing with emhttpd: *** bug: 5246 /mnet/userappdata cache was marked as the answer   
    Jan 11 21:22:21 NAS kernel: BTRFS: error (device sdk1) in cleanup_transaction:1942: errno=-28 No space left Jan 11 21:22:21 NAS kernel: BTRFS info (device sdk1): forced readonly  
    But, the more interesting thing is that you don't actually have a cache pool named "cache" Rather you have a cache pool named cache_1tb_ssd, but was probably a semi-recent change / addition, but at the time of doing that, you left your various shares all referencing "cache" in the select cache pool option.
    And the share exists on "cache" and on various disks, but since there is no pool named cache, the files all wind up in RAM.  (Also you'll have to manually adjust the various docker templates you've got (show more settings), and see if anything there is directly referencing /mnt/cache/...
    After you've got all that fixed up, then reboot, and we'll take it from there (with a new set of diagnostics)
  19. Squid's post in Issues with updating Dockers - Image can not be deleted, in use by other container(s) was marked as the answer   
    OTOH, revert the changes you made that were in some thread that put the logs to RAM
    Jan 7 14:30:01 KingServer docker: RAM-Disk synced and if that solves it ask about it in the relevant thread.
  20. Squid's post in Restore my key was marked as the answer   
    Probably best to include more detail and talk to @SpencerJ or email Limetech https://unraid.net/contact
  21. Squid's post in (SOLVED) Fix Common Problems: Machine Check Events reported, asking for help was marked as the answer   
    Yup.  Same non-issue
  22. Squid's post in Is parity maintained when moving files from one disk to another within the array? was marked as the answer   
    Yes in real time.
  23. Squid's post in Can't ssh into server on 6.10rc2 was marked as the answer   
    Is SSH Enabled in Management Settings?
  24. Squid's post in Normal transfer speeds? was marked as the answer   
    Connect the 2.5G switch to the router (or the switch following it if you have one)
    Everything connected to the 2.5G switch will communicate with each other at 2.5 regardless of what the speed of the router / switch it's connected to is.
  25. Squid's post in Error message on boot - How to debug to fix it was marked as the answer   
    It looks like the network stats plugin automatically tries to download the package on every boot, instead of saving it to the flash drive.  In your case, the network isn't completely up at that time and it fails.
    Ignore the error (it's harmless), Uninstall and reinstall network stats.  And post in the support thread