Tony13

It's a Gigabyte GA-Z170MX-Gaming 5. Hope this helps someone. Thanks again.

Well it booted fine on my X220. So I messed around with the BIOS/UEFI and there was a launch option set to Auto for the flash drive, turns out it was trying to UEFI boot it which in turn seems to mess up the fallback BIOS boot. Setting it to Hard Drive allows it to BIOS boot correctly. Must have decided to see the flash drive as a new device after the upgrade and apply the Auto setting. Thank you for the support, very much appreciated.

Thanks for the continuing assistance. Just tried your suggestion Frank and I'm still stuck with a blinking cursor.

I left the rest of the files in the previous folder, I only copied bzimage and bzroot to the root of the flash drive. When I power on, the system POSTs then goes straight to a blinking white cursor in the top left on a black screen. I've removed all boot options except for the flash drive.

Thanks for the replies, sorry I've only just returned to this post, I went away on holiday for a few days and came back to no internet which has finally been resolved today. I was coming from 6.2.2 and no I didn't backup I used the bzimage and bzroot files in Previous but still have no luck booting. Any other recommendations?

Hi Everyone, So I upgraded to 6.2.4 via the plugins section and now my unRAID USB won't boot, I just get a flashing white cursor of my mobo looking for an OS. I've checked all my boot options (UEFI and legacy), cleared a memtest and my server can still boot other live USBs and PXE boot. Which leads me to the conclusion of a corrupt update? Could anyone provide advice on what to do to get my system up and running? I know my disk configuration but that's about it. Many Thanks.

OPs post says they have a AMD FX-8350 which is an 8 core without hyper-threading, there are 4 modules and 2 cores per module. I don't know anything more but would it be safe to assume core 0 and 1 share the same module? Or did AMD go the other route with core 0 and 4 etc. Maybe there is some information about what cores unRAID likes to use on AMD CPUs somewhere that might help.

It might help to mention the version of unRAID you are running if you make future threads. CPU pinning is explained and demonstrated in the top sticky topic of this sub-forum. Hyper-V is explained in the wiki documentation. Search is your friend

I think your issue might be different to mine. I don't think mine was pulling any data because the install was never managing to get addresses from the DNS thus the timeout. Where as a HTTP code 400 is according to w3.org, I guess yours is only happening for linuxserver dockers like mine though? Maybe head to their forums and ask around?

Beets is predominantly a command-line tool, you will need to import music into the Beets database before it will show in the webGUI. This should get you started, docker exec -it Beets bash

SSH to your unRAID and run, docker exec -it Beets bash That should get you started.

I've read that some Realtek adapters have problems with WoL and S3 sleep. Does your unRAID box post to its default screen when it wakes up? Or are you running headless? You might want to plug a monitor in and see. I'd hazard a guess that the NIC isn't waking up when the system does.

Do you have "Use cache disk" set to yes on the shares you wish to use the cache drive? Typically files that go to the cache are then moved to the array by the scheduled file mover.

Update. DNS messed up by PiHole (I think). Set DNS in unRaid network settings, everythings all good now. Running unRaid 6.2.0-beta21 I can install dockers from a number of different repositories. They seem to take a little while but that isn't the problem. Any dockers from linuxserver.io refuse to pull, I have a notion from some comments around the internet that it could be due to an incorrect MTU value. Can anyone direct me to a solution? My Google-fu has failed me. Install log below. Pulling image: linuxserver/couchpotato:latest IMAGE ID [98aae5d8e559]: Pulling image (latest) from docker.io/linuxserver/couchpotato. Pulling image (latest) from docker.io/linuxserver/couchpotato, endpoint: https://registry-1.docker.io/v1/. Pulling dependent layers. IMAGE ID [f7eef3e8d2a5]: Pulling metadata. TOTAL DATA PULLED: 0 B docker: Error response from daemon: Get https://registry-1.docker.io/v2/linuxserver/couchpotato/manifests/latest: Get https://auth.docker.io/token?scope=repository%3Alinuxserver%2Fcouchpotato%3Apull&service=registry.docker.io: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers). See '/usr/bin/docker run --help'. Many Thanks.