The system ran out of memory and I had to shut it down by keeping the power button pressed because it wasn’t even responding to keyboard commands, like REISUB. Now the internal hard drive isn’t mounting and the system doesn’t recognize it. It’s doing a sound all the time like ‘crgg’ as if it’s trying to start but it can’t. I’ve tried restarting a few times but it doesn’t mount and I don’t know what else to do.
Try to boot from a Live USB/DVD and fsck the drive partition i guess 
If that drive is still making that sound even when you boot from the Live medium, then i guess it died…
The system boots fine, I have it on an SSD. So I can just run that command without booting from a LIVE USB right?
❯ sudo fsck /dev/sdh
fsck from util-linux 2.38.1
e2fsck 1.46.5 (30-Dec-2021)
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/sdh
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/sdh contains `DOS/MBR boot sector; partition 1 : ID=0xee, start-CHS (0x0,0,2), end-CHS (0x3ff,255,63), startsector 1, 60555263 sectors, extended partition table (last)' data
❯ sudo e2fsck -b 8193 /dev/sdh
[sudo] password for user:
e2fsck 1.46.5 (30-Dec-2021)
e2fsck: Bad magic number in super-block while trying to open /dev/sdh
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/sdh contains `DOS/MBR boot sector; partition 1 : ID=0xee, start-CHS (0x0,0,2), end-CHS (0x3ff,255,63), startsector 1, 60555263 sectors, extended partition table (last)' data
❯ sudo e2fsck -b 32768 /dev/sdh
e2fsck 1.46.5 (30-Dec-2021)
e2fsck: Bad magic number in super-block while trying to open /dev/sdh
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/sdh contains `DOS/MBR boot sector; partition 1 : ID=0xee, start-CHS (0x0,0,2), end-CHS (0x3ff,255,63), startsector 1, 60555263 sectors, extended partition table (last)' data
Maybe connecting the hard drive to a computer with Windows could solve this?
This is the whole device.
You can’t fs check the whole device - just partitions on it.
The filesystem (which you want to check) is on a partition on that device.
like: /dev/sdh1
What filesystem is it? ext4? or ntfs?
External device … connected via USB?
It could be a power issue - the USB port might not deliver sufficient power to drive the device properly.
I have this issue here with some USB spinning harddisk.
I have to use a powered Hub to use it on my laptop’s USB ports.
This doesn’t seem to do anything. I only have one partition so it should be /dev/sdh1.
❯ sudo fsck /dev/sdh1
fsck from util-linux 2.38.1
Internal ext4 hard drive.
sounds like a classic headcrash, the drive is dead.
The sound is pretty normal, but it just keeps repeating again and again.
What does the headcrash sound like? If it’s anything like this then it’s not that.
I’ve restarted again and now it works. Perhaps that last
❯ sudo fsck /dev/sdh1
fsck from util-linux 2.38.1
did something after all.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.