[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bad magic number in super-block



Moin,

ich habe eine externe USB-FP mit 4 TO Speicherkapazität für Sicherheitskopien:

"# fdisk -l /dev/sdb
Disk /dev/sdb: 3.64 TiB, 4000787029504 bytes, 7814037167 sectors
Disk model: M3 Portable
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: 604D0441-323B-43B2-B3E1-28B322F9D04B

Device        Start        End    Sectors  Size Type
/dev/sdb1        34     262177     262144  128M Microsoft reserved
/dev/sdb2    264192    8652799    8388608    4G Linux swap
/dev/sdb3   8652800   71567359   62914560   30G Linux filesystem
/dev/sdb4  71567360 7814037133 7742469774  3.6T Linux filesystem

Partition 1 does not start on physical sector boundary."

Ich bekomme folgende Fehlermeldung:

"# e2fsck  -c /dev/sdb
e2fsck 1.45.6 (20-Mar-2020)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: 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>
 or
    e2fsck -b 32768 <device>

Found a gpt partition table in /dev/sdb".

"e2fsck -b 8193 /dev/sdb" oder "e2fsck -b 32768 /dev/sdb" ergeben die gleiche Fehlermeldung.

Was kann ich da noch machen?

Gruß

Klaus


Reply to: