e2fsck ignores the existence of backup super blocks

Asked by Bougron on 2018-05-14

I got this error message:

ubuntu@ubuntu:~$ sudo e2fsck -fn /dev/sda1
e2fsck 1.42.13 (17-May-2015)
e2fsck: La tentative de lecture d'un bloc depuis le système de fichiers a produit une lecture tronquée lors de la tentative d'ouverture de /dev/sda1
Peut-être cette partition est-elle de taille zéro ?
( Attempting to read a block from the file system caused a truncated read when attempting to open / dev / sda1
Maybe this partition is zero size? )

I did not know what to do. But a very competent person told me to make this order.
sudo mount -r -t ext4 -o sb=$((32768*4)) /dev/disk/by-id/ata-MAXTOR_STM3160215A_9RA8V0BK-part1 /mnt

This solved the problem

Why e2fsck did not think to do it?
having been unable to read the first super-block to think of automatically accessing the next block and using it for repair, and so on.
it is only that the last super block does not solve the problem that it should tell me that the repair is not possible,

In information, he could tell me he had to loop N times before finding a good super block and advise me to have the condition of the disk checked.

Probably the same error in the MOUNT command?

I got this error message:

ubuntu@ubuntu:~$ sudo e2fsck -fn /dev/sda1
e2fsck 1.42.13 (17-May-2015)
e2fsck: La tentative de lecture d'un bloc depuis le système de fichiers a produit une lecture tronquée lors de la tentative d'ouverture de /dev/sda1
Peut-être cette partition est-elle de taille zéro ?
( Attempting to read a block from the file system caused a truncated read when attempting to open / dev / sda1
Maybe this partition is zero size?)

I did not know what to do.

but a very competent person told me to make this order.
sudo mount -r -t ext4 -o sb=$((32768*4)) /dev/disk/by-id/ata-MAXTOR_STM3160215A_9RA8V0BK-part1 /mnt
This solved the problem

Why e2fsck did not think to do it?
having been unable to read the first super-block to think of automatically accessing the next block and using it for repair, and so on.
it is only that the last super block does not solve the problem that it should tell me that the repair is not possible,

In information, he could tell me he had to loop N times before finding a good super block and advise me to have the condition of the disk checked.

probably the same error in the MOUNT command?

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
2018-05-14
Last reply:
2018-05-14

I suggest you report a bug

Can you help with this problem?

Provide an answer of your own, or ask Bougron for more information if necessary.

To post a message you must log in.