Jump to content

trurl

Moderators
  • Posts

    44,363
  • Joined

  • Last visited

  • Days Won

    137

Everything posted by trurl

  1. Can you elaborate on this a bit? I have no problems creating or renaming files with Con. or con. anything on Unraid. What are you using to do the renaming?
  2. @Hoopster hope you don't mind my picking your brain a little more on this. I think you've talked me in to the E-2176G. Now I'm trying to decide between C246 WSI and E3C246D2I. I run headless so IPMI seems like a no brainer, except I have never used it. The WSI has more video output options but maybe I don't care if IPMI will do what I need. I would still use iGPU for plex transcoding. Currently when I need to troubleshoot something I can use the monitor for the desktop PC sitting beside my server, but it doesn't have VGA. I have a VGA monitor that still works but it is in storage. If I understand IPMI correctly, it will let me access the BIOS over the network. Is that a web interface or some other client application? Will IPMI also let me access the Unraid boot menu if I need to select SAFE mode boot for example? I already have Noctua NH-L9I. Do you think that will be sufficient? I am reusing my Lian Li PC-Q25 case but I might be able to squeeze something a little taller in there since I am also using SFX PSU.
  3. That will teach me to reply from my phone without my glasses on. Of course I meant If USB disconnects, which may happen more often than many realize in 24/7 operation, the disk will likely get disabled and so rebuilds will be a frequent occurrence. If you want an array with USB then don't use parity and accept that you have no redundancy.
  4. You don't. USB connections are to unreliable for the parity array.
  5. Docker image is actually unimportant. In fact, we often recommend people delete it and recreate it since everything in it will be downloaded again when you reinstall your dockers. And the Previous Apps feature on the Apps page will reinstall your dockers exactly as they were. Disable Docker Service in Settings - Docker, then delete the docker image. Do the same for Settings - VM Manager. While these are disabled, delete the system share from all disks except cache. Enable Docker Service will recreate docker image according to the settings, and since system share is cache-prefer, it will be created on cache where it belongs. Then use the aforementioned Previous Apps feature.
  6. Post your plex docker run command as explained in this very first link in the Docker FAQ: https://forums.unraid.net/topic/57181-docker-faq/?do=findComment&comment=564345 Also post a screenshot of the transcode directory setting within the Plex application.
  7. No that shouldn't happen. You must have been having hardware issues, if only bad connections. After you New Config, if parity build is going slowly post new diagnostics before rebooting so we can take a look. The entire 3TB parity build shouldn't take more than 10 hours.
  8. Why are your drives so hot? These disks seem pretty old. Did you test any of these disks before attempting to build an array with them? The SMART attributes for disk1 don't look bad. What SMART errors were you referring to exactly? Your VMs and dockers should be on cache for better performance. Since each data disk in the array is an independent filesystem, your disk1 data should be OK. If disk2 doesn't have anything important on it, I would just New Config with disk1 assigned as is, assign any other disks as needed, and rebuild parity.
  9. Parity swap isn't difficult if your hardware is working well and you follow the procedure exactly. It's very unclear from your description if any of that is true or in fact if parity swap was even appropriate. Do you have any important data on any of the involved disks? Note that parity itself has no data. You probably should have asked for help before now. Maybe Diagnostics would give us something to go on. Go to Tools-Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post.
  10. Every disk including cache is part of user shares. I see you also have VMs enabled. Do you have any VMs? Looks like you are going to be pretty tight with RAM even trying to run dockers. 2GB is fine for simple NAS, but at least 4GB would be my recommendation to attempt dockers, and 8GB to attempt VMs. Can you add RAM?
  11. Docker img is one thing, used by all of your dockers. That is what I assume you meant when you said docker img assigned size 20GB. This is the size you have allocated docker img, and how much of that being used is displayed on the Dashboard. Then later you say plex docker was 19GB. The space used within docker img by each docker can be displayed from the Docker page by clicking the Container Size button at the bottom. Is that what you mean by the 19GB plex docker? Do you have any other dockers? So which of these are you talking about?
  12. OK. Everyone on this thread. I apologize for breaking the link to the Unassigned Devices plugin thread, that was definitely my bad, along with some unexpected behavior from our forum software. That link has now been fixed on the Plugins page and on the Apps page in your Unraid webUI. Even Unassigned Devices plugin now.
  13. It only uses one docker image, preferably on cache. Since you added cache after enabling dockers it got created on the array first. Don't know how you got 3 though and probably not worth finding out. Go to Tools-Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post.
  14. @Hoopster thanks very much for replying. It is your builds that got me thinking along these lines. I figured anything that had M2 would sacrifice SATA ports for it but I just threw that out there. My current cache is SATA SSD and I would be fine with keeping it that way. I noticed that C246 and maybe I would like it better since it sounds like it supports newer CPUs, but I wasn't sure about that OCULink, something I had never heard of until seeing that board. Will there be any problem using that with Unraid? What cables would I need if I just wanted to use the OCULink for SATA drives? Something like this? https://store.supermicro.com/cable/sas-sata/oculink/supermicro-50cm-oculink-to-4-sata-cable-cbl-sast-0933.html
  15. Are you following the SpaceInvader One video?
  16. SMART for that disk doesn't show any bad attributes, but it says the last extended SMART test was a long time ago. Run the extended test. Might be a good time to upsize it anyway, it's small and getting old. But of course you need valid parity to rebuild to a replacement. Did your last successful parity check have zero sync errors?
  17. So was that calibre install before that other thread you posted? The way a misconfigured docker can use RAM is if you have a host mapping that isn't a user share or a disk. The Unraid OS is in RAM, and any path that isn't in one of the mounts (shares or disks or flash) is in RAM just like the rest of the OS. Here is the link so you don't have to go looking for it: https://forums.unraid.net/topic/57181-docker-faq/?do=findComment&comment=564345
  18. Looks like you have probably disturbed disk connections when mucking about in the case. Also, you shouldn't preclear SSDs. Shutdown, check all connections, power and SATA, both ends, including any power splitters. Try again. If you still have problems post diagnostics instead of syslog. Diagnostics contains syslog, SMART for all attached disks, and many other things that give us a lot more information about your configuration and problems. Diagnostics are what we always prefer. Tools - Diagnostics, attach complete ZIP.
  19. On mobile now so haven't looked at Diagnostics yet. Might be useful to have your docker run command for Calibre also. See the first link in the Docker FAQ pinned near the top of the Docker Engine subforum.
  20. Very unlikely and even if it would work for licensing might be a source of problems. Best to use a USB2 port.
  21. One thing that can cause post-read to fail is bad RAM, so memtest might be something to keep in mind. But for that specific disk, SMART is sufficient reason to not trust it.
  22. Could you give more details about this?
  23. Bad connections are a frequent cause of disabled disks. Looks like you have corruption on disk5. When you check the filesystem, you should capture the output so you can post it.
  24. My motherboard died so I have temporarily downgraded to the previous mobo with i3 CPU which I still had in the attic. Looking for mITX motherboard, need 7+ drives on board, though one could be M2 for cache as long as there would still be at least 6 SATA for my 5 data + parity. I am hoping to keep the expansion slot free for possible graphics to play with some VMs. My previous mITX builds have always needed to use that slot for additional SATA. I will also need a CPU to go with it, Intel with iGPU. I have never used a server motherboard, or anything with SAS->SATA. I don't have the broad experience some on the forum do with different hardware. These look like they would work for me: https://www.newegg.com/asrock-c236-wsi-intel-xeon-e3-1200-v5-v6-series-processors/p/N82E16813599009 https://www.newegg.com/intel-xeon-e3-1275-v6-lga-1151/p/N82E16819117784 pcpartpicker doesn't seem to think that motherboard is compatible with any Xeon but that CPU is definitely on the supported list according to the manufacturer website. Looks like CPU went out-of-stock on newegg while I was researching this, but Amazon still has it, and there are other e3-1200 V6 models that are compatible. And I guess I might splurge on ECC RAM while I'm at it. Anybody have anything to say about those or any other ideas?
×
×
  • Create New...