BobCV

Solved my own problem... Turns out that when I installed the docker, I failed to notice that there was an error (I don't think that it was until about the 3rd time of reinstalling it that I noticed the error). At any rate, like Ed, I had created a unique network just the same as he had (except I named mine ProxyNet -- note the capitalization!). However, the docker installation error message stated that the network proxynet (all lower case) did not exist. I went in and removed that network and created another, but in all lower case, and the error went away... problem solved. Not sure if this should be considered a reportable "bug", but users beware! Thanks anyway!

Newbie here (actually, I've been running UnRaid for several years, but I haven't posted much to the forum)... I had started to follow spaceinvaderone's video for setting up a reverse proxy with letsencrypt. Obviously, due to the change from letsencrypt to swag, I then jumped over to his video on updating from letsencrypt to swag, except I just simply installed swag from the get go and followed the common instructions from both videos. It appears that Ed was running UnRaid 6.9.0-beta back in October of 2020, but my current version 6.9.2 only has uptime rather than a Log button to the right of the Autostart button, so no log to view here. Clicking the log from the icon menu brings up a blank log. However, the bigger issue is that clicking the Start option generates an Execution Error with an associated message of "No such container". I've searched the forum for this sort of error with no luck and I've also uninstalled and reinstalled swag but still got the error. Any suggestions?

Thanks. I don't think I'll give up on this group quite yet, but I probably will try multiple approaches.

Even though I've had UnRaid for several years, I consider myself a relative newbie to any Linux based systems. It was very easy to set up and has run faithfully for several years. Like many other folks, I recently ran into the situation where the Lime version of the Plex docker was depreciated, and so, following the instructions on how to transfer my plex library (https://www.youtube.com/watch?v=7RgPx7BN8DE) I swapped over to the offical Plex docker app. Using the instructions from the Youtube video, I was able to easily point the app to my original library files and all was fine with the world for several days. Stored movie media worked just fine, iTunes music media worked, DVR media worked, everything seemed to work fine. After about four or five days, I was listening to the music media on my iPhone app while driving home from work, when suddenly it went dead. I figured that maybe I had a power glitch at home which shut off the server or something like that, but there was no evidence when I got there. I rebooted everything and the Plex docker starts and displays my media library just fine, but when I select any server stored media (movies, DVR, music, etc.), it give a "Playback Error" message stating "Please check that the file exists and the necessary drive is mounted." Live TV and other PLEX media which does not physically reside on my server still works just fine. When I go in to confirm/edit the configuration settings, those settings can "see" the files just fine -- so they don't appear to be hidden or mislinked: Any thoughts on where I might start to debug this issue? I've searched this site and found several postings which were close or somewhat similar, but not exact and the solutions did not seem to fix my particular problem (unless I happened to just overlook the "right" posting). Any help would be appreciated.

Thanks all for the quick responses. It seems that I was a bit anxious for no good reason and, now that I understand how it is intended to function, all is well. I really appreciate the feedback, tutorial, and clarification...

Okay.. Thanks BRiT. That makes all the sense in the world. Appreciate the quick response!

Another newbie here with what's probably a novice question , but I have a system with four 3Tb drives where, obviously, one of them is set up as the parity disk, leaving me with total storage of about 9Tb. I also have two linked 250Gb SDDs for cache which seems to be paired and working properly. My question is that I guess I was expecting the stored data to be somewhat balanced across the 3 disks as storage builds up. Instead, it appears that all data is going exclusively to the first disk with nothing on disks 2 and 3. Is that normal or did I set up something incorrectly? I've checked the forum (admittedly, I may not have searched on the correct terminology), watched setup videos, and tried to see if this is correct or not, with nothing conclusive to point to. Are my expectations just off, or did I set up something incorrectly? If this is normal, when can I expect the other drives to "kick in"? When disk 1 hits 70%, 90%, 100%, or ?? Aside from this, I am absolutely pleased with the performance of this system.

Not exactly sure what I did, but previously, the bios boot order was only visually showing SDD/HDD options. When I just now rebooted into the bios, the same SDD/HDD options were still there, but so were the UEFI and standard USB booting options. I simply reordered them so that the USB was first, then CD, followed by HDD and UEFI. and that worked -- we're good to go! BTW, there was a secure boot option (not enabled) I could find no specific USB secure boot options. Whatever I did to the bios to make the UEFI and USB appear must have been last night because they weren't there the last time I went in yesterday. .. Oh well , we're good now. Thanks all to the prompt replies, I really appreciate them.

The MB is the Asrock Z270 Taichi, the bios is set to Legacy USB mode enabled. Since it does successfully boot from USB with the FreeRaid stick, I can only assume that I have it properly configured to boot from USB. However, I will be contacting the Asrock support team to make sure I'm doing it right. Thanks for the assist

Okay.. Bought a new 16Gb SanDisk Cruzer Fit, fresh out of the container, formatted FAT32 with the UNRAID label, ran the make_bootable file as administrtor, and booted with the exact same result ("This is a NAS data disk and cannot boot system. System halted."). I also noted that, contrary to my earlier comment, that this message also showed up when no flash drive was installed, so I began to suspect that this was a message that has been somehow embedded into the installed SDDs/HDDs based on my earlier FreeNAS installation -- no formatting or configuring -- that I can recall . Fortunately, my MB has a F11 keystroke to select boot devices at power up. Here is where, in addition to selecting from the installed SDDs and HDDs, there are two SanDisk boot options: "UEFI: SanDisk, Partition 1", and "USB: SanDisk:) The first failed to boot, but the second succeeded. So I have now discovered that I can boot, just not in an automated fashion. i also again confirmed that, without modifying the bios from where it is currently configured, I can boot from the same SanDisk flash drive but with FreeNAS installed and boot just fine with no manual intervention. But I just can't seem to do this with the UNRAID configured flash. So I've ruled out my prior thought that it was a flash drive problem. I tried modifying the bios USB settings for legacy compatibility for Enabled/Disabled/UEFI Only modes, but only the default Enabled mode worked at all. FYI, the MB is an Asrock Z270 Taichi So far, I have successfully installed a trial license, configured my storage shares, and installed some useful plugins -- and it all seems to work just fine. But no hands free booting. And that will be a problem. Any theories/thoughts/help??

It's a 16Gb version and I believe it _was_ GPT when purchased. However, with my subsequent reparitioning and formatting, I suspect that this is honked up. When it was set up for FreeNAS, there was a 1Gb partition that was identified by Windows as an EFI system partition and a 14Gb unknown partition. After repartitioning and formatting as FAT32, it is simply identified as an Active, Primary Partition. So I think you possibly are on to something there. I'm not totally familiar with GUID formatting, but is the Windows Diskpart tool able to perform this or is there another tool out there I can obtain to "fix" this? Okay, I was able to figure out out to convert it to a GPT partition, so the disk shows up in Windows as a EFI system partition and the diskpart tool states that it is identified as gpt. I reformatted, reinstalled, reran the make_bootable, but still no joy -- same error, still puzzled.

Can't disagree with your thought since I did see this same sort of error message on the FreeNAS forum sight. However, I did perform a full repartition and full format of the disk before installing UNRAID. Since they are cheap, a new flash drive may be a good option, but I do not have one laying around.

Hi all, newbie here. I searched the forum for this issue with no success. My apologies if I err. Just downloaded 6.3.2 to a Sandisk Ultra Fit USB drive which had been formatted as FAT32 with a label of UNRAID, successfully ran the "make_bootable.bat" file (yes, as administrator) and text on the screen implied that this process was successful. When booting the system I immediately get the message "This is a NAS data disk and cannot boot system. System halted." (No UNRAID boot menu). The bios was configured to boot first from USB then from DVD (confirmed that the drive was empty). If I configure the bios to only boot from USB and nothing else, I get no message and it immediately opens the bios (there are no other OS or formatted drives in the system). I figure that it has to be something with the usb boot drive, but I can successfully install FreeNAS on this same SanDisk drive and it will successfully boot. Any suggestions?