October 5, 20241 yr Community Expert 1 minute ago, saber-raider said: I can confirm that this workaround works. Thank you so much for taking the time and effort to address this issue; I really appreciate it. I've also opened a ticket with TerraMaster support and made them aware of this thread and the workaround. Hopefully, a long-term solution will be found soon. I'm new to Unraid and was wondering if there's a risk that a future update could modify the first line in `/boot/syslinux/syslinux.cfg`, potentially preventing the system from automatically booting into the OS after an upgrade/reboot cycle? Very rarely get changed last update was to update mem test but it was only that option changed. Unlikely that option has will be changed.
October 5, 20241 yr 18 hours ago, Piece said: I was able to get my F6-424 Max to auto boot straight into unraid by editing the first line in the /syslinux/syslinux.cfg to be: default Unraid OS This does however make it skip over the boot loader selection menu all together though, so i guess it might be slightly inconvenient if for whatever reason you were in a situation where you needed to boot into the GUI Mode or Safe Mode. You would have to go back into the usb and edit the line again. Im not really familiar with syslinux or bootloaders at all to know if there is any better work around at the moment though. I guess something about that bootloader menu it doesn't seem to like auto booting into it. I can already confirm that this workaround fixes the auto-boot problem. Currently i'm running Unraid on a Terra Master U8-500 Plus and i stumbled over this issue. Many Thanks for your investigation 💪
October 5, 20241 yr Author 21 hours ago, Piece said: I was able to get my F6-424 Max to auto boot straight into unraid by editing the first line in the /syslinux/syslinux.cfg to be: default Unraid OS This does however make it skip over the boot loader selection menu all together though, so i guess it might be slightly inconvenient if for whatever reason you were in a situation where you needed to boot into the GUI Mode or Safe Mode. You would have to go back into the usb and edit the line again. Im not really familiar with syslinux or bootloaders at all to know if there is any better work around at the moment though. I guess something about that bootloader menu it doesn't seem to like auto booting into it. Many Thanks! This workaround works for me too! I'm also running an F6-424 Max.
October 8, 20241 yr On 10/5/2024 at 2:19 PM, Sascha147 said: Many Thanks! This workaround works for me too! I'm also running an F6-424 Max. This is why PLOP or grub is better for booting.
October 8, 20241 yr Author 5 hours ago, OLD SALTY CRAB said: This is why PLOP or grub is better for booting. Can confirm i never had this kind of issues with grub
October 8, 20241 yr Thanks for the advice. Unraid boots, but I am unhappy I don't have a boot menu. Hopefully, I won't need the boot menu any time soon. Has anybody tried vesamenu.c32 instead of menu.c32? It is part of syslinux.txz package. I am not sure on which version of Slackware latest stable unRaid is based. https://packages.slackware.com/?r=slackware64-current&p=syslinux-4.07-x86_64-4.txz&f
October 9, 20241 yr I can confirm this works on my F6-424 MAX. Maybe Unraid can actually support vesamenu and newer features in further releases. On 10/4/2024 at 4:28 PM, Piece said: I was able to get my F6-424 Max to auto boot straight into unraid by editing the first line in the /syslinux/syslinux.cfg to be: default Unraid OS This does however make it skip over the boot loader selection menu all together though, so i guess it might be slightly inconvenient if for whatever reason you were in a situation where you needed to boot into the GUI Mode or Safe Mode. You would have to go back into the usb and edit the line again. Im not really familiar with syslinux or bootloaders at all to know if there is any better work around at the moment though. I guess something about that bootloader menu it doesn't seem to like auto booting into it.
October 20, 20241 yr On 10/4/2024 at 10:28 PM, Piece said: I was able to get my F6-424 Max to auto boot straight into unraid by editing the first line in the /syslinux/syslinux.cfg to be: default Unraid OS Thanks for this!
October 20, 20241 yr On 10/9/2024 at 2:25 AM, OLD SALTY CRAB said: I can confirm this works on my F6-424 MAX. Maybe Unraid can actually support vesamenu and newer features in further releases. Slackware (the upstream Linux distro) has has similar issues with "black screen" booting. With the latest release, they switched to Grub2 instead of LILO/ELILO (which, like syslinux [that Unraid uses] haven't been updated since 2014/2015). Hopefully, at some point Unraid can look at making a similar switch.
October 21, 20241 yr On 9/24/2024 at 8:33 PM, Snubbers said: Small update, Terramaster support just got back with surprising news! I've sent images of the BIOS and all details requested, here's hoping.. I've been messing around with the NAS a bit more, and hopefully this issue can be fixed as the HW is quite good! I've tried a 64GB RAM upgrade and that was perfect, and will be trying some newer M.2 NVME Drives to see if I can get ASPM working on those, if I enable it on the WD SN750's (4 years old now!) I get recoverable errors once it goes to L1 ASPM which is not uncommon with older NVME drives! I'll also install windows 11 on a spare HDD and boot to that to see about updating the ASM1166 firmware if it is not the latest. How did it go with ASPM tests? I've always had "visual" problems on nasboxes(f4-424 pro, asustor 6704 etc) with recoverable errors but never "real" problems so I have just hidden the errors. Did you needed to ug ASM1166 FW, or is it recent? A Bummer that a FW-upgrade cant be done without Windows...
October 21, 20241 yr If anyone would like to try something out of the box, I started playing with Grub2 as a bootloader for Unraid instead of syslinux. IMPORTANT DETAILS This will only change the UEFI bootloader; if you are using legacy boot, it will do nothing. Before installing, you should have access to both the Unraid server and a computer that you can use to modify the flash drive (in case you need to restore the default loader). If you have problems booting via the new bootloader, remove the EFI folder and restore the EFI- folder. Installation Rename the existing EFI folder on the flash drive back to EFI- (this is your backup folder in case you have issues) Copy the EFI and grub folders from the ZIP file to the flash drive. Details on the creation process and boot config here: https://gist.github.com/dkaser/18064a5a7d282c3d1b59eb4ee901242b grub-test.zip
October 21, 20241 yr 33 minutes ago, EDACerton said: If anyone would like to try something out of the box, I started playing with Grub2 as a bootloader for Unraid instead of syslinux. Keep in mind that mods like this are not supported in any way. There is functionality in the webgui that reads the syslinux config files so not everything will work right on Grub. Although we are also testing Grub internally and have been adding support to the webgui. Zero guarantees though, this is not a released feature.
October 21, 20241 yr 7 hours ago, BarbaGrump said: How did it go with ASPM tests? I've always had "visual" problems on nasboxes(f4-424 pro, asustor 6704 etc) with recoverable errors but never "real" problems so I have just hidden the errors. Did you needed to ug ASM1166 FW, or is it recent? A Bummer that a FW-upgrade cant be done without Windows... Using the following in a script running after the array starts, I've had zero errors in the logs now with some pretty extensive use of the NAS, and idle power with 5 x 14TB 7200RPM drives + 2 NVME Samsung 990 Pros + 1 Crucial MX500 4TB is 21W, and hourly average with all dockers/vms running is 25w the majority of the time, but during scheduled backups and other media duties (downloading etc). It averages 30W over a day.. Prior to the power tweaks, it was almost double that.. I've not upgraded or checked the ASM firmware at this point, I could easily boot to windows using an external USB HDD and do an upgrade, but at this point 30W average over 24hours with nearly 20 containers running and a VM is about as good as I need. # Enable SATA link power management echo med_power_with_dipm | tee /sys/class/scsi_host/host*/link_power_management_policy # Runtime PM for I2C Adapter (i915 gmbus dpb) echo auto | tee /sys/bus/i2c/devices/i2c-*/device/power/control # Autosuspend for USB device echo auto | tee /sys/bus/usb/devices/*/power/control # Runtime PM for disk echo auto | tee /sys/block/sd*/device/power/control # Runtime PM for PCI devices echo auto | tee /sys/bus/pci/devices/????:??:??.?/power/control # Runtime PM for ATA devices echo auto | tee /sys/bus/pci/devices/????:??:??.?/ata*/power/control Edited October 21, 20241 yr by Snubbers
October 21, 20241 yr 6 hours ago, ljm42 said: Keep in mind that mods like this are not supported in any way. There is functionality in the webgui that reads the syslinux config files so not everything will work right on Grub. Although we are also testing Grub internally and have been adding support to the webgui. Zero guarantees though, this is not a released feature. I never said it was supported, I said it was out of the box 😂
October 22, 20241 yr 12 hours ago, Snubbers said: Using the following in a script running after the array starts, I've had zero errors in the logs now with some pretty extensive use of the NAS, and idle power with 5 x 14TB 7200RPM drives + 2 NVME Samsung 990 Pros + 1 Crucial MX500 4TB is 21W, and hourly average with all dockers/vms running is 25w the majority of the time, but during scheduled backups and other media duties (downloading etc). It averages 30W over a day.. Prior to the power tweaks, it was almost double that.. I've not upgraded or checked the ASM firmware at this point, I could easily boot to windows using an external USB HDD and do an upgrade, but at this point 30W average over 24hours with nearly 20 containers running and a VM is about as good as I need. # Enable SATA link power management echo med_power_with_dipm | tee /sys/class/scsi_host/host*/link_power_management_policy # Runtime PM for I2C Adapter (i915 gmbus dpb) echo auto | tee /sys/bus/i2c/devices/i2c-*/device/power/control # Autosuspend for USB device echo auto | tee /sys/bus/usb/devices/*/power/control # Runtime PM for disk echo auto | tee /sys/block/sd*/device/power/control # Runtime PM for PCI devices echo auto | tee /sys/bus/pci/devices/????:??:??.?/power/control # Runtime PM for ATA devices echo auto | tee /sys/bus/pci/devices/????:??:??.?/ata*/power/control That is really good results. I’ll be running unraid on proxmox with ~15 containers, but also ~10 vms and lxcs. All ssd/nvme.
October 23, 20241 yr On 10/21/2024 at 8:11 PM, Snubbers said: Using the following in a script running after the array starts, I've had zero errors in the logs now with some pretty extensive use of the NAS, and idle power with 5 x 14TB 7200RPM drives + 2 NVME Samsung 990 Pros + 1 Crucial MX500 4TB is 21W, and hourly average with all dockers/vms running is 25w the majority of the time, but during scheduled backups and other media duties (downloading etc). It averages 30W over a day.. Prior to the power tweaks, it was almost double that.. I've not upgraded or checked the ASM firmware at this point, I could easily boot to windows using an external USB HDD and do an upgrade, but at this point 30W average over 24hours with nearly 20 containers running and a VM is about as good as I need. # Enable SATA link power management echo med_power_with_dipm | tee /sys/class/scsi_host/host*/link_power_management_policy # Runtime PM for I2C Adapter (i915 gmbus dpb) echo auto | tee /sys/bus/i2c/devices/i2c-*/device/power/control # Autosuspend for USB device echo auto | tee /sys/bus/usb/devices/*/power/control # Runtime PM for disk echo auto | tee /sys/block/sd*/device/power/control # Runtime PM for PCI devices echo auto | tee /sys/bus/pci/devices/????:??:??.?/power/control # Runtime PM for ATA devices echo auto | tee /sys/bus/pci/devices/????:??:??.?/ata*/power/control Just One more question…which parms in Bios did you change? Or is above with default settings?
October 23, 20241 yr 1 hour ago, BarbaGrump said: Just One more question…which parms in Bios did you change? Or is above with default settings? I did turn on ASPM if it was an option, but that only covers 3 x PCIe buses, and the net effect was only allowing the NVME drives to reach L1: Here's the ASPM status: lspci -vv | awk '/ASPM/{print $0}' RS= | grep --color -P '(^[a-z0-9:.]+|ASPM )' 00:06.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x4 Controller #0 (rev 04) (prog-if 00 [Normal decode]) LnkCap: Port #5, Speed 16GT/s, Width x4, ASPM L1, Exit Latency L1 <16us LnkCtl: ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+ 00:06.2 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x4 Controller #2 (rev 04) (prog-if 00 [Normal decode]) LnkCap: Port #5, Speed 16GT/s, Width x4, ASPM L1, Exit Latency L1 <16us LnkCtl: ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+ 00:1c.0 PCI bridge: Intel Corporation Device 51bc (rev 01) (prog-if 00 [Normal decode]) LnkCap: Port #5, Speed 8GT/s, Width x2, ASPM L0s L1, Exit Latency L0s <1us, L1 <16us LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk+ 00:1d.0 PCI bridge: Intel Corporation Device 51b2 (rev 01) (prog-if 00 [Normal decode]) LnkCap: Port #11, Speed 8GT/s, Width x2, ASPM L0s L1, Exit Latency L0s <1us, L1 <16us LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk+ 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller S4LV008[Pascal] (prog-if 02 [NVM Express]) LnkCap: Port #0, Speed 16GT/s, Width x4, ASPM L1, Exit Latency L1 <64us LnkCtl: ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+ 02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller S4LV008[Pascal] (prog-if 02 [NVM Express]) LnkCap: Port #0, Speed 16GT/s, Width x4, ASPM L1, Exit Latency L1 <64us LnkCtl: ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+ 03:00.0 Ethernet controller: Aquantia Corp. AQC113C NBase-T/IEEE 802.3an Ethernet Controller [Marvell Scalable mGig] (rev 03) LnkCap: Port #0, Speed 8GT/s, Width x2, ASPM not supported LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk+ 04:00.0 SATA controller: ASMedia Technology Inc. ASM1166 Serial ATA Controller (rev 02) (prog-if 01 [AHCI 1.0]) LnkCap: Port #0, Speed 8GT/s, Width x2, ASPM L0s L1, Exit Latency L0s <4us, L1 <64us LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk+ The NVME drives I had are power hungry Samsung 990pro's, but they do support ASPM nicely, so the power saving from those is over 10W alone.. I also generally turn off the 'turbo' mode for the CPU, it doesn't make a difference to the idle power consumption, but it does stop it getting close to 90C if running a full iGPU/CPU immich machine learning session which maxes out the entire CPU.. it will hover around 70C-75C if I turn off turbo Edited October 23, 20241 yr by Snubbers
December 19, 20241 yr just wanted to say thanks for this workaround. I am using a new 424-MAX and not being able to boot was a showstopper. I do have longer term concerns, because I suspect future releases will overwrite the syslinux.cfg file... which is no good. I don't mind not getting the boot menu option, because in console I can type "slim" and up pops the menu. This is good.
December 26, 20241 yr Author On 12/20/2024 at 12:54 AM, bucky2076 said: just wanted to say thanks for this workaround. I am using a new 424-MAX and not being able to boot was a showstopper. I do have longer term concerns, because I suspect future releases will overwrite the syslinux.cfg file... which is no good. I don't mind not getting the boot menu option, because in console I can type "slim" and up pops the menu. This is good. Have done the Update from 6.12.13 to 6.12.14 and this fix is still working without issues. Hopefully they don´t change anything with the release of Unraid 7 in the Future.
December 28, 20241 yr On 12/27/2024 at 12:07 AM, Sascha147 said: Have done the Update from 6.12.13 to 6.12.14 and this fix is still working without issues. Hopefully they don´t change anything with the release of Unraid 7 in the Future. I am on unraid 7 rc2 and it works fine....
December 31, 20241 yr On 10/4/2024 at 9:28 PM, Piece said: I was able to get my F6-424 Max to auto boot straight into unraid by editing the first line in the /syslinux/syslinux.cfg to be: default Unraid OS This does however make it skip over the boot loader selection menu all together though, so i guess it might be slightly inconvenient if for whatever reason you were in a situation where you needed to boot into the GUI Mode or Safe Mode. You would have to go back into the usb and edit the line again. Im not really familiar with syslinux or bootloaders at all to know if there is any better work around at the moment though. I guess something about that bootloader menu it doesn't seem to like auto booting into it. what are using to edit the file ? running a F4424 pro and having the same issues , tried with notepad , wordpad and notepad ++ and it converts to word file not a cfg file , ?
December 31, 20241 yr Community Expert 12 minutes ago, vespersmurf said: what are using to edit the file ? running a F4424 pro and having the same issues , tried with notepad , wordpad and notepad ++ and it converts to word file not a cfg file , ? Any editor should be ok as it is a dos based file system. Extension would normally stay as ,cfg
January 1, 20251 yr cheers for the reply , i managed to change the file , but its not working for me , i seem to only be able to install the GUI version ,2nd option no matter how new installs i do, whether manual or 1 click , in the headless the 424 pro cannot find the usb , but when booting to GUI it finds it fine ?! also in the headless it returns to the main bios without any options for booting until i power cycle , i did have this running proxmox ,might to return to proxmox and run unraid in a vm ?
January 1, 20251 yr "waiting up to 30 sec for device with label UNRAID to come online ... usb 1-3: device descriptor read /64, error - 110 " then a whole load more errors
January 8, 20251 yr On 10/5/2024 at 3:21 PM, saber-raider said: I can confirm that this workaround works. Thank you so much for taking the time and effort to address this issue; I really appreciate it. I've also opened a ticket with TerraMaster support and made them aware of this thread and the workaround. Hopefully, a long-term solution will be found soon. I'm new to Unraid and was wondering if there's a risk that a future update could modify the first line in `/boot/syslinux/syslinux.cfg`, potentially preventing the system from automatically booting into the OS after an upgrade/reboot cycle? This workaround works indeed! Incredibly happy about it. I was already installing Truenas, but I think it's not suitable for my use case. One thing though, first I was trying to install the 7.0 RC1 without any luck. It was giving me a kernel panic error while booting. Hoping this won't happen when they release it. No problems with the latest 6.x version thankfully.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.