You are not logged in.

#1 2026-01-30 21:11:41

BeatrixVonDOS
Member
Registered: 2026-01-30
Posts: 3

can't mount drive even after cleaning using fsck

I was backing up my drive to wipe it on a old but functional SSD, its slow but i've done this several times before with this drive and use it as a backup, but by mistake i moved my hyprland config file to to drive instead of copying them and broke my system for a second but hit control z and rebooted and everything worked just fine, except i could'nt mount my drive anymore, i used fsck to clean the dirty whatever but now it's giving a new error and i dont know what to do, i am very much a linux noob and yes i know im a idiot for jumping straight into difficult distros before learning anything, but this drive has alot of importent stuff too me so please any help is needed, thank you.

THE ERROR:
ntfs_mst_post_read_fixup_warn: magic: 0xffffffff  size: 1024   usa_ofs: 65535  usa_count: 65535: Invalid argument
Record 0 has no FILE magic (0xffffffff)
Failed to load $MFT: Input/output error
Failed to mount '/dev/sda': Input/output error
NTFS is either inconsistent, or there is a hardware fault, or it's a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very
important! If the device is a SoftRAID/FakeRAID then first activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
for more details.

i then ran 'fsck -t ntfs /dev/sdc1'
got:
fsck from util-linux 2.41.3
Mounting volume... ntfs_mst_post_read_fixup_warn: magic: 0xffffffff  size: 1024   usa_ofs: 65535  usa_count: 65535: Invalid argument
Record 0 has no FILE magic (0xffffffff)
Failed to load $MFT: Input/output error
FAILED
Attempting to correct errors... ntfs_mst_post_read_fixup_warn: magic: 0xffffffff  size: 1024   usa_ofs: 65535  usa_count: 65535: Invalid argument
Record 0 has no FILE magic (0xffffffff)
Failed to load $MFT: Input/output error
FAILED
Failed to startup volume: Input/output error
Checking for self-located MFT segment... ntfs_mst_post_read_fixup_warn: magic: 0xffffffff  size: 1024   usa_ofs: 65535  usa_count: 65535: Invalid argument
OK
Unrecoverable error
Volume is corrupt. You should run chkdsk.
what do i do, my sister has a laptop with windows on it, do try to use chkdsk

Last edited by BeatrixVonDOS (2026-01-30 21:12:40)

Offline

#2 2026-01-30 21:19:36

BeatrixVonDOS
Member
Registered: 2026-01-30
Posts: 3

Re: can't mount drive even after cleaning using fsck

fsck gave this when i ran it '/dev/nvme0n1p1: 22 files, 28830/261628 clusters'
i think it just cleaned me laptops nvme and not the ssd

also ran this 'sudo mount -t ntfs3 -o force /dev/sda /home/bek0/mysdd'
got 'mount: /home/bek0/mysdd: fsconfig() failed: /dev/sda: Can't lookup blockdev.
       dmesg(1) may have more information after failed mount system call.'

dmesg said:
[  139.204020]  sda: sda1
[  139.204238] sd 2:0:0:0: [sda] Attached SCSI disk
[  139.250612] scsi 2:0:0:1: Wrong diagnostic page; asked for 1 got 8
[  139.250623] scsi 2:0:0:1: Failed to get diagnostic page 0x1
[  139.250626] scsi 2:0:0:1: Failed to bind enclosure -19
[  139.250656] ses 2:0:0:1: Attached Enclosure device
[  141.650563] ntfs3: Enabled Linux POSIX ACLs support
[  141.650565] ntfs3: Read-only LZX/Xpress compression included
[  141.651303] ntfs3(sda1): It is recommened to use chkdsk.
[  141.710214] ntfs3(sda1): volume is dirty and "force" flag is not set!
[  159.250050] ntfs3(sda1): It is recommened to use chkdsk.
[  159.278946] ntfs3(sda1): volume is dirty and "force" flag is not set!
[  268.302985] EXT4-fs (sda): VFS: Can't find ext4 filesystem
[  268.303243] EXT4-fs (sda): VFS: Can't find ext4 filesystem
[  268.303431] EXT4-fs (sda): VFS: Can't find ext4 filesystem
[  268.314097] FAT-fs (sda): invalid media value (0xb9)
[  268.314106] FAT-fs (sda): Can't find a valid FAT filesystem
[  268.315395] ntfs3(sda): Primary boot signature is not NTFS.
[  268.315408] ntfs3(sda): try to read out of volume at offset 0xe8decffe00
[  268.316369] ntfs3(sda): Primary boot signature is not NTFS.
[  268.316378] ntfs3(sda): try to read out of volume at offset 0xe8decffe00
[  703.157721] ntfs3(sda): Primary boot signature is not NTFS.
[  703.157742] ntfs3(sda): try to read out of volume at offset 0xe8decffe00
[  770.120466] ntfs3(sda): Primary boot signature is not NTFS.
[  770.120479] ntfs3(sda): try to read out of volume at offset 0xe8decffe00
[  771.807149] ntfs3(sda): Primary boot signature is not NTFS.
[  771.807165] ntfs3(sda): try to read out of volume at offset 0xe8decffe00
[  804.439691] ntfs3(sda): Primary boot signature is not NTFS.
[  804.439705] ntfs3(sda): try to read out of volume at offset 0xe8decffe00
[  878.966970] wlan0: AP e4:83:26:ca:71:48 appears to change mode (expected HT, found legacy) in beacon, disconnect
[  883.081829] wlan0: authenticate with e4:83:26:ca:71:48 (local address=b8:1e:a4:75:f6:a5)
[  883.081834] wlan0: send auth to e4:83:26:ca:71:48 (try 1/3)
[  883.084396] wlan0: authenticated
[  883.084720] wlan0: associate with e4:83:26:ca:71:48 (try 1/3)
[  883.089738] wlan0: RX AssocResp from e4:83:26:ca:71:48 (capab=0x1431 status=0 aid=38)
[  883.202373] wlan0: associated
[ 1269.310413] EXT4-fs (sda): VFS: Can't find ext4 filesystem
[ 1269.310610] EXT4-fs (sda): VFS: Can't find ext4 filesystem
[ 1269.310755] EXT4-fs (sda): VFS: Can't find ext4 filesystem
[ 1269.311075] FAT-fs (sda): bogus number of reserved sectors
[ 1269.311077] FAT-fs (sda): Can't find a valid FAT filesystem
[ 1312.919251] EXT4-fs (sda): VFS: Can't find ext4 filesystem
[ 1312.919564] EXT4-fs (sda): VFS: Can't find ext4 filesystem
[ 1312.919732] EXT4-fs (sda): VFS: Can't find ext4 filesystem
[ 1312.920376] FAT-fs (sda): bogus number of reserved sectors
[ 1312.920379] FAT-fs (sda): Can't find a valid FAT filesystem
[ 1313.857090] EXT4-fs (sda): VFS: Can't find ext4 filesystem
[ 1313.857283] EXT4-fs (sda): VFS: Can't find ext4 filesystem
[ 1313.857436] EXT4-fs (sda): VFS: Can't find ext4 filesystem
[ 1313.857760] FAT-fs (sda): bogus number of reserved sectors
[ 1313.857762] FAT-fs (sda): Can't find a valid FAT filesystem
[ 1321.202012] usb 4-1: USB disconnect, device number 2
[ 1330.075097] usb 4-1: new SuperSpeed USB device number 3 using xhci_hcd
[ 1330.086662] usb 4-1: New USB device found, idVendor=1058, idProduct=0810, bcdDevice=10.49
[ 1330.086673] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1330.086676] usb 4-1: Product: My Passport 0810
[ 1330.086679] usb 4-1: Manufacturer: Western Digital
[ 1330.086682] usb 4-1: SerialNumber: 575837314542334B31363634
[ 1330.089643] usb-storage 4-1:1.0: USB Mass Storage device detected
[ 1330.089987] scsi host2: usb-storage 4-1:1.0
[ 1331.107641] scsi 2:0:0:0: Direct-Access     WD       My Passport 0810 1049 PQ: 0 ANSI: 6
[ 1331.107909] scsi 2:0:0:1: Enclosure         WD       SES Device       1049 PQ: 0 ANSI: 6
[ 1331.109686] sd 2:0:0:0: Attached scsi generic sg0 type 0
[ 1331.109822] ses 2:0:0:1: Attached Enclosure device
[ 1331.109891] ses 2:0:0:1: Attached scsi generic sg1 type 13
[ 1331.111214] sd 2:0:0:0: [sda] Spinning up disk...
[ 1335.993252] ses 2:0:0:1: Wrong diagnostic page; asked for 1 got 8
[ 1335.993265] ses 2:0:0:1: Failed to get diagnostic page 0x1
[ 1335.993269] ses 2:0:0:1: Failed to bind enclosure -19
[ 1336.995077] .ready
[ 1337.065491] sd 2:0:0:0: [sda] 1953458176 512-byte logical blocks: (1.00 TB/931 GiB)

i dont whats happpening  does it not have a file sysytem i dont know what to do

Offline

#3 2026-01-31 10:32:31

BeatrixVonDOS
Member
Registered: 2026-01-30
Posts: 3

Re: can't mount drive even after cleaning using fsck

never mind just formatted it, it didnt have any drivers, or a file system and now cant even see the partition

Offline

Board footer

Powered by FluxBB