ksd2kd

I use pfSense and it was your question that got me to check the vlan config again. I had bound vlan40 to the wrong interface. I switched it to the unRAID interface and all is working now. I was just too focused on the unRAID settings trying to troubleshoot and got tunnel vision. Thanks!

Nothing? Is it even possible to get a VM to use a vlan?

I've have a few vlans setup for use by some docker containers and it all works as expected. However, when I tried to set up a VM on one of those same vlans I can't get it to work. All the setting look ok as far as I can tell but I can't get network connectivity on my win10 vm. Can someone take a look at these configs and tell me what I've done wrong.

Unable to remove partition. unRAID: v6.6.6 UD: v2019.03.22 - Enabled Destructive Mode - Unmounted disk - Clicked the '+' icon next to drive icon - Clicked the red 'x' - Typed 'Yes' - Clicked 'Remove' - I can see the red removing spinner pop up next to the partition for a second or two. The partition is not removed. I can remount it and access all the files. I've tried a few times and I know I've done this before. edit: Just tried reinstalling UD, same result edit: After rebooting, the drive is now showing up as unformatted. Clicked Format, after a few seconds the same partition shows up again but this time it's empty which is what I wanted so I guess I'm good to go.

It came back ok after a hard reset, wait and see what happens. Thanks for reminding me about the BIOS.

My unRAID server normally updates docker images at 6:00am. This morning however, the system became unstable just after autoupdate finished. I can't shutdown from the GIU because parts of it are missing. I tried running diagnostics but that doesn't work either. All the docker containers web frontends are inaccessible but I can see that the containers are running. I can ssh into the box just fine and was able to get the syslog. I tried to shutdown but it just hangs. root@unraid:/# poweroff Broadcast message from root@unraid (pts/0) (Fri Mar 8 10:11:07 2019): The system is going down for system halt NOW! It's been like that for about an hour. There are definitely bad things happening at the end of the syslog right at 6:01 if someone wouldn't mind taking a look. Also, is there some other way to do a clean shutdown from the console? syslog-tail.txt

You need to install the 'CA User Scripts' plugin and create a script that will run on array startup. The plugin has a nice help section that will walk you thru it.

@Jclendineng I just added the commands to a user script per BRiT

@Frank1940 Just what I was looking for. @DoItMyselfToo I've had bad batches of spinning HDs back in the day so it could just be that. I got a new SanDisk Ultra Fit. I'll keep this thread open until I either solve it or give up. Thanks all.

I was able to get the array started after getting a new key. I went thru and checked each of my docker configs and all file mounts were to /mnt/user/appdata or other /mnt/user shares. Are there any other ways for a container to write to the boot drive? What if one of them were writing excessively to their writable (top-most) container layer, where would that end up?

Here is a link to the topic I opened after the first one failed. https://lime-technology.com/forums/topic/70174-os-flash-drive-w12m-writes/ At first I thought I'd been hacked because of the way all my shares had been made public. I was never able to figure out what caused it but I did recheck my Docker container configs after to see if they were using the USB, but it all looked ok. When my replacement failed I wasn't able to run a diagnostic. I can't remember the error I got from the command line, something like 'bus error'. The USB was dead so that would make sense. It's hard to believe I got 2 bad USB drives so perhaps I do have something wrong with my container configs per @Frank1940 and @DoItMyselfToo.

The two drives are/were both 32G Lexar JumpDives bought together and only used for my unRAID server. Each failed in a similar way. I can't see any files when mounted on my server or in my macbook. When I fired up Disk Utility on the mac to see if I could possibly reformat and reinstall the os, it just hung, and was never able to even see the drive. Also, I have a tool called SpinRite which I've been using for decades to recover spinning drives and have had good luck with SSDs and flash drives as well. SpinRite hung too when trying to analyze the drives. I've learned over the years that if SpinRite can't bring it back, it's gone.

I'll take a look at that as soon as I can get the array started. The start button is greyed out because of the license issue. I'm totally down until I can get a response form support.

My USB failed a few months back and I went thru the replacement procedure per:https://lime-technology.com/replace-key Then yesterday, the new USB failed and I'm having to do this again. I was able to restore from a backup and start the server but the button for 'replace key' is greyed out. I sent an email to support and a link to this thread. I guess it has to do with the 12 month thing.

?

Wow, didn't know 6.5.0 was out! I had to got to Tools>Update>CheckForUpdate to see that. I could swear a new update alert used to show up on the gui banner.

I'll give it a try. To be clear, you mean prerelease v6.5.1.-rc6.

I saw this today in FCP warnings. Searching around I found it looks to be hardware/driver/firmware issue. The only hardware change is that I recently moved the OS thumb drive from usb3 to usb2 after advice from: https://lime-technology.com/forums/topic/70174-os-flash-drive-w12m-writes/?tab=comments#comment-642941 One thing though, I couldn't get the bios boot preferences to recognize the usb2 drive but was able to see it in a boot override screen. Bad usb2 ports? unraid-diagnostics-20180417-1550.zip

It's using USB 3. Why is 2 preferred? So, you think it just flaked out then? Do you know if the os flash drive be cloned/backed up? Isn't it serialized or something for licensing purposes?

OS: v6.4.0 Model: Custom M/B: Gigabyte Technology Co., Ltd. - Z77X-UD5H CPU: Intel® Core™ i7-3770K CPU @ 3.50GHz HVM: Enabled IOMMU: Disabled Cache: 128 kB, 1024 kB, 8192 kB Memory: 32 GB (max. installable capacity 32 GB) Network: eth0: 1000 Mb/s, full duplex, mtu 1500 eth1: not connected Kernel: Linux 4.14.13-unRAID x86_64 OpenSSL: 1.0.2n So, last night I found all my shares had been made public via SMB, not just according to the GUI, I could see and mount all my shares remotely, which made me think security breach. I tried to change them back but was unable, hitting apply did nothing! After changing my underwear, I started poking around and noticed that the OS flash drive had over 12M reads/writes since last reboot. Also, I could not bring up the Dashboard and could not run Fix Common Problems. I saw in the syslog that the os flash drive had failed (all those writes may have exhausted its lifespan?? ) so I downloaded the diagnostics file and tried to stop the array, which didn't go well and I had to crash the system. After a restart the os would not boot, no GUI, no ssh, no ping. The flash drive would not mount on my MBP, just flashed for a few seconds and self ejected. I did manage to get the drive working again by running 'dd' on it over and over. This time the os booted normally and passed it's parity check. Unraid seems to be working file now. So, I have two questions: Can some one take a look at the diagnostic dump and help me get some insight into what caused this. Do you think that the drive just failed and that's what precipitated all those read/writes, or was it the other way around? Or, perhaps something else. Also, I obviously need to get the os off that drive and onto another. I have an identical one that I bought at the same time specifically for unraid. Is it possible to make a copy/backup. I remember reading something about a hardcoded uuid so just a straight dump might now work. Thanks for taking a look. unraid-diagnostics-20180315-1855.zip

Yeah, I checked that -> ELK Stack Prerequisites These settings need to be made at the host level. Do you know if that go script is the right place for setting kernel parameters like these?

I'm getting an error while starting elasticsearch via docker max file descriptors [40960] for elasticsearch process is too low, increase to at least [65536] max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144] What's the right way to tweak those params? I've looked around but didn't find a definitive answer. Should I just add this to /boot/config/go? ulimit -n 65536 sysctl -w vm.max_map_count=262144 unRAID v6.3.2

How do I persist Settings across restarts? I changed the listening port to suit my needs and disabled DTH and PEX but after restarting, they're all back to the defaults. update: Just read this on the github repo for this app: "Settings, changed by the user through the "Settings" panel in ruTorrent, are valid until rtorrent restart. After which all settings will be set according to the rtorrent config file (/config/rtorrent/rtorrent.rc),this is a limitation of the actual apps themselves."

Overloading repo works and you're right about the need to add a dedicated field. As it is now all runtimes must be baked into the image. Thanks for the super fast reply.

A docker run command looks like this: docker run [OPTIONS] IMAGE [COMMAND] [ARG...] On the container run form I get to from "Docker" -> "Add Container" where do I add the container runtime COMMAND and any associated ARGS? I tried "Extra Parameters" but that field maps to OPTIONS. I'm new to unRAID and the forums so let me know if there's a better place to post general questions like this.