IrishFavor

@jonathanm Oh i guess that is my mistake what does it use for the boot loader when booting the the unraid splash screen it just looked alot like my other bootable distro's that use grub. Any ideas on something else i can try?

Bump The issue is still going on, i have a theory that if i upgrade the Unraid USB from Grub to Grub2 it might solve the issue. Any thoughts anyone know how i can go about doing this? I am familiar tho still a novice with Linux and Bash. However i don't think that this would be that complicated a task. I have just tested both drives that i had on another computer and they both booted without issue in BIOS and UEFI. So i know it is not an issue with the drives and as stated above i am able to boot from a Live Ubuntu USB and that works fine. I believe that USB was using the YUMI Multiboot based on Grub2.

i had a similar issue after an upgrade, what happens when you go to the IP address/ Main (ie. http://192.168.1.100/Main)?

Few questions that may help get answers for you. When you say performance issues are you referring to network slowness (ie. transferring stuff to the VM over the network, browsing the internet) or slowness within the VM where opening files and directories and applications stored on the VM are slow? or a bit of both? Another question related to the above are you running your VM from your cache pool or from your storage array? Second about building a VM with no network attached if i remember correctly you will configure the IP address and network settings in the host os on the VM, Perhaps someone else can confirm this as my service is down for the moment and im having some issues with booting to unraid.

Iv had similar issues when my Docker.img files was to small i increased the size and then redeployed the docker container using the same config locations everything imported without issue and i was back up and running, Perhaps you are having a similar issue, also check to see do you have your dockers running from your storage array or your cache drive? i have hears similar issues having to do with disks going to sleep i have not had that issue but that could be another cause.

TL;DR: Upgraded server hardware due to power failure and new server will not boot into Unraid. Problem: Upgraded server hardware from Dell Poweredge R710 to a Dell Poweredge R910 when attempting to boot from USB i get an error message; Failed to Allocate memory for Kernel command line, bailing out booting kernel failed: bad file number. I recently had a power failure which rendered my Dell Poweredge R710 inoperable, as a result i was able to obtain a replacement for it. The replacement device is a Dell Poweredge R910. The configuration is: 4 x Intel Xenon E7-4850 (10 Core/ 20 thread) 64GB DDR3 ECC Registered Memory Perc H700 Raid controller iDRAC 6 Enterprise I have validated that BIOS is up to date according to https://www.dell.com/support/home/en-us/product-support/product/poweredge-r910/drivers I have verified that the hardware is recognized in the BIOS and posts without issue, the problem comes when i attempt to boot from the Unraid USB in UEFI mode, when i attempt to boot in legacy mode it never gets to the splash screen (GRUB Loader) to boot Unraid. Seeing that there were several people with similar issues i looked for resolution and was unable to find one: https://forums.unraid.net/topic/66286-failed-to-allocate-memory-for-kernel-command-line-bailing-out-booting-kernel-failed-bad-file-number/ https://forum.level1techs.com/t/failed-to-allocate-memory-for-kernel-command-line-bailing-out-booting-kernel-failed-bad-file-number-unraid-6-6-7/140482/11 https://linustechtips.com/main/topic/1047343-failed-to-allocate-memory-for-kernel-command-line-bailing-out-booting-kernel-failed-bad-file-number-unraid-667/?tab=comments#comment-12418630 After reading the updates in the posts above it appears that there may be 2 potential causes of the issue with booting to the Unraid USB. there is an issue with the GRUB boot-loader not being able to communicate with the onboard memory to load the OS. I was able to boot a multi-boot USB into Ubuntu from a GRUB boot menu, Ubuntu loads and sees all memory and CPU cores and threads. There is an issue with the allocation of memory as video memory in the BIOS/ UEFI that causes the failure of the booting of Syslinux. I am unable to change the allocation of system memory in the BIOS, it currently shows 8MB and does not allow for editing. As a side note i have attempted to boot the USB in legacy mode as a drive, hard disk, and floppy none of which have solved the issue. I have also built a new flash-drive with the utility found at https://unraid.net/download using the latest stable release both with and without UEFI support. I have also tried the internal and external USB (front/ back) and all give the same results. I am unsure how to resolve this issue any assistance is greatly appreciated, I am unsure what would allow the R710 to boot in both UEFI and legacy without issue whereas the R910 is having issues.

Aw crap i must have hit delete by accident while testing thanks for that catch, i don't think that was the issue i will update it and test. if that doesn't work as i have been changing settings perhaps a refresh from default is needed. I'll delete the apps and docker.img and try again.

apologies yes i wrote /Data when i should have written /data when i changed the path within the settings from ${AppDir} to /data it would error out. however when i changed it back to ${AppDir} it appears that the downloads would initiate correctly.

Confirmed that changing the MainDir back to ${MainDir}/downloads allows for the downloading of files however UMASK set to 000 does not appear to solve the issue with files being moved over. Sonarr Log: DownloadedEpisodesImportServiceImport failed, path does not exist or is not accessible by Sonarr: /home/nobody/downloads/downloadscompleted/TV Shows/NAMEOFTVSHOW.S01E03.1080p.WEB.H264-PETRIFIED1:06pm EpisodeSearchServiceEpisode search completed. 1 reports downloaded.12:54pm DownloadServiceReport sent to NZBget. NAMEOFTVSHOW.S01E03.1080p.WEB.H264-PETRIFIED12:54pm NzbgetAdding report [NAMEOFTVSHOW.S01E03.1080p.WEB.H264-PETRIFIED] to the queue.12:54pm DownloadDecisionMakerProcessing 6 releases12:54pm NzbSearchServiceSearching 1 indexers for [NAME OF TV SHOW: S01E03]12:54pm RssSyncServiceRSS Sync Completed. Reports found: 100, Reports grabbed: 012:51pm DownloadDecisionMakerProcessing 100 releases12:51pm RssSyncServiceStarting RSS Sync12:51pm EpisodeSearchServiceEpisode search completed. 1 reports downloaded.12:50pm It appears that changing the UMASK had no effect or the wrong setting was used?

Setting MainDir back to ${MainDir}/downloads appears to allow downloading of files: INFOThu Nov 28 2019 12:51:30Successfully downloaded NAMEOFTVSHOW.S01E01.INTERNAL.1080p.WEB.H264-DEFLATE/dTPKvBPUY1j5F9.part02.rar Letting file finish with UMASK set to 000 to see if file will now import.

Testing with MainDir set to \Data\downloads appears to give same error: ERRORThu Nov 28 2019 12:47:09Could not create file /Data/downloads/tmp/nzb-38.tmp

Testing with MainDir set to \Data appears to give this error: ERRORThu Nov 28 2019 12:43:09Could not create file /Data/tmp/nzb-20.tmp Now testing with \Data\downloads

Ok, just tried downloading with UMASK set to 000 and NZBget: /data = /mnt/user/Downloads/ /config = /mnt/cache/appdata/binhex-nzbget/config Sonarr: /data = /mnt/user/Downloads/ /media = /mnt/user/TV Shows/ /config = /mnt/cache/appdata/binhex-sonarr/config with path set in ZNBget to ${MainDir}/downloads, that did not resolve the issue. I will now try with /Data set for the MainDir.

Ok, ill try 000. now i did look at Sonarr and did not see an option for UMASK is this something i would need to SSH into the container and set?

I am using all Binhex containers so i would imagine they are all set with similar settings? And for the paths in the NZBget when it says ${AppDir} that should refer the the \Data Location = /mnt/user/Downloads/ So in that location you should see /mnt/user/Downloads/downloads/completed and /mnt/user/Downloads/downloads/intermediate ${MainDir} should refer to the previous location of /mnt/user/Downloads/downloads So my understanding is if i have no UMASK set and my Data = /mnt/user/Downloads in Sonarr then it should be able to locate the files and move them?

That is correct it should be: NZBget: /data = /mnt/user/Downloads/ /config = /mnt/cache/appdata/binhex-nzbget/config Sonarr: /data = /mnt/user/Downloads/ /media = /mnt/user/TV Shows/ /config = /mnt/cache/appdata/binhex-sonarr/config If i understand correctly tho if UMASK is set to 1000 it will not use that feature so it shouldn't filter anything out correct?

UMASK is set to 1000

Thanks all for the reply, ok so i understand that i need to have a common path for the 2 apps. I have tried mapping sonarr to the download location and i get the same thing it will see the files and can initiate a download however it does not move the files or rename files etc. I have even created a separate share to test on one of the disks in the array instead of the cache drive. I have also tried restoring permissions via the script above. As of now the config for both apps are as follows: NZBget: /data/mnt/user/Downloads/ /config/mnt/cache/appdata/binhex-nzbget/config Sonarr: /data/mnt/user/Downloads/ /media/mnt/user/TV Shows/ /config/mnt/cache/appdata/binhex-sonarr/config

Im having issues with what i think to be permissions between 2 docker apps (NZBget, Sonarr). Docker containers: binhex-nzbget Settings: /data/mnt/cache/appdata/binhex-nzbget/data /config/mnt/cache/appdata/binhex-nzbget/config binhex-sonarr (Version 2.0.0.5338, Mono Version 5.20.1) Settings: /config/mnt/cache/appdata/binhex-sonarr/config /data/mnt/cache/appdata/binhex-sonarr/data/ /media/mnt/user/TV Shows/ When i add a show it is able to connect to NZBget to search and download a file, the file will successfully download and NZBget states that it unpacks the file. However Sonarr never picks up the file. It appears that he file is able to be seen however i get the following error. Import failed, path does not exist or is not accessible by Sonarr: /usr/local/bin/nzbget/downloads/completed/TV Shows/NAMEOFTVSHOW.S01E06.NAMEOFEPISODE.1080p..WEB-DL.DDP5.1.H.264-NTb I have tried both the Docker Safe New Permissions under settings as well as SSH into the server and applying permissions to the directory with: chmod -R 777 ./ None of which have resolved the issue, after which i wiped the configuration and re-imaged the flashdrive and started from scratch however the issue persists. Any assistance would be greatly appreciated.

Here is an idea, both light and dark versions available.

Yea the dell motherboard is not compatible with the supermicro chassis that i have however down the road i may by a compatible board to replace them both. For the time being i need the super micro chassis as it has enough bays for what i need. Currently im running 36TB with disks arranging from 2TB - 6TB about 16 drives in total. As i upgrade the smaller drives the physical space will be less of a requirement. currently i am running it as a media server, serving to about 28 users approx 4-6 users on at a time pulling full HD files and i have not had any issues thus far. However i want to upgrade for a few reasons, such as power efficiency and having more resources to be able to run virtual machines and a home automation server. If i can find a good deal on a SSI CEB motherboard CPU (at least 10 cores) and RAM then i will upgrade however for the moment i dont have to spend anything other then the connections between the 2 so i feel that this is the best economic choice for me at the moment.

ken-ji thanks for the response those look to be pretty reasonable. I will order a few after the holidays and give them a test and report back my findings. I did notice that they do not appear to interface with the motherboard at all, is it safe to assume that the system that they are in will be mainly used to house the drives and power them? Thus not being used computationally?

As Ken-Ji stated above it would depend on the connectors, Would something like this do the trick? http://www.scsi4me.com/dell-perc-6-e-sas-raid-controller-for-sas-external-storage-system-optional-controller-dell-poweredge-2900-iii-2950-iii.html

Sorry for the delayed response, work has gotten crazy with the holidays moving in. Keeping them on 24/ will not be a problem. I did not even take into account slaving the power supply together. Currently there is no battery backup however that is my next purchase and i was going to run the APC plugins for power management and safe shutdown as far as turning them on i am not sure if there is a way to have them both power back on once power is restored. As for the models they are whatever came standard with the machines they both have redundant power supplys. For the Supermicro i am not entirely sure on the model of the machine, it appears that the chassis and PSU are probably the same as [ 6048R-E1CR72L ] (https://www.supermicro.com/products/system/4U/6048/SSG-6048R-E1CR72L.cfm). As for the Dell 710 the speck sheet can be seen here (http://www.dell.com/us/business/p/poweredge-r710/pd) as for any connections between the server i have not purchased anything, however i am willing to invest the time and money to get this working. Currently they both exist on the same local network using a gigabit connection to either machine.

Not sure if this is the correct place for this question, If not please feel free to direct me to a better place. Currently i have 2 servers 1 is an old Super-micro with 24bays and is currently running my unraid. However the second server is a dell 710 that has much more processing power but only 6 drive bays. I would like to keep my drives in the super-micro and use it as a SAN while utilizing the Dell 710's processing and memory resources. I have not had a chance to test this and have not seen any similar setups or guides. Would creating a 2nd server with another hypervisor adding the drives from the super micro to the drive pool and attaching to the dell via an external JBOD connection allow me to see the drives within the unraid hypervisor and assign disks? Thank you for any assistance in regards to this.