Hi all,
I'm testing UnRaid and trying out several options and settings.
Currently there are no important data on the system, I just did full memory check and disk stress test.
Seems I've messed something up with one of my nvme drives that I want to use as pool.
Both should be xfs formatted as I won't use pool raid, so that's fine for my usage.
This one pool disk shows up as "Ummountable: Wrong or no file system"
Done so far:
used the Unassigned Devices tool to remove all partitions
added the drive as 2nd pool
set file system to xfs in the pool
formatted the disk
Result still the same.
Now I see an issue in the disk log:
Apr 9 00:25:12 Tower root: mount: /mnt/c-nvme0n1x: special device /dev/nvme0n1p1 does not exist.
Apr 9 00:25:12 Tower emhttpd: /mnt/c-nvme0n1x mount error: Wrong or no file system
So I've checked with lsblk and see some weird entries for nvme0n1
root@Tower:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
...
nvme0n1 259:0 0 465.8G 0 disk
└─nvme0n1p3 259:3 0 464.8G 0 part
├─pve-swap 254:0 0 8G 0 lvm
├─pve-root 254:1 0 96G 0 lvm
├─pve-data_tmeta 254:2 0 3.4G 0 lvm
│ └─pve-data 254:4 0 337.9G 0 lvm
└─pve-data_tdata 254:3 0 337.9G 0 lvm
└─pve-data 254:4 0 337.9G 0 lvm
nvme1n1 259:4 0 465.8G 0 disk
└─nvme1n1p1 259:5 0 465.8G 0 part /mnt/c-nvme1n1x
There is a "p3" mount point with some strange additional entries.
I guess these are leftovers from the previous usage of this system, so UnRaid created them on first startup.
The "p1" entry is missing, so creating the filesystem fails,
Don't ask me how I managed to remove this (at least I didn't do it from shell, just used the standard unRaid options)
What's the best way to clean up this mess?
Probably get rid of the "p3" entries, so they don't cause later issues
Create a proper "p1" entry.
Is there a tool, that re-scans this device and creates all proper entries?
Or do I have to come up with some shell commands?
Thanks for your help and Happy Easter