October 4, 2025Oct 4 Hi,After I updated to 7.1.4 I got an error on 2 of my drives with "Unmountable: unsupported or no file system".I stopped the array and ran "sgdisk -o -a 8 -n 1:32K:0 /dev/sdX" on both drives, one of them came back after that but the other is still down with "Unmountable: unsupported or no file system".What else can I do?thebasement-diagnostics-20251004-1803.zip Edited October 4, 2025Oct 4 by Humi
October 5, 2025Oct 5 Please NEVER run random commands you find on other threads; most likely they don't apply. Are the diags before or after running those?
October 5, 2025Oct 5 Author 3 hours ago, JorgeB said:Please NEVER run random commands you find on other threads; most likely they don't apply. Are the diags before or after running those?They are after running it
October 6, 2025Oct 6 With the array started post the output from wipefs /dev/md1p1 (this as written won't wipe anything)Also, which other disk is unmountable, only seeing disk1, and there's a pool with a missing device, is this expected?
October 6, 2025Oct 6 Author I didn't get anything when I ran "wipefs /dev/md1p1".Disk 1 is my problem atm. It was 1 and 3, but 3 came back.The pool problem is not suppose to be like that. Should only have 1 disk on each pool. But for some reason one of the pools wants to have two. How do I change that?
October 7, 2025Oct 7 Let's first deal with disk1, do you have any diags from when disk1 was working? It can be from months ago, as long as it was the same disk.
October 7, 2025Oct 7 Author Sadly not. Should probably start doing some checkups on the disks every now and then.
October 7, 2025Oct 7 Without diags it will be a guessing game. Currently there is no filesystem signature being detected on disk1, assuming it was using xfs, and the partition layout is still correct, which it may not be, try running xfs_repair to see if it finds a backup superblock, with the array running type:xfs_repair /dev/md1p1
October 7, 2025Oct 7 Author Amazing! It worked! Seems like the pool problem also got solved at the same time Did a restart and got new logs.BIG Thanks!This is what I got from the repair: Phase 1 - find and verify superblock...bad primary superblock - bad magic number !!!attempting to find secondary superblock....found candidate secondary superblock...verified secondary superblock...writing modified primary superblockPhase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... thebasement-diagnostics-20251007-1651.zip
October 7, 2025Oct 7 Great, disk1 is almost full, so hopefully all data is there, check for a lost+found folder, there may be some lost files.
October 8, 2025Oct 8 Author Can't find any folders that are called lost or found. I've been checking via Krusader, is there any otherway to check for them?
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.