Hello,
Sorry, I missed,
But, unbelivable!!!
In the Message;
Subject : Re: External USB disks not recognized - Leap 15.3
Message-ID : <9eb9884e-38bd-f637-ce8e-d03f2b64f2c4@coldsiberia.org>
Date & Time: Sun, 24 Apr 2022 20:08:12 +0200
[PIO] == Per Inge Oestmoen has written:
[...]
PIO> Here we go:
PIO> ----
PIO> localhost:/home/siberia # fsck -n /dev/nvme0n1
PIO> fsck from util-linux 2.36.2
PIO> e2fsck 1.43.8 (1-Jan-2018)
PIO> Warning! /dev/nvme0n1 is in use.
PIO> ext2fs_open2: Bad magic number in super-block
PIO> fsck.ext2: Superblock invalid, trying backup blocks...
PIO> fsck.ext2: Bad magic number in super-block while trying to open /dev/nvme0n1
PIO> The superblock could not be read or does not describe a valid ext2/ext3/ext4
PIO> filesystem. If the device is valid and it really contains an ext2/ext3/ext4
PIO> filesystem (and not swap or ufs or something else), then the superblock
PIO> is corrupt, and you might try running e2fsck with an alternate superblock:
PIO> e2fsck -b 8193 <device>
PIO> or
PIO> e2fsck -b 32768 <device>
PIO> Found a gpt partition table in /dev/nvme0n1
PIO> ----
PIO> ----
PIO> localhost:/home/siberia # fsck -n /dev/sda
PIO> fsck from util-linux 2.36.2
PIO> e2fsck 1.43.8 (1-Jan-2018)
PIO> ext2fs_open2: Bad magic number in super-block
PIO> fsck.ext2: Superblock invalid, trying backup blocks...
PIO> fsck.ext2: Bad magic number in super-block while trying to open /dev/sda
PIO> The superblock could not be read or does not describe a valid ext2/ext3/ext4
PIO> filesystem. If the device is valid and it really contains an ext2/ext3/ext4
PIO> filesystem (and not swap or ufs or something else), then the superblock
PIO> is corrupt, and you might try running e2fsck with an alternate superblock:
PIO> e2fsck -b 8193 <device>
PIO> or
PIO> e2fsck -b 32768 <device>
PIO> Found a gpt partition table in /dev/sda
PIO> ----
PIO> ----
PIO> localhost:/home/siberia # fsck -n /dev/sdb
PIO> fsck from util-linux 2.36.2
PIO> e2fsck 1.43.8 (1-Jan-2018)
PIO> Warning! /dev/sdb is in use.
PIO> ext2fs_open2: Bad magic number in super-block
PIO> fsck.ext2: Superblock invalid, trying backup blocks...
PIO> fsck.ext2: Bad magic number in super-block while trying to open /dev/sdb
PIO> The superblock could not be read or does not describe a valid ext2/ext3/ext4
PIO> filesystem. If the device is valid and it really contains an ext2/ext3/ext4
PIO> filesystem (and not swap or ufs or something else), then the superblock
PIO> is corrupt, and you might try running e2fsck with an alternate superblock:
PIO> e2fsck -b 8193 <device>
PIO> or
PIO> e2fsck -b 32768 <device>
PIO> Found a gpt partition table in /dev/sdb
First.
It is common knowledge that checking HDDs must be done in an unmounted
state.
In other words, you should boot your PC with the opensuse installation
disc, enter rescue mode, and perform an internal or external HDD
check.
I must say that your approach is extremely dangerous!
Second.
Did you try to understand the meaning of the message after the check?
It should be accepted that there are very few people who will continue
to use the system after seeing this message.
Usually, they will immediately make a backup and replace the HDD.
This is because continuing to use the system as it is will destroy not
only the other HDDs, but also the system itself.
Regards & Good Night.
---
┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp
┃\/彡
┗━━┛ Think.
-- The IBM slogan --