January 15, 20251 yr I recently upgraded my system, and I'm encountering an issue with Disk1. It is now listed as "Unmountable: no file system." Unfortunately, it doesn't mount even when I boot into safe mode. Since the disk is unmounted, I'm unable to run a Btrfs scrub. Jan 15 18:33:13 Tower emhttpd: Mounting disks... Jan 15 18:33:13 Tower emhttpd: mounting /mnt/disk1 Jan 15 18:33:13 Tower emhttpd: shcmd (353): mkdir -m 0666 -p /mnt/disk1 Jan 15 18:33:13 Tower emhttpd: /sbin/blkid /dev/md1p1 2>&1 Jan 15 18:33:13 Tower emhttpd: shcmd (354): rmdir /mnt/disk1 Jan 15 18:33:13 Tower emhttpd: disk1: mount error: no file system Jan 15 18:33:13 Tower emhttpd: mounting /mnt/disk2 Edited January 15, 20251 yr by smithgdpr
January 15, 20251 yr Community Expert Please post the output from: wipefs /dev/sdd1 Despite the name, this command as written, won't wipe anything.
January 15, 20251 yr Author 5 minutes ago, JorgeB said: Please post the output from: wipefs /dev/sdd1 Despite the name, this command as written, won't wipe anything. wipefs /dev/sdd1 wipefs: error: /dev/sdd1: probing initialization failed: No such file or directory wipefs /dev/sdd DEVICE OFFSET TYPE UUID LABEL sdd 0x200 gpt sdd 0x74702555e00 gpt sdd 0x1fe PMBR
January 15, 20251 yr Community Expert Is disk1 still sdd as in the diags? If yes, post the output from: fdisk -l /dev/sdd
January 15, 20251 yr Author 1 minute ago, JorgeB said: Is disk1 still sdd as in the diags? If yes, post the output from: fdisk -l /dev/sdd The diagnostics reflect the current system fdisk -l /dev/sdd Disk /dev/sdd: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors Disk model: TOSHIBA HDWN180 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 0527CABE-5552-40BB-94AC-9C04EA4FC4EA Device Start End Sectors Size Type /dev/sdd1 64 15628053134 15628053071 7.3T Linux filesystem
January 15, 20251 yr Community Expert 5 minutes ago, smithgdpr said: /dev/sdd1: probing initialization failed: No such file or directory This error doesn't make sense, there's a partition sdd1 post output from blkid /dev/sdd1
January 15, 20251 yr Author 5 minutes ago, JorgeB said: This error doesn't make sense, there's a partition sdd1 post output from blkid /dev/sdd1 blkid /dev/sdd1 #no output blkid /dev/sdd /dev/sdd: PTUUID="0527cabe-5552-40bb-94ac-9c04ea4fc4ea" PTTYPE="gpt"
January 15, 20251 yr Community Expert If the array is running try stopping it first, and then retry: 21 minutes ago, JorgeB said: wipefs /dev/sdd1
January 15, 20251 yr Author 1 minute ago, JorgeB said: or with the array running wipefs /dev/md1p1 wipefs /dev/md1p1 DEVICE OFFSET TYPE UUID LABEL md1p1 0x0 xfs fff50345-de61-427b-8187-81eebdee4cb7 md1p1 0x10040 btrfs 97f8a3a9-b0a1-47e7-a062-53680695e51b
January 15, 20251 yr Community Expert ahh, now we have something, that is the problem, there are two signatures, you were also using btrfs for disk1 right?
January 15, 20251 yr Author Just now, JorgeB said: ahh, now we have something, that is the problem, there are two signatures, you were also using btrfs for disk1 right? It's supposed to be btrfs, definitely weird
January 15, 20251 yr Author 10 minutes ago, JorgeB said: ahh, now we have something, that is the problem, there are two signatures, you were also using btrfs for disk1 right? 9 minutes ago, smithgdpr said: It's supposed to be btrfs, definitely weird How do i proceed? Wipe and rebuild from parity?
January 15, 20251 yr Community Expert Solution If you are sure it's btrfs, you can use wipefs to wipe the xfs signature, this should be pretty safe, but always good to make sure backups are up to date first: wipefs -a -t xfs /dev/md1p1 Then restart the array
January 15, 20251 yr Author 13 minutes ago, JorgeB said: If you are sure it's btrfs, you can use wipefs to wipe the xfs signature, this should be pretty safe, but always good to make sure backups are up to date first: wipefs -a -t xfs /dev/md1p1 Then restart the array Tyvm! Worked like a charm. I've no idea how that happend. It has always been btrfs... Anyway, thanks for you time, I really appreciate it! Cheers.
January 16, 20251 yr Community Expert 13 hours ago, smithgdpr said: I've no idea how that happend. The dual signatures mean the device wasn't properly wiped before, when it was reformatted btrfs, but it wasn't a problem with v6.12 because it ignored it.
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.