[SOLVED] HDD got unmounted when hyprland crashed. Now: wrong fs etc.

thefinn · 2026-01-15 16:01:17

Hi. Thanks in advance for any help.

Context:
I was messing around with adding large files to my e-reader when hyprland suddenly crashed. My e-reader and my external harddrive were mounted at the time. At least that's how I remember it. Then the next thing I know hyprland boots up again and my HDD doesn't mount. (I'm not 100% on the chronology here, but it's what makes the most sense to me.)

Error msg:
"An error occurred while accessing '[disk]', the system responded: The requested operation has failed: Error mounting /dev/sdc1 at /run/media/k/[disk]: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error."

What I did next:
After I restarted and it didn't work, and I tried mounting it to my Linux/Win dual boot laptop in both OS's and that didn't work, I started panicking a little bit and tried finding solutions online.

Thing 1: Disks GUI. I went on my laptop, which runs Gnome, and ran Disks. These two steps didn't work (writing these from memory, sorry if some are errata): 1) pressing the "play" button, and 2) pressing the "gear" button, pressing "Edit mount options" and unchecking "User session defaults". Still same error message. Then the post said to press "Check filesystem" or "Repair filesystem". These were greyed out for me; I couldn't click them.

Thing 2: mount. I tried:

mount /dev/sdc ~/temp

But got the same error msg as before.

Thing 3: fsck. I tried fsck-ing. Here's the result:

sudo fsck -M /dev/sdc
fsck from util-linux 2.41.3
e2fsck 1.47.3 (8-Jul-2025)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdc

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

/dev/sdc contains `DOS/MBR boot sector; partition 1 : ID=0xee, start-CHS (0x0,0,2), end-CHS (0x2fc,254,63), startsector 1, 4294967295 sectors, extended partition table (last)' data

Thing 4: e2fsck. I tried doing the superblock thing fsck told me to do. I got the same error message from both numbers (or superblocks, I take it).

sudo e2fsck -b 8193 /dev/sdc 
e2fsck 1.47.3 (8-Jul-2025)
e2fsck: Bad magic number in super-block while trying to open /dev/sdc

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

/dev/sdc contains `DOS/MBR boot sector; partition 1 : ID=0xee, start-CHS (0x0,0,2), end-CHS (0x2fc,254,63), startsector 1, 4294967295 sectors, extended partition table (last)' data

Thing 5: dmesg. Here's some of the output from that with bold text or colours. I don't really know what to do with it, though, and that's why I came here.

[    5.126008] spi-nor spi0.0: probe with driver spi-nor failed with error -22
[    5.134012] r8169 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control

[    5.250965] at24 8-0051: supply vcc not found, using dummy regulator
[    5.253043] at24 8-0051: 256 byte spd EEPROM, read-only
[    5.253070] at24 8-0053: supply vcc not found, using dummy regulator
[    5.255008] at24 8-0053: 256 byte spd EEPROM, read-only
[    5.255774] ppdev: user-space parallel port driver

[    5.362423] intel_rapl_common: Found RAPL domain package
[    5.362427] intel_rapl_common: Found RAPL domain core
[    5.362428] intel_rapl_common: Found RAPL domain dram
[    5.589842] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[    5.595622] systemd-journald[310]: Received client request to flush runtime journal.
[    5.716180] EXT4-fs (sdb1): mounted filesystem 70393c0e-f5ca-4925-9211-0a71b5f77a8b r/w with ordered data mode. Quota mode: none. ************NOTE that this is sdb1, not sdc1. My problem is with sdc.*****

[  148.999703] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2

So yeah, that's it. I don't really know what to do. But I have hope that there is some solution I'm just too dumb to know about!

Last edited by thefinn (2026-01-15 19:56:07)

thefinn · 2026-01-15 16:07:08

Actually, here's some more dmesg before I go eat. (I checked it again now; I assume the new stuff is from when I last tried to connect the HDD.)

[  148.317983] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.
[  148.317986] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.
[  148.995458] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[  148.999065] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[  148.999420] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[  148.999703] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[  148.999707] cfg80211: failed to load regulatory.db
[  294.460014] usb 4-5: new SuperSpeed USB device number 2 using xhci_hcd
[  294.474304] usb 4-5: New USB device found, idVendor=1058, idProduct=2621, bcdDevice=10.34
[  294.474317] usb 4-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  294.474323] usb 4-5: Product: Elements 2621
[  294.474328] usb 4-5: Manufacturer: Western Digital
[  294.474332] usb 4-5: SerialNumber: 575838324443345057304C36
[  294.493193] usb-storage 4-5:1.0: USB Mass Storage device detected
[  294.493451] scsi host6: usb-storage 4-5:1.0
[  294.493530] usbcore: registered new interface driver usb-storage
[  294.497133] usbcore: registered new interface driver uas
[  295.501487] scsi 6:0:0:0: Direct-Access     WD       Elements 2621    1034 PQ: 0 ANSI: 6
[  295.503397] sd 6:0:0:0: [sdc] Spinning up disk...
[  296.513280] ......ready
[  301.581135] sd 6:0:0:0: [sdc] Very big device. Trying to use READ CAPACITY(16).
[  301.598750] sd 6:0:0:0: [sdc] 9767475200 512-byte logical blocks: (5.00 TB/4.55 TiB)
[  301.598752] sd 6:0:0:0: [sdc] 4096-byte physical blocks
[  301.599208] sd 6:0:0:0: [sdc] Write Protect is off
[  301.599214] sd 6:0:0:0: [sdc] Mode Sense: 47 00 10 08
[  301.599547] sd 6:0:0:0: [sdc] No Caching mode page found
[  301.599550] sd 6:0:0:0: [sdc] Assuming drive cache: write through
[  301.649068]  sdc: sdc1
[  301.649236] sd 6:0:0:0: [sdc] Attached SCSI disk
[  312.143193] ntfs3: Enabled Linux POSIX ACLs support
[  312.143196] ntfs3: Read-only LZX/Xpress compression included
[  312.145398] ntfs3(sdc1): It is recommened to use chkdsk.
[  312.357129] ntfs3(sdc1): volume is dirty and "force" flag is not set!
[  599.247135] usb 4-5: USB disconnect, device number 2
[  750.175234] logitech-hidpp-device 0003:046D:1023.0005: HID++ 1.0 device connected.
[  874.297051] usb 4-5: new SuperSpeed USB device number 3 using xhci_hcd
[  874.311368] usb 4-5: New USB device found, idVendor=1058, idProduct=2621, bcdDevice=10.34
[  874.311381] usb 4-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  874.311388] usb 4-5: Product: Elements 2621
[  874.311392] usb 4-5: Manufacturer: Western Digital
[  874.311397] usb 4-5: SerialNumber: 575838324443345057304C36
[  874.313056] usb-storage 4-5:1.0: USB Mass Storage device detected
[  874.313381] scsi host6: usb-storage 4-5:1.0
[  875.338403] scsi 6:0:0:0: Direct-Access     WD       Elements 2621    1034 PQ: 0 ANSI: 6
[  875.340146] sd 6:0:0:0: [sdc] Spinning up disk...
[  876.350286] ......ready
[  881.417672] sd 6:0:0:0: [sdc] Very big device. Trying to use READ CAPACITY(16).
[  881.590076] sd 6:0:0:0: [sdc] 9767475200 512-byte logical blocks: (5.00 TB/4.55 TiB)
[  881.590089] sd 6:0:0:0: [sdc] 4096-byte physical blocks
[  881.590435] sd 6:0:0:0: [sdc] Write Protect is off
[  881.590447] sd 6:0:0:0: [sdc] Mode Sense: 47 00 10 08
[  881.590767] sd 6:0:0:0: [sdc] No Caching mode page found
[  881.590770] sd 6:0:0:0: [sdc] Assuming drive cache: write through
[  881.627724]  sdc: sdc1
[  881.627842] sd 6:0:0:0: [sdc] Attached SCSI disk
[  883.780607] ntfs3(sdc1): It is recommened to use chkdsk.
[  883.848655] ntfs3(sdc1): volume is dirty and "force" flag is not set!
[  885.717213] ntfs3(sdc1): It is recommened to use chkdsk.
[  885.748616] ntfs3(sdc1): volume is dirty and "force" flag is not set!
[  886.690907] ntfs3(sdc1): It is recommened to use chkdsk.
[  886.692745] ntfs3(sdc1): volume is dirty and "force" flag is not set!
[  887.466345] ntfs3(sdc1): It is recommened to use chkdsk.
[  887.468274] ntfs3(sdc1): volume is dirty and "force" flag is not set!
[  889.641960] ntfs3(sdc1): It is recommened to use chkdsk.
[  889.643815] ntfs3(sdc1): volume is dirty and "force" flag is not set!
[  890.720723] ntfs3(sdc1): It is recommened to use chkdsk.
[  890.722574] ntfs3(sdc1): volume is dirty and "force" flag is not set!
[ 2065.692154] FAT-fs (sdc): bogus number of reserved sectors
[ 2065.692158] FAT-fs (sdc): Can't find a valid FAT filesystem
[ 2065.692828] EXT4-fs (sdc): VFS: Can't find ext4 filesystem
[ 2065.693677] EXT4-fs (sdc): VFS: Can't find ext4 filesystem
[ 2065.694467] EXT4-fs (sdc): VFS: Can't find ext4 filesystem
[ 2065.695358] ntfs3(sdc): Primary boot signature is not NTFS.
[ 2065.695363] ntfs3(sdc): try to read out of volume at offset 0x48c5faffe00

Scimmia · 2026-01-15 16:13:40

Why do you keep trying to mount or fsck /dev/sdc instead of /dev/sdc1? Is there not supposed to be a partition on this disk?

Last edited by Scimmia (2026-01-15 16:14:11)

thefinn · 2026-01-15 18:34:49

No, there is a partition on it. I just don't really understand computers yet. The first fsck I did was on sdc1, but it just gave me this:

 fsck from util-linux 2.41.3 
fsck: fsck.ntfs not found; ignore /dev/sdc1

So I thought I was doing it wrong by not fsck-ing sdc.

Regarding mounting, I tried this now:

 sudo mount /dev/sdc1 ~/temp

And got this:

mount: /home/k/temp: unknown filesystem type 'ntfs'.
       dmesg(1) may have more information after failed mount system call.

Last edited by thefinn (2026-01-15 18:35:34)

Scimmia · 2026-01-15 18:44:22

Ok, then, that makes more sense.

There is no fsck for ntfs. There is ntfsfix, but it's very much not recommended. To fix a NTFS filesystem, you use chkdsk in Windows. That last error about unknown filesystem is usually because you've updated the kernel without rebooting, so there are no modules to load for it.

V1del · 2026-01-15 18:46:15

[  883.780607] ntfs3(sdc1): It is recommened to use chkdsk.
[  883.848655] ntfs3(sdc1): volume is dirty and "force" flag is not set!

fsck is not chkdsk, get the disk to a Windows install and run chkdsk. If you don't have a Windows install anymore, why are you still using ntfs? You can "bypass" this by using ntfsfix -d from ntfs-3g but this just removes the dirty flag and doesn't do proper consistency checks, files could be corrupted silently, do a proper check with chkdsk.

5hridhyan · 2026-01-15 18:48:05

ntfs3(sdc1): volume is dirty and "force" flag is not set!
ntfs3(sdc1): It is recommended to use chkdsk.

attach to a Windows system and run "chkdsk X: /f" replace the "X" with the Drive letter, let it finish completely, and After repair, from linux side install a package from pacman "ntfs-3g'
then mount....

edit:
repeated post bymistake, I should have refresh the page before replying, missed recent replies, sorry.

Last edited by 5hridhyan (2026-01-15 18:57:18)

thefinn · 2026-01-15 19:53:59

Thanks guys, you're spot on -- and thanks for the extra info about ntfs-3g.
For anyone possibly struggling with the same thing: When I installed ntfs-3g I got a much better error message from "mount /dev/sdc1 ~/temp". It basically told me the same thing as Scimmia and V1del: to use chkdsk.
But also: When I opened Windows this time, I did so without plugging in the HDD first. I didn't realize this would be a difference, but it was. When plugging the HDD into a Windows up and running, I got a gui asking me to scan and repair the drive. This fixed it.

Thanks guys!!

Last edited by thefinn (2026-01-15 19:56:55)

seth · 2026-01-15 20:40:00

But also: When I opened Windows this time

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

Also windows has a "remove savely" feature which syncs and closes the filesystem and then notifies you that it's ready and you *have* to use that, regardless of OS or dual booting.

thefinn · 2026-01-16 09:52:38

3rd link below

I remember doing this when I first set up the dual boot! I assume something about my comment indicates that fast startup is on, but I really think I did disable it properly back when I set everything up. (I followed the instruction in the 3rd link.) I assumed Windows not giving me the "sync and repair" gui was because I had the hdd plugged in the whole time from Linux reboot -> grub -> windows boot manager -> windows.

seth · 2026-01-16 10:17:39

The question is why the NTFS ended up dirty, dual boot hibernation ("fast start") is one possible explanation, so I posted a textblock for you to look into that.
nb. that MS frequently re-enables the feature w/ updates so it's a good idea to frequently check that it's still disabled - it will otherwise run you into trouble. Also frequently

thefinn · 2026-01-16 10:21:10

Ah, I see. Thanks! In this case, I can fairly safely say it isn't the reason for the dirty drive. The reason is that I have been using two computers throughout this thread: Only my laptop is set up as a dual boot, and the dirty flag happened when the hdd was plugged into my arch-only stationary. But I will check the fast startup now on my laptop. Cheers!

Arch Linux

#1 2026-01-15 16:01:17

[SOLVED] HDD got unmounted when hyprland crashed. Now: wrong fs etc.

#2 2026-01-15 16:07:08

Re: [SOLVED] HDD got unmounted when hyprland crashed. Now: wrong fs etc.

#3 2026-01-15 16:13:40

Re: [SOLVED] HDD got unmounted when hyprland crashed. Now: wrong fs etc.

#4 2026-01-15 18:34:49

Re: [SOLVED] HDD got unmounted when hyprland crashed. Now: wrong fs etc.

#5 2026-01-15 18:44:22

Re: [SOLVED] HDD got unmounted when hyprland crashed. Now: wrong fs etc.

#6 2026-01-15 18:46:15

Re: [SOLVED] HDD got unmounted when hyprland crashed. Now: wrong fs etc.

#7 2026-01-15 18:48:05

Re: [SOLVED] HDD got unmounted when hyprland crashed. Now: wrong fs etc.

#8 2026-01-15 19:53:59

Re: [SOLVED] HDD got unmounted when hyprland crashed. Now: wrong fs etc.

#9 2026-01-15 20:40:00

Re: [SOLVED] HDD got unmounted when hyprland crashed. Now: wrong fs etc.

#10 2026-01-16 09:52:38

Re: [SOLVED] HDD got unmounted when hyprland crashed. Now: wrong fs etc.

#11 2026-01-16 10:17:39

Re: [SOLVED] HDD got unmounted when hyprland crashed. Now: wrong fs etc.

#12 2026-01-16 10:21:10

Re: [SOLVED] HDD got unmounted when hyprland crashed. Now: wrong fs etc.

Board footer