LINUX.ORG.RU

История изменений

Исправление makoven, (текущая версия) :

Делал fsck.ext4 на sdc3. А оно кажись выполнило e2fsck. Или надо e2fsck на md2 делать?

root@work:/home/user# fsck.ext4  /dev/sdc3  
e2fsck 1.43.5 (04-Aug-2017)
ext2fs_open2: Bad magic number in super-block
fsck.ext4: Superblock invalid, trying backup blocks...
fsck.ext4: Bad magic number in super-block while trying to open /dev/sdc3

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>

Исправление makoven, :

Делал fsck на sdc3. А оно кажись выполнило e2fsck. Или надо e2fsck на md2 делать?

root@work:/home/user# fsck.ext4  /dev/sdc3  
e2fsck 1.43.5 (04-Aug-2017)
ext2fs_open2: Bad magic number in super-block
fsck.ext4: Superblock invalid, trying backup blocks...
fsck.ext4: Bad magic number in super-block while trying to open /dev/sdc3

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>

Исходная версия makoven, :

Делал fsck на sdc3. А оно кажись выполнило e2fsck

root@work:/home/user# fsck.ext4  /dev/sdc3  
e2fsck 1.43.5 (04-Aug-2017)
ext2fs_open2: Bad magic number in super-block
fsck.ext4: Superblock invalid, trying backup blocks...
fsck.ext4: Bad magic number in super-block while trying to open /dev/sdc3

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>