Slasheal

Sounds about what I've been trying to point you to twice.

Same error I had. Look where "/home/node/.n8n/config" is mapped. Likely on: /mnt/cache/appdata/n8n instead of: /mnt/user/appdata/n8n

Hello, I installed it using the official n8nio template. Updated the timezone to match my timezone. It wasn't starting, was loopbooting. I had this error: No encryption key found - Auto-generating and saving to: /home/node/.n8n/config Error: Command "start" not found. There was two issues: 1st I installed it in: /mnt/cache/appdata/n8n instead of: /mnt/user/appdata/n8n 2nd is the created folder had permissions issues on the n8n appdata folder. I fixed it with Unraid UI and re-installed the template. It worked. Then I got the warning "however you are either visiting this via an insecure URL, or using Safari." on the n8n UI. Click the n8n container icon and select Edit. Add N8N_SECURE_COOKIE variable. Set its value to false. Click Apply at the bottom of the page. The warning will disappear, and you will be able to log in and use n8n normally. Don't forget to turn it back to true it once the app is reverse-proxied.

Here's my notes to get it to work. Would however recommend to instead use: https://forums.unraid.net/topic/130542-support-kilrahdolibarr/

Were you able to fix it?

I run Unraid 7.0.1 and wanted to report that for my system, having "isolcpus=0-1" in the boot options caused the Sleep / WOL functions to stop working. The system was hanging on a WOL command, independently of the NIC. I had to uninstall all plugins, reset everything, and try to set things back one by one, resetting bios, and so on. Only took me 8H to figure out it was this simple cpu isolation configuration. It's unrelated to this plugin, but it's where the information will likely be the most useful. I don't remember adding that option recently, so it could be an update and hardware specific issues that makes it not compatible anymore. Either case, if it can save someone some headache... It's worth checking :).

Yes my issues are now solved. You need to edit the boot options. You can do it from the GUI and then reboot. You'll need to append it to whatever boot option you currently use. To check if your changes worked, run "ls usb -t" in the terminal and make sure it's seen as USB Storage and not UAS, like on the screenshots above.

I can't help you with swag unfortunately.

Sorry I can't put a screen capture but you need to go on the top right of your screen, right click on the configurator icon and mount the partitions. It will appear in osx and you'll be able to edit it. Google how to mount the partitions for open core configurator.

Was someone able to passhthrough a USB device with a speed, as displayed in the system report, above 480mbps ? I tried to passthrough USB SSD storage that's seen as 10Gbits by Unraid and by my Macbook, but drops to 480Mbits once plugged to the VM. Same issue with multiple storage devices (SSD, DAS, card readers).

I did another reinstallation and it worked this time. Haven't been able to gasp what was the issue.

I'm also stuck to that. Tried 4 installs with different CPU selected in case it was messing with the install. Changed the settings on docker, ran the docker, ran the VMs. Everytime I get the apple logo and back to boot picker. I get this on the VM's logs but I'm unable to tell if it's related :

It seems that it's a feature rather than an issue. However it begs the question : why weren't they making noise when I used the enclosure.

I however still have the issue where the drives are making noise every 3 secs. It isn't the case when plugged to my mac. Could it be unraid's drive settings ? Tried changing the spin down delay, ain't that. Each disk one by one make that "low tick" noise. If I remove a disk, I hear a tick less than what's on the video. 460898729_26785356184443556_179525599263136440_n.mp4

And it worked ! As you understood I was putting in the USB concentrator and not the bridge that was displayer per drive. Thanks a lot !

I'm not sure to understand your question about the IDs. When it actually worked I had 3 coherent disks names and one was named incoherently to the 3 others. I wanted to change it, stopped the array, removed the pool, and then it stopped displaying 4 disks. I tried formating the disks back on osx, then plugging it to unraid, shows one or two disks. Tried formating the disk to zfs, stopped the array, still sees only one disk with previous partitions that should have been wiped from the zfs formating. Weird. server-diagnostics-20240922-1905.zip

I figured out it should be : usb-storage.quirks=XXXX:XXXX:u and not usb_storage.quirks=XXXX:XXXX:u It really did seem to work, but after I tried recreating an the array, I'm back at facing the same issue than before... I really don't gasp what's going on here... Edit : I tried adding usb-storage.quirks=XXXX:XXXX:u and usb_storage.quirks=XXXX:XXXX:u, didn't worked. Is there a way to check if UAS is activated ? Screen Recording 2024-09-22 at 16.51.15.mov

Hello ! I had missed your message on that topic, I forgot that I had made two topics 🤦‍♂️ I replied yesterday. It's a good thing that I haven't spammed the other topic, as it was two different issues it seems... I surrendered on the data that was contained on those disks and wiped them. 🫤 Still, I can't use the DAS. Also what I noticed is that the disks are continously pooled and I hear noise from the reading heads every 3 secs. I formated the disks on my Macbook and it was not making any noises and was working as expected. I did what you described, added those arguments, please see the included pictures on the other post. It doesn't seem to solve the issue or to make any change. 🫤

I am updating this post again to point out the issue I found in Unraid 7 beta 2 (7.0.0-beta.2 2024-07-12). I wasn't able to trouble shoot my issues with my BTRFS array failing but I found out there's clearly something that isn't working on Unraid 7. 7 beta 1 and 2 sees only one drive : While they appear fine and separated on stable 6.12.13 : In both scenario I see : With 7 beta 2 and one disk out of the array using a SATA to usb adapter, then I see all my drives. My previous unrecoverable array is displayed as "array" and is greyed out, can't be mounted : Once I re-insert that drive in the DAS, I then see two 18TB drives. Remember, there's 4 drives being plugged. I'm joining the three diagnostics files. server-diagnostics-20240922-0029 (Beta 7 2 one drive removed and back in).zip server-diagnostics-20240922-0000 (Unraid 7 beta 2).zip server-diagnostics-20240922-0008 (Unraid 6.12.13).zip server-diagnostics-20240922-0008 (Unraid 6.12.13).zip

I used these drives with their USB enclosure for months without USB dropping, with two different USB Hubs. On the other hand, it was verry annoying to store these drives reliably and keep them from overheating. Also the fact that USB was dropping if you were touching those USB cables. So it's a known DAS common issue without any way around ? Bummer. Ubuntu sees those properly, even if Unraid isn't Debian based, I would have thought it's just a matter of driver, linux kernel version or so on. If there's no possible fix, unfortunately I'll have to send it back, but at least people wil be able to know that it does not work. EDIT 1 : I was using Unraid 7 beta 1, tried upgrading to Beta 2, without much change. I rolled back to last stable version... and voilà . My drives appear separate. Let's see if everything works. EDIT 2 : The drives works individually, but I still have to fix that BTRFS pool. Sep 15 20:17:11 Server unassigned.devices: Partition '3WHM5PXJ' cannot be mounted. Sep 15 20:18:52 Server unassigned.devices: Mounting partition 'sdd1' at mountpoint '/mnt/disks/3WHM5PXJ'... Sep 15 20:18:52 Server unassigned.devices: Mount cmd: /sbin/mount -t 'btrfs' -o rw,relatime,space_cache=v2 '/dev/sdd1' '/mnt/disks/3WHM5PXJ' Sep 15 20:18:52 Server kernel: BTRFS info (device sde1): first mount of filesystem cfb76aba-1473-4817-b54c-771e543e4bb4 Sep 15 20:18:52 Server kernel: BTRFS info (device sde1): using crc32c (crc32c-intel) checksum algorithm Sep 15 20:18:52 Server kernel: BTRFS error (device sde1): unrecognized or unsupported super flag: 34359738368 Sep 15 20:18:52 Server kernel: BTRFS error (device sde1): dev_item UUID does not match metadata fsid: cfb76aba-1473-4817-b54c-771e543e4bb4 != ea800352-ab41-4e21-ab0b-827ff85e9fc2 Sep 15 20:18:52 Server kernel: BTRFS error (device sde1): superblock contains fatal errors Sep 15 20:18:52 Server kernel: BTRFS error (device sde1): open_ctree failed Sep 15 20:18:52 Server unassigned.devices: Mount of 'sdd1' failed: 'mount: /mnt/disks/3WHM5PXJ: wrong fs type, bad option, bad superblock on /dev/sdd1, missing codepage or helper program, or other error. dmesg(1) may have more information after failed mount system call.' Sep 15 20:18:52 Server unassigned.devices: Partition '3WHM5PXJ' cannot be mounted. When trying to mount it manually : "sudo mount -t btrfs /dev/sde /mnt/disks/WDC_WD180EDFZ-11AFWA0_3WG58XLL" [ 1396.340256] BTRFS info (device sde1): first mount of filesystem cfb76aba-1473-4817-b54c-771e543e4bb4 [ 1396.340269] BTRFS info (device sde1): using crc32c (crc32c-intel) checksum algorithm [ 1396.340272] BTRFS error (device sde1): unrecognized or unsupported super flag: 34359738368 [ 1396.340273] BTRFS error (device sde1): dev_item UUID does not match metadata fsid: cfb76aba-1473-4817-b54c-771e543e4bb4 != ea800352-ab41-4e21-ab0b-827ff85e9fc2 [ 1396.340274] BTRFS error (device sde1): superblock contains fatal errors [ 1396.340290] BTRFS error (device sde1): open_ctree failed When I tried to fix the FSID. In anycase, the enclosure doesn't seem to be at fault. Most likely it's due to the fact that I removed the USB to SATA contrôler. Once I manage to get this fixed, I'll make another post to tell people if the enclosure does work. In the meanwhile, I'll try to get support to not loose the data on these drives.

Hello guys. I've been always using Unraid with external hard drive and low power computers. These last months I've been using it with a Thinkcentre and (Intel 12th gen) and 2 WD MyBook 18TB drives as well as a 2TB SSD. The goal of having a DAS is to reduce the footprint and the possible risks of touching a USB cable. I'm repporting my findings and issues with the new Orico 99 Series DAS. Long story short : I seem to face two issues : one is the disks not being displayed individually on unraid. I see only one disk no matter what. The second issue, is my BTRFS pool being broken, probably because I now don't use the SATA to USB adapters that were with those external drives. On Ubuntu, it seems that XFS drives works OK, but unraid still don't see them individually. If the issue with the BTRFS pool isn't solvable easily, I could totally use the USB to SATA adapters and transfer the data to other drives. However, it doesn't solve the issues with all drives being seen as one. On the other hand, Ubuntu sees 4 drives... I'll appreciate if you can help me solve these issues. ________________________________________________________________________________________________ I bought the new Orico 99 Series DAS as I found it at an amazing price on Ebay (135$). This enclosure is equiped with a Usb 3.2 gen 2 10gbits (1.25GB/s) USB interface that even offers to be daisy chained. Great ! Since those drives can push up to 220MB/s and 180MB/s continuous, it seems like a good way to avoid any kind of throttling due to USB 3.0 (700MB/s) max speed. I also wanted to see if those newer USB chipsets can be used reliably with unraid, which would be awesome. I was also able to... save some space in my bags while moving in the US for work ! I just chucked the hard drives and installed them in the DAS. The issue I have now have is Unraid seeing only one drive out of the 4 drives : I tried pulling out drives one by one. What I observed is that no matter which drive is plugged, I always see that exact serial number and Unraid only sees one drive. Maybe the USB controller doesn't expose the disks properly so Unraid only sees the same duplicated part of the serial number. 2 of the drives were XFS and previously used as the main array, but these has been discarded and unused since months. The 2 drives I would like to work, are BTRFS and were used in the MEDIA array, these somehow can however not be mounted. There was no raid, it was just two drives making up a 36TB pool. I'm guessing they were using the MIXED profile. https://wiki.tnonline.net/w/Btrfs/Profiles Regarding my main array, it now only consists of what was previously my cache drive : a 2TB SSD. I store here my dockers, nextcloud, with all my important data. These two 18TB drives are used to store videos, and as backup drives for my important data. These informations are also duplicated to the MEDIA array as well as to an 2.5" external USB drive with a cron task. So I basically ensure to always have a copy even if the drives and the SSD fails. Anyway. I also have a SATA to USB adapter, and would love to try it out to see if the drive is always labelled with the same UUID. I will need to get a 12VDC PSU at work to power it. I will do that monday's evening. If the disks aren't labeled the same, then it could be a firmware bug from Orico. But right now I'm guessing that it's due to the fact that I got rid of those SATA to USB adapters that were with the original drive from WD. Will update the post with the info on monday. Here's what I have been trying : So I tried changing UUID with the Unassigned Disks Pluggin. Wasn't working. In the log I could see : I checked on the main page and the disk currently inserted was indeed sdb1. So I tried mounting the disks manually and I got : I'll go on and try to repair this BTRFS file system. I'll update this post with how things are going. sudo mount -t btrfs /dev/sda1 /mnt/disks/WDC_WD18 When trying to manually mount : Sep 15 03:29:02 Server unassigned.devices: Mount of 'sdb1' failed: 'mount: /mnt/disks/3WHM5PXJ: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error. dmesg(1) may have more information after failed mount system call.' Sep 15 03:29:02 Server unassigned.devices: Partition '3WHM5PXJ' cannot be mounted. Sep 15 03:29:02 Server unassigned.devices: Mounting partition 'sdc1' at mountpoint '/mnt/disks/WDC_WD18_1'... Sep 15 03:29:02 Server unassigned.devices: Mount cmd: /sbin/mount -t 'btrfs' -o rw,relatime,space_cache=v2 '/dev/sdc1' '/mnt/disks/WDC_WD18_1' Sep 15 03:29:02 Server kernel: BTRFS info (device sdc1): first mount of filesystem cfb76aba-1473-4817-b54c-771e543e4bb4 Sep 15 03:29:02 Server kernel: BTRFS info (device sdc1): using crc32c (crc32c-intel) checksum algorithm Sep 15 03:29:02 Server kernel: BTRFS error (device sdc1): unrecognized or unsupported super flag: 34359738368 Sep 15 03:29:02 Server kernel: BTRFS error (device sdc1): dev_item UUID does not match metadata fsid: cfb76aba-1473-4817-b54c-771e543e4bb4 != ea800352-ab41-4e21-ab0b-827ff85e9fc2 Sep 15 03:29:02 Server kernel: BTRFS error (device sdc1): superblock contains fatal errors Sep 15 03:29:02 Server kernel: BTRFS error (device sdc1): open_ctree failed Sep 15 03:29:03 Server unassigned.devices: Mount of 'sdc1' failed: 'mount: /mnt/disks/WDC_WD18_1: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error. dmesg(1) may have more information after failed mount system call.' Then with dmesg : [ 6724.096404] md: import_slot: 29 empty [ 6731.264966] usb 1-5: USB disconnect, device number 3 [ 6735.262403] usb 1-2: USB disconnect, device number 2 [ 6745.586554] usb 1-4: new high-speed USB device number 11 using xhci_hcd [ 6745.719398] hub 1-4:1.0: USB hub found [ 6745.719656] hub 1-4:1.0: 4 ports detected [ 6745.844639] usb 2-10: new SuperSpeed USB device number 16 using xhci_hcd [ 6745.889192] hub 2-10:1.0: USB hub found [ 6745.889439] hub 2-10:1.0: 4 ports detected [ 6746.433602] usb 1-4.3: new high-speed USB device number 12 using xhci_hcd [ 6746.577838] hub 1-4.3:1.0: USB hub found [ 6746.578099] hub 1-4.3:1.0: 4 ports detected [ 6746.641077] usb 2-10.3: new SuperSpeed USB device number 17 using xhci_hcd [ 6746.744225] hub 2-10.3:1.0: USB hub found [ 6746.744774] hub 2-10.3:1.0: 4 ports detected [ 6747.305625] usb 1-4.3.1: new high-speed USB device number 13 using xhci_hcd [ 6747.458915] scsi host1: uas [ 6747.459870] scsi 1:0:0:0: Direct-Access WDC WD18 0EDFZ-11AFWA 81.0 PQ: 0 ANSI: 6 [ 6747.463469] sd 1:0:0:0: Attached scsi generic sg1 type 0 [ 6747.536588] sd 1:0:0:0: [sdb] 35156656128 512-byte logical blocks: (18.0 TB/16.4 TiB) [ 6747.536591] sd 1:0:0:0: [sdb] 4096-byte physical blocks [ 6747.536820] sd 1:0:0:0: [sdb] Write Protect is off [ 6747.536821] sd 1:0:0:0: [sdb] Mode Sense: 2f 00 00 00 [ 6747.537319] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 6747.537419] sd 1:0:0:0: [sdb] Preferred minimum I/O size 4096 bytes [ 6747.537420] sd 1:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes) [ 6747.585446] usb 1-4.3.2: new high-speed USB device number 14 using xhci_hcd [ 6747.736764] scsi host7: uas [ 6747.737639] scsi 7:0:0:0: Direct-Access WDC WD18 0EDFZ-11AFWA 81.0 PQ: 0 ANSI: 6 [ 6747.744718] sd 7:0:0:0: Attached scsi generic sg2 type 0 [ 6749.605737] sdb: sdb1 [ 6749.605968] sd 1:0:0:0: [sdb] Attached SCSI disk [ 6749.812148] sd 7:0:0:0: [sdc] 35156656128 512-byte logical blocks: (18.0 TB/16.4 TiB) [ 6749.812151] sd 7:0:0:0: [sdc] 4096-byte physical blocks [ 6749.812355] sd 7:0:0:0: [sdc] Write Protect is off [ 6749.812356] sd 7:0:0:0: [sdc] Mode Sense: 2f 00 00 00 [ 6749.812766] sd 7:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 6749.812874] sd 7:0:0:0: [sdc] Preferred minimum I/O size 4096 bytes [ 6749.812876] sd 7:0:0:0: [sdc] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes) [ 6749.982039] sdc: sdc1 [ 6749.982246] sd 7:0:0:0: [sdc] Attached SCSI disk [ 6751.317191] md: unRAID driver removed [ 6751.359068] md: unRAID driver 2.9.31 installed [ 6751.361928] mdcmd (1): import 0 [ 6751.361932] md: import_slot: 0 empty [ 6751.409650] mdcmd (2): import 1 nvme0n1 2048 1953513560 0 Force_MP600_214082410FF12885000D [ 6751.409658] md: import disk1: (nvme0n1) Force_MP600_214082410FF12885000D size: 1953513560 [ 6751.409667] mdcmd (3): import 2 [ 6751.409673] mdcmd (4): import 3 [ 6751.409678] mdcmd (5): import 4 [ 6751.409683] mdcmd (6): import 5 [ 6751.409688] mdcmd (7): import 6 [ 6751.409693] mdcmd (8): import 7 [ 6751.409697] mdcmd (9): import 8 [ 6751.409702] mdcmd (10): import 9 [ 6751.409707] mdcmd (11): import 10 [ 6751.409711] mdcmd (12): import 11 [ 6751.409715] mdcmd (13): import 12 [ 6751.409720] mdcmd (14): import 13 [ 6751.409725] mdcmd (15): import 14 [ 6751.409729] mdcmd (16): import 15 [ 6751.409733] mdcmd (17): import 16 [ 6751.409738] mdcmd (18): import 17 [ 6751.409742] mdcmd (19): import 18 [ 6751.409746] mdcmd (20): import 19 [ 6751.409751] mdcmd (21): import 20 [ 6751.409755] mdcmd (22): import 21 [ 6751.409759] mdcmd (23): import 22 [ 6751.409764] mdcmd (24): import 23 [ 6751.409768] mdcmd (25): import 24 [ 6751.409772] mdcmd (26): import 25 [ 6751.409776] mdcmd (27): import 26 [ 6751.409781] mdcmd (28): import 27 [ 6751.409785] mdcmd (29): import 28 [ 6751.409788] mdcmd (30): import 29 [ 6751.409789] md: import_slot: 29 empty [ 6805.758774] BTRFS info (device sdc1): first mount of filesystem cfb76aba-1473-4817-b54c-771e543e4bb4 [ 6805.758805] BTRFS info (device sdc1): using crc32c (crc32c-intel) checksum algorithm [ 6805.758810] BTRFS error (device sdc1): unrecognized or unsupported super flag: 34359738368 [ 6805.758811] BTRFS error (device sdc1): dev_item UUID does not match metadata fsid: cfb76aba-1473-4817-b54c-771e543e4bb4 != ea800352-ab41-4e21-ab0b-827ff85e9fc2 [ 6805.758812] BTRFS error (device sdc1): superblock contains fatal errors [ 6805.761725] BTRFS error (device sdc1): open_ctree failed [ 6810.607842] BTRFS info (device sdc1): first mount of filesystem cfb76aba-1473-4817-b54c-771e543e4bb4 [ 6810.607872] BTRFS info (device sdc1): using crc32c (crc32c-intel) checksum algorithm [ 6810.607876] BTRFS error (device sdc1): unrecognized or unsupported super flag: 34359738368 [ 6810.607878] BTRFS error (device sdc1): dev_item UUID does not match metadata fsid: cfb76aba-1473-4817-b54c-771e543e4bb4 != ea800352-ab41-4e21-ab0b-827ff85e9fc2 [ 6810.607879] BTRFS error (device sdc1): superblock contains fatal errors [ 6810.609516] BTRFS error (device sdc1): open_ctree failed [ 6827.031479] BTRFS info (device sdc1): first mount of filesystem cfb76aba-1473-4817-b54c-771e543e4bb4 [ 6827.031509] BTRFS info (device sdc1): using crc32c (crc32c-intel) checksum algorithm [ 6827.031516] BTRFS error (device sdc1): unrecognized or unsupported super flag: 34359738368 [ 6827.031517] BTRFS error (device sdc1): dev_item UUID does not match metadata fsid: cfb76aba-1473-4817-b54c-771e543e4bb4 != ea800352-ab41-4e21-ab0b-827ff85e9fc2 [ 6827.031519] BTRFS error (device sdc1): superblock contains fatal errors [ 6827.031717] BTRFS error (device sdc1): open_ctree failed [ 6827.951552] BTRFS info (device sdc1): first mount of filesystem cfb76aba-1473-4817-b54c-771e543e4bb4 [ 6827.951583] BTRFS info (device sdc1): using crc32c (crc32c-intel) checksum algorithm [ 6827.951590] BTRFS error (device sdc1): unrecognized or unsupported super flag: 34359738368 [ 6827.951591] BTRFS error (device sdc1): dev_item UUID does not match metadata fsid: cfb76aba-1473-4817-b54c-771e543e4bb4 != ea800352-ab41-4e21-ab0b-827ff85e9fc2 [ 6827.951593] BTRFS error (device sdc1): superblock contains fatal errors [ 6827.953617] BTRFS error (device sdc1): open_ctree failed [ 6997.478213] block nvme0n1: the capability attribute has been deprecated. [ 7108.370644] BTRFS info (device sdc1): first mount of filesystem cfb76aba-1473-4817-b54c-771e543e4bb4 [ 7108.370657] BTRFS info (device sdc1): using crc32c (crc32c-intel) checksum algorithm [ 7108.370660] BTRFS error (device sdc1): unrecognized or unsupported super flag: 34359738368 [ 7108.370661] BTRFS error (device sdc1): dev_item UUID does not match metadata fsid: cfb76aba-1473-4817-b54c-771e543e4bb4 != ea800352-ab41-4e21-ab0b-827ff85e9fc2 [ 7108.370663] BTRFS error (device sdc1): superblock contains fatal errors [ 7108.370878] BTRFS error (device sdc1): open_ctree failed server-diagnostics-20240914-2131.zip Tried BTRFS repair : When trying repair I get "superblock checksum matches but it has invalid members" I'm clueless on how to fix it. Maybe it's just a matter of pointing out that the other drive is in the btrfs pool as well ? Ubuntu sees the pair of disks as having the same UUID. On the other hand, previous XFS disks UUID are OK. When 4 drives are plugged, I see 4 drives. I tried "echo 1 > /sys/block/sdb/device/delete" and "echo 1 > /sys/block/sdb/device/delete". without any luck.

I had the same issue and it was basically working on first install, then causing issue everytime the docker is restarted, eating all my ram and causing a server crash. I have 16GB of ram, 8 available. Best advice I can get is to throttle the RAM consumption in the docker setting and enable swap memory. Also, unistall the docker and reinstall it configured to use little to no memory. With these configured, I was able to fix my configuration. And yes, 4GB DDR3 isn't enough really, but I gave it 2GB of RAM and it has access to swap. Works well now.

This fixed the VM not booting. However I was attempting to do some nested virtualisation and it's just not possible.

The irony at me having the same issue months later and searching again until I find my message.