I’m once again asking for your support. Yesterday I had a power outage while moving a folder from my external drive to my secondary hard disk. I was booted into emergency mode, but modified my secondary disk out of my /etc/fstab file and managed to boot fine into my system. I am however having trouble with mounting my secondary drive now.
An error occurred while accessing 'Lageret', the system responded: The requested operation has failed: Error mounting /dev/sdb2 at /run/media/oelholm/Lageret: Unknown error when mounting /dev/sdb2
fdisk -l tells me:
Disk /dev/sdb: 3,64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: TOSHIBA HDWD240
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: 74A8410B-E867-4C3B-A981-66772C4ED136
Device Start End Sectors Size Type
/dev/sdb1 34 32767 32734 16M Microsoft reserved
/dev/sdb2 32768 7814033407 7814000640 3,6T Microsoft basic data
Partition 1 does not start on physical sector boundary.
Is my data gone?
Boot off the install media and fsck the disk.
I’m writing from beyond the install USB
fdisk /dev/sdb gives me the following:
sudo fsck /dev/sdb
fsck from util-linux 2.36.1
e2fsck 1.46.0 (29-Jan-2020)
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/sdb
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>
e2fsck -b 32768 <device>
/dev/sdb contains `DOS/MBR boot sector MS-MBR Windows 7 english at offset 0x163 "Invalid partition table" at offset 0x17b "Error loading operating system" at offset 0x19a "Missing operating system"; partition 1 : ID=0xee, start-CHS (0x0,0,2), end-CHS (0x0,254,63), startsector 1, 4294967295 sectors' data
Could this be because it’s NTFS?
If it is formatted by Windows, I think you should use Windows tools.
And for the future, there are UPS devices available for about 100 euros and more.
UPS devices may really help on power outages, you have some time to properly shut down your systems.
Currently running chkdsk on windows 10. It’s about four hours in and it reports three hours left. Good old spinning harddrives hahaha
Another reason a i hate Windows! Normally when i run into this kind of a problem on a Windows formatted drive i do a low level format on it to bring it back to life with a drive utility.
It finished, and everything seems to work now. Boy, did it take a lot of time