Everything posted by Steve731
-
Issue with setting up internal boot in OS7.3.2
How do I remove it? if that is possible
-
Issue with setting up internal boot in OS7.3.2
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
-
Issue with setting up internal boot in OS7.3.2
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
-
Issue with setting up internal boot in OS7.3.2
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
-
7.3.2 update and server locking up
I justvdragged the file to the attachment window and they just opened. I thought I was dragging a zipper file across from the diagnosic folder on my Mac book pro
-
7.3.2 update and server locking up
Found it 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
-
7.3.2 update and server locking up
Being a relative newby to Unraid, I am unsure how obtain a "Diagnostics ZIP". I would appreciate pointer in this matter.
-
7.3.2 update and server locking up
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.