Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Issue with setting up internal boot in OS7.3.2

Featured Replies

I have an issue with Unraid OS 7.3.2 when I update my Lincstation N2 to several days ago. Liking the idea of being able to boot from internal drives istead of a USB stick drive. So I set the internal boot to work and when it finally stopped, I was informed that the drive I had chosen for the internal boot was "Unmountable: unsupprotable no filesystem. I was also inform that there was an Unassigned Device, which contained Dev1 DUTB42-0x60c35e18 - 125GB (mmcblk0) . In the Array Operation (with array started) It informs that there is an "Unmoutable disk present" and underneath the following, Boot KODAK_SSD_1TB_E332MX14300149(nvme1n1.

I have tried reverting to the Previous OS and following the setup given in a youtube video Space Invader1, I stll getthe same results.

What am I doing wrong. I have tried reformating the problem drive, no change butvall I get is more of the same. Any Idea's would be appreciated.

unraid-7.3.2.txt domain.cfg bootpool.cfg pooled.cfg boot.cfg docker.cfg zfs.conf savedpcidata.json editor.cfg super.dat ident.cfg pci_diffs.json network-extra.cfg network.cfg go.txt disk.cfg listen.txt SOLIDIGM_SSDPFKKW020X7_SDC7N458710307D1H-2026-05-27 pooled (nvme0).txt KINGSTON_SNV3S2000G_50026B738398DE87-2026-05-27 pooled3 (nvme2).txt eui.00000000000000000026b738398de875-2026-05-27 pooled3 (nvme2).txt eui.aca32f037500b45d2ee4ac0000000001-2026-05-27 pooled (nvme0).txt CT2000BX500SSD1_2442E98F405D-2026-05-27 pooled2 (sdc).txt KODAK_SSD_X350_1TB_E332MX14300149-2026-05-27 boot (nvme1).txt nvme.126f-453333324d583134333030313439-4b4f44414b20535344205833353020315442-00000001-2026-05-27 boot (nvme1).txt Samsung_SSD_870_QVO_8TB_S5SSNF0W518704K-2026-05-27 pooled4 (sdb).txt SanDisk_Ultra_Fit_050122f234b93a78b82b093a8b4de9d85d23b5714b2b981068c31f373d795819981100000000000000000000971465f3ff101210835581078a276a12-0-0-2026-05-27 flash (sda).txt cmdline.txt btrfs-usage.txt drm.txt plugins.txt motherboard.txt iommu_groups.txt ntp.txt aspm-status.txt ethtool.txt folders.txt sshd.txt lsmod.txt lsscsi.txt loads.txt testparm.txt memory.txt lspci.txt meminfo.txt lsusb.txt urls.txt top.txt servers.conf.txt vars.txt lscpu.txt lsof.txt df.txt ifconfig.txt dhcplog.txt graphql-api.txt syslog-previous.txt syslog.txt appdata.cfg system.cfg shareDisks.txt P--------m.cfg

  • Community Expert

The diags are generated as a single zip file, please attach that instead.

  • Community Expert
6 hours ago, JorgeB said:

The diags are generated as a single zip file, please attach that instead.

You really need to figure this out to get any help. Nobody is going to bother to download all those individual files.

Perhaps your Mac is automatically unzipping the single Diagnostics ZIP file to a folder, and then you are trying to attach the folder.

Go to wherever files are downloaded and find the single Diagnostics ZIP file and attach that single ZIP file to your NEXT post in this thread.

  • Author

Please find attached zip file tower-diagnostic-20260805-1109.zip, as requested. I must apologise as I have never zipped previously on my MacBook Pro.tower-diagnostics-20260805-1109.zip

  • Community Expert

Diags show that you are currently booting from a flash drive, and have two pools, which I assume you tried to create as boot pools: boot and bootpool. If this is correct, click on those pools and then "remove pool", then rerun the wizard to create the boot pool and make sure you boot from the new internal boot pool device after rebooting.

  • Author

Thank you for the pointer.

I've removed all the pools, but I have an issue. I have 6 drive slots on my Lincstation N2 and the MAIN page is showing that there are 7 unassigned device. I think that the unassigned device that is out of place is 'Device 5' and titled 'DUTB42_0x60c35e18 - 125 GB (mmcblk0)'. When looked up on the internet and I am informed that this is part of the Unraid Boot up Software. How do I remove DUTB42, which I would like to do before I start re-assigning devices to slots.

I have re-formated Dev 7 (KODAK_SSD_X350_1TB_E332MX14300149 - 1 TB (nvme2n1)) to Fat32 using a M.2 to USB3.1 enclosure and the NVME device now shows a total capacity of 1 TB.

I have inserted (SAMSUNG_MZVLB256HAHQ-000H1_S425NE1M518910 - 256 GB (nvme3n1), shown as Dev 4, with the intention of using as the internal boot device.

tower-diagnostics-20260808-1421.zip

  • Community Expert

mmcblk is the internal eMMC storage/boot likely provided by lincstation.

  • Community Expert

The eMMC should not count for licensing; you can use it or not.

  • Author

How do I remove it? if that is possible

  • Community Expert

It's soldered onto the board, it cannot be removed, AFAIK.

  • Community Expert
On 8/8/2026 at 10:01 AM, Steve731 said:

re-formated Dev 7 (KODAK_SSD_X350_1TB_E332MX14300149 - 1 TB (nvme2n1)) to Fat32

You don't want to use FAT32 for an assigned disk.

  • Community Expert

Yeah you dont manually format any disks, unraid handles this for you.

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.