January 1, 20251 yr Happy new year! I'm running into an issue where my cache pool disks show an "Unmountable: wrong or no file system" error. I recently upgraded to v7 and had to do some weird things around upgrading my Unraid USB drive, so I think maybe this issue started around then. I found some other threads that recommend formatting the drives, but when I try to use the GUI option to do so, I run into an issue where an update.htm page opens and does nothing. I've also tried doing this in safe mode, but I see the same error. I'm very new to Unraid, so I'd appreciate any help where I can fix my cache drives! hermes-diagnostics-20250101-0944.zip
January 3, 20251 yr Author Thanks for stepping in, @JorgeB! Let me know what else you need! root@hermes:~# blkid /dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="1D01-2F2C" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="bbefcdff-01" /dev/md1p1: UUID="406772b4-fa39-4876-996c-bfae653df0dc" BLOCK_SIZE="512" TYPE="xfs" /dev/loop1: BLOCK_SIZE="131072" TYPE="squashfs" /dev/loop2: UUID="7da88bde-0100-400f-ae26-c3ac1329954e" UUID_SUB="27991eeb-41a4-4e25-a021-66a3b170f812" BLOCK_SIZE="4096" TYPE="btrfs" /dev/loop0: BLOCK_SIZE="131072" TYPE="squashfs"
January 3, 20251 yr Community Expert It's not showing any filesystem on the pool devices, post the output from: fdisk -l /dev/nvme0n1 and fdisk -l /dev/nvme1n1
January 3, 20251 yr Author Here you go: root@hermes:~# fdisk -l /dev/nvme0n1 Disk /dev/nvme0n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: Samsung SSD 990 EVO 1TB Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes root@hermes:~# fdisk -l /dev/nvme1n1 Disk /dev/nvme1n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: Samsung SSD 990 EVO 1TB Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes
January 3, 20251 yr Community Expert Both devices don't even have a partition, try typing: sfdisk /dev/nvme0n1 then type 2048 and hit Enter, post the output from that.
January 3, 20251 yr Author Here are the outputs. I didn't know what to do after typing in "2048" so I typed it in again, which didn't seem like it did anything: root@hermes:~# sfdisk /dev/nvme0n1 Welcome to sfdisk (util-linux 2.40.2). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Checking that no-one is using this disk right now ... OK Disk /dev/nvme0n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: Samsung SSD 990 EVO 1TB Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes sfdisk is going to create a new 'dos' disk label. Use 'label: <name>' before you define a first partition to override the default. Type 'help' to get more information. >>> 2048 Created a new DOS (MBR) disklabel with disk identifier 0x6c739437. Created a new partition 1 of type 'Linux' and of size 931.5 GiB. /dev/nvme0n1p1 : 2048 1953525167 (931.5G) Linux /dev/nvme0n1p2: /dev/nvme0n1p2: 2048 All space for primary partitions is in use. Failed to add #2 partition: Invalid argument /dev/nvme0n1p2:
January 4, 20251 yr Community Expert 13 hours ago, hhhbbb said: I didn't know what to do after typing in "2048" Don't type anything, but now hit CTRL + C to abort and retry but with 64, post output again.
January 4, 20251 yr Author I hope I understood you correctly, but I ran sfdisk with 64 instead of 2048. It still leaves me with the terminal referencing the second drive: root@hermes:~# sfdisk /dev/nvme0n1 Welcome to sfdisk (util-linux 2.40.2). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Checking that no-one is using this disk right now ... OK Disk /dev/nvme0n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: Samsung SSD 990 EVO 1TB Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes sfdisk is going to create a new 'dos' disk label. Use 'label: <name>' before you define a first partition to override the default. Type 'help' to get more information. >>> 64 Created a new DOS (MBR) disklabel with disk identifier 0x2672af10. Created a new partition 1 of type 'Linux' and of size 931.5 GiB. /dev/nvme0n1p1 : 64 1953525167 (931.5G) Linux /dev/nvme0n1p2: /dev/nvme0n1p2: /dev/nvme0n1p2:
January 5, 20251 yr Community Expert This was just to see if a filesystem signature was detected on the device, like if it has been wiped with wipefs, but no signature is being detected, with both possible starting sectors that Unraid uses, meaning either the device was completely wiped with a full device trim, or it had an issue, try the other NMVe device, with both 2048 and 64 and also post the results, but will likely be the same.
January 5, 20251 yr Author Here are the outputs of the other drive, definitely looks similar: root@hermes:~# sfdisk /dev/nvme1n1 Welcome to sfdisk (util-linux 2.40.2). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Checking that no-one is using this disk right now ... OK Disk /dev/nvme1n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: Samsung SSD 990 EVO 1TB Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes sfdisk is going to create a new 'dos' disk label. Use 'label: <name>' before you define a first partition to override the default. Type 'help' to get more information. >>> 2048 Created a new DOS (MBR) disklabel with disk identifier 0x6870c7e2. Created a new partition 1 of type 'Linux' and of size 931.5 GiB. /dev/nvme1n1p1 : 2048 1953525167 (931.5G) Linux /dev/nvme1n1p2: /dev/nvme1n1p2: /dev/nvme1n1p2: /dev/nvme1n1p2: ^C root@hermes:~# sfdisk /dev/nvme1n1 Welcome to sfdisk (util-linux 2.40.2). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Checking that no-one is using this disk right now ... OK Disk /dev/nvme1n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: Samsung SSD 990 EVO 1TB Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes sfdisk is going to create a new 'dos' disk label. Use 'label: <name>' before you define a first partition to override the default. Type 'help' to get more information. >>> 64 Created a new DOS (MBR) disklabel with disk identifier 0xc6f40941. Created a new partition 1 of type 'Linux' and of size 931.5 GiB. /dev/nvme1n1p1 : 64 1953525167 (931.5G) Linux /dev/nvme1n1p2: /dev/nvme1n1p2: /dev/nvme1n1p2: ^C
January 5, 20251 yr Author If the devices are wiped, do you have any advice for figuring out how to reformat the drives and add them to the cache pool? When I try to format them through the Unraid UI, it just opens up an empty update.htm page which does nothing. I see these "missing csrf_token" entries in the logs when that page opens, even in safe mode: Jan 3 09:43:13 hermes kernel: pts pts0: sig=22, tty->pgrp == NULL! Jan 5 13:19:17 hermes emhttpd: error: cmdFormat: missing csrf_token Jan 5 13:19:57 hermes emhttpd: error: cmdFormat: missing csrf_token
January 6, 20251 yr Community Expert 12 hours ago, hhhbbb said: cmdFormat: missing csrf_token This should never happen, try booting in safe mode or using a different browser.
January 6, 20251 yr Author Unfortunately, I tried booting in safe mode and ran into the same blank update.htm and same "missing csrf_token" error message. While in safe mode, I did this with both Chrome and Firefox. Here are the most recent logs from that session: Jan 6 09:50:03 hermes kernel: mdcmd (31): set md_num_stripes 1280 Jan 6 09:50:03 hermes kernel: mdcmd (32): set md_queue_limit 80 Jan 6 09:50:03 hermes kernel: mdcmd (33): set md_sync_limit 5 Jan 6 09:50:03 hermes kernel: mdcmd (34): set md_write_method Jan 6 09:50:03 hermes kernel: mdcmd (35): start STOPPED Jan 6 09:50:03 hermes kernel: unraid: allocating 15750K for 1280 stripes (3 disks) Jan 6 09:50:03 hermes kernel: md1p1: running, size: 7814026532 blocks Jan 6 09:50:03 hermes emhttpd: shcmd (80): udevadm settle Jan 6 09:50:03 hermes emhttpd: import 30 pool device: (nvme1n1) Samsung_SSD_990_EVO_1TB_S7M3NL0X925096B Jan 6 09:50:03 hermes emhttpd: import 31 pool device: (nvme0n1) Samsung_SSD_990_EVO_1TB_S7M3NL0X925063F Jan 6 09:50:03 hermes emhttpd: cache: recover volume Jan 6 09:50:03 hermes emhttpd: /sbin/blkid /dev/nvme1n1p1 2>&1 Jan 6 09:50:03 hermes emhttpd: /sbin/blkid /dev/nvme0n1p1 2>&1 Jan 6 09:50:03 hermes emhttpd: update_pool_cfg: 30 cache 0 Jan 6 09:50:03 hermes emhttpd: /sbin/blkid /dev/sda1 2>&1 Jan 6 09:50:03 hermes emhttpd: /dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="1D01-2F2C" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="bbefcdff-01" Jan 6 09:50:03 hermes emhttpd: import 32 flash device: (sda) Jan 6 09:50:03 hermes emhttpd: update_pool_cfg: 30 cache 0 Jan 6 09:50:03 hermes SysDriversBuild: Submitting SysDrivers Build Jan 6 09:50:03 hermes emhttpd: shcmd (85): touch /boot/config/forcesync Jan 6 09:50:03 hermes sysDrivers: SysDrivers Build Starting Jan 6 09:50:04 hermes emhttpd: Mounting disks... Jan 6 09:50:04 hermes emhttpd: mounting /mnt/disk1 Jan 6 09:50:04 hermes emhttpd: shcmd (86): mkdir -m 0666 -p /mnt/disk1 Jan 6 09:50:04 hermes emhttpd: /sbin/blkid /dev/md1p1 2>&1 Jan 6 09:50:04 hermes emhttpd: /dev/md1p1: UUID="406772b4-fa39-4876-996c-bfae653df0dc" BLOCK_SIZE="512" TYPE="xfs" Jan 6 09:50:04 hermes emhttpd: shcmd (87): mount -t xfs -o noatime,nouuid /dev/md1p1 /mnt/disk1 Jan 6 09:50:04 hermes kernel: XFS (md1p1): Mounting V5 Filesystem 406772b4-fa39-4876-996c-bfae653df0dc Jan 6 09:50:04 hermes kernel: XFS (md1p1): Ending clean mount Jan 6 09:50:04 hermes emhttpd: shcmd (88): xfs_growfs /mnt/disk1 Jan 6 09:50:04 hermes root: meta-data=/dev/md1p1 isize=512 agcount=8, agsize=268435455 blks Jan 6 09:50:04 hermes root: = sectsz=512 attr=2, projid32bit=1 Jan 6 09:50:04 hermes root: = crc=1 finobt=1, sparse=1, rmapbt=0 Jan 6 09:50:04 hermes root: = reflink=1 bigtime=1 inobtcount=1 nrext64=0 Jan 6 09:50:04 hermes root: = exchange=0 Jan 6 09:50:04 hermes root: data = bsize=4096 blocks=1953506633, imaxpct=5 Jan 6 09:50:04 hermes root: = sunit=0 swidth=0 blks Jan 6 09:50:04 hermes root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1, parent=0 Jan 6 09:50:04 hermes root: log =internal log bsize=4096 blocks=521728, version=2 Jan 6 09:50:04 hermes root: = sectsz=512 sunit=0 blks, lazy-count=1 Jan 6 09:50:04 hermes root: realtime =none extsz=4096 blocks=0, rtextents=0 Jan 6 09:50:04 hermes emhttpd: mounting /mnt/cache Jan 6 09:50:04 hermes emhttpd: shcmd (89): mkdir -m 0666 -p /mnt/cache Jan 6 09:50:04 hermes emhttpd: shcmd (90): rmdir /mnt/cache Jan 6 09:50:04 hermes emhttpd: cache: mount error: wrong or no file system Jan 6 09:50:04 hermes emhttpd: shcmd (91): /usr/sbin/zfs mount -a Jan 6 09:50:04 hermes emhttpd: shcmd (92): sync Jan 6 09:50:04 hermes emhttpd: shcmd (93): mkdir /mnt/user0 Jan 6 09:50:04 hermes emhttpd: shcmd (94): /usr/libexec/unraid/shfs /mnt/user0 -disks 2 -o default_permissions,allow_other,noatime Jan 6 09:50:04 hermes emhttpd: shcmd (95): mkdir /mnt/user Jan 6 09:50:04 hermes emhttpd: shcmd (96): /usr/libexec/unraid/shfs /mnt/user -disks 3 -o default_permissions,allow_other,noatime -o remember=0 Jan 6 09:50:04 hermes emhttpd: shcmd (99): /usr/local/sbin/update_cron Jan 6 09:50:04 hermes emhttpd: Starting services... Jan 6 09:50:04 hermes emhttpd: shcmd (102): /etc/rc.d/rc.samba reload Jan 6 09:50:05 hermes emhttpd: shcmd (106): /etc/rc.d/rc.avahidaemon reload Jan 6 09:50:05 hermes avahi-daemon[1976]: Got SIGHUP, reloading. Jan 6 09:50:05 hermes emhttpd: shcmd (116): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 20 Jan 6 09:50:05 hermes kernel: loop2: detected capacity change from 0 to 41943040 Jan 6 09:50:05 hermes kernel: BTRFS: device fsid 7da88bde-0100-400f-ae26-c3ac1329954e devid 1 transid 15410 /dev/loop2 scanned by mount (5189) Jan 6 09:50:05 hermes kernel: BTRFS info (device loop2): first mount of filesystem 7da88bde-0100-400f-ae26-c3ac1329954e Jan 6 09:50:05 hermes kernel: BTRFS info (device loop2): using crc32c (crc32c-intel) checksum algorithm Jan 6 09:50:05 hermes kernel: BTRFS info (device loop2): using free space tree Jan 6 09:50:05 hermes kernel: BTRFS info (device loop2): auto enabling async discard Jan 6 09:50:05 hermes root: Resize device id 1 (/dev/loop2) from 20.00GiB to max Jan 6 09:50:05 hermes emhttpd: shcmd (118): /etc/rc.d/rc.docker start Jan 6 09:50:05 hermes rc.docker: Starting Docker daemon... Jan 6 09:50:06 hermes sysDrivers: SysDrivers Build Complete Jan 6 09:50:09 hermes kernel: Bridge firewalling registered Jan 6 09:50:09 hermes kernel: Initializing XFRM netlink socket Jan 6 09:50:10 hermes kernel: docker0: port 1(veth203f8bc) entered blocking state Jan 6 09:50:10 hermes kernel: docker0: port 1(veth203f8bc) entered disabled state Jan 6 09:50:10 hermes kernel: veth203f8bc: entered allmulticast mode Jan 6 09:50:10 hermes kernel: veth203f8bc: entered promiscuous mode Jan 6 09:50:12 hermes kernel: eth0: renamed from veth1898a0a Jan 6 09:50:12 hermes kernel: docker0: port 1(veth203f8bc) entered blocking state Jan 6 09:50:12 hermes kernel: docker0: port 1(veth203f8bc) entered forwarding state Jan 6 09:50:13 hermes rc.docker: Docker daemon... Started. Jan 6 09:50:13 hermes rc.docker: Starting network... Jan 6 09:50:14 hermes rc.docker: created network ipvlan br0 with subnets: 172.16.0.0/12; Jan 6 09:50:14 hermes rc.docker: Network started. Jan 6 09:50:14 hermes rc.docker: Starting containers... Jan 6 09:50:14 hermes rc.docker: Containers started. Jan 6 09:50:14 hermes update_services: delay = 10s Jan 6 09:50:14 hermes emhttpd: nothing to sync Jan 6 09:50:16 hermes kernel: tun: Universal TUN/TAP device driver, 1.6 Jan 6 09:50:16 hermes kernel: wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information. Jan 6 09:50:16 hermes kernel: wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <[email protected]>. All Rights Reserved. Jan 6 09:50:20 hermes emhttpd: error: cmdFormat: missing csrf_token Edited January 6, 20251 yr by hhhbbb
January 6, 20251 yr Community Expert Try recreating the flash drive, that error should never happen with stock Unraid commands.
January 7, 20251 yr Author I recreated the flash drive by: - first creating a flash backup - reformatting the flash drive with Rufus - using the USB Creator to install v7 rc2 - deleting the `config` folder and replacing it with the `config` from my flash backup drive I then started my array and attempted again to format my cache drives, but unfortunately, I still run into the same issue of a new empty update.htm tab and the "error: cmdFormat: missing csrf_token" message in the logs.
January 7, 20251 yr Community Expert Solution By recreating I meant don't restore the config, or it may restore the problem, restore only the key, you can also restore super.dat if you want, for the assignments.
January 8, 20251 yr Author I restored only my key and super.dat and I was able to reformat my hard drives! I just need to reinstall my docker containers and plugins, but that's not bad at all. Thank you for the help @JorgeB!
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.