El 16 de mayo de 2015 12:43:14 CEST, "Manolo Díaz" <diaz.man...@gmail.com> escribió: >El sábado, 16 may 2015, a las 12:27 UTC+2 horas, >Ramses II escribió: > >>Hola a todos, >> >>Estoy intentando montar una partición de una tarjeta SD que me ha >dejado de >>arrancar el sistema y me da el siguiente error: >> >>---------------------------------------------------------------------------- >>------------------------------ >>root@proxmox:/mnt# mount /dev/sdd6 /mnt/sd >>mount: wrong fs type, bad option, bad superblock on /dev/sdd6, >> missing codepage or helper program, or other error >> In some cases useful info is found in syslog - try >> dmesg | tail or so >> >>root@proxmox:/mnt# >>---------------------------------------------------------------------------- >>------------------------------ >> >>El dmesg me da lo siguiente: >> >>---------------------------------------------------------------------------- >>------------------------------ >>root@proxmox:/mnt# dmesg | tail >>EXT4-fs error (device sdd6): ext4_iget: bad extended attribute block >>2147483648 inode #8 >>EXT4-fs (sdd6): no journal found >>root@proxmox:/mnt# >>---------------------------------------------------------------------------- >>------------------------------ >> >>¿Me podría orientar alguien si podría solucionar ese error de alguna >forma >>para poder montar la partición y sacarle los datos? >> >> >>Saludos y gracias, >> >>Ramses > >fsck /dev/sdd6 antes de montarla. Posiblemente tenga que repararla. En >ese caso te pide confirmación antes de realizar cambios.
Manolo, no me atrevía a ejecutar el comando, por si había alguna otra solución, pero al habérmelo dicho tú, le he echado "eggs", pero se me han abierto ahora las carnes: --------------- root@proxmox:~# fsck /dev/sdd6 fsck from util-linux 2.20.1 e2fsck 1.42.5 (29-Jul-2012) Superblock has an invalid journal (inode 8). Clear<y>? yes *** ext3 journal has been deleted - filesystem is now ext2 only *** root contains a file system with errors, check forced. Resize inode not valid. Recreate<y>? yes fsck.ext4: Illegal doubly indirect block found while reading bad blocks inode This doesn't bode well, but we'll try to go on... Pass 1: Checking inodes, blocks, and sizes The bad block inode looks invalid. Clear<y>? yes Inode 2 has a extra size (284) which is invalid Fix<y>? yes Error while reading over extent tree in inode 2: Corrupt extent header Clear inode<y>? yes Inode 2 is a zero-length directory. Clear<y>? yes Quota inode is not in use, but contains data. Clear<y>? yes Quota inode is not in use, but contains data. Clear<y>? yes Reserved inode 5 (<The boot loader inode>) has invalid mode. Clear<y>? yes Inode 5, i_blocks is 264192, should be 0. Fix<y>? yes Inode 6 has a bad extended attribute block 64. Clear<y>? yes Journal inode is not in use, but contains data. Clear<y>? yes Inode 9, i_size is 288230376151712768, should be 0. Fix<y>? yes Inode 9, i_blocks is 1024, should be 0. Fix<y>? yes Inode 10 has a bad extended attribute block 320. Clear<y>? yes Inode 10 has INDEX_FL flag set but is not a directory. Clear HTree index<y>? yes Inode 10, i_size is 9007199254749312, should be 0. Fix<y>? yes Inode 10, i_blocks is 70377334374400, should be 0. Fix<y>? yes Inode 11 has a bad extended attribute block 90113. Clear<y>? yes Error while reading over extent tree in inode 11: Corrupt extent header Clear inode<y>? yes Inode 11 is a zero-length directory. Clear<y>? yes Inode 13 is in use, but has dtime set. Fix<y>? yes Error while reading over extent tree in inode 13: Corrupt extent header Clear inode<y>? yes Inode 13, i_blocks is 70368760955081, should be 0. Fix<y>? yes Inode 14 has a bad extended attribute block 8224. Clear<y>? yes Error while reading over extent tree in inode 14: Corrupt extent header Clear inode<y>? yes Inode 14, i_size is 9297751799451150084, should be 0. Fix<y>? yes Inode 14, i_blocks is 140748762652776, should be 0. Fix<y>? yes Inode 15 is in use, but has dtime set. Fix<y>? yes Error while reading over extent tree in inode 15: Corrupt extent header Clear inode<y>? yes Inode 15, i_blocks is 67596, should be 0. Fix<y>? yes Inode 16 is in use, but has dtime set. Fix<y>? yes Inode 16 has a extra size (32796) which is invalid Fix<y>? yes Error while reading over extent tree in inode 16: Corrupt extent header Clear inode<y>? yes Inode 16, i_blocks is 21475889392, should be 0. Fix<y>? yes Inode 17 is in use, but has dtime set. Fix<y>? yes Inode 17, i_size is 292808742838331200, should be 0. Fix<y>? yes Inode 17, i_blocks is 4398047559913, should be 0. Fix<y>? yes Inode 18 is in use, but has dtime set. Fix<y>? yes Inode 19 is in use, but has dtime set. Fix<y>? yes Error while reading over extent tree in inode 19: Corrupt extent header Clear inode<y>? yes Inode 19, i_blocks is 75530872, should be 0. Fix<y>? yes Inode 20 is in use, but has dtime set. Fix<y>? yes Inode 21 is in use, but has dtime set. Fix<y>? yes Inode 21 has a extra size (156) which is invalid Fix<y>? yes Inode 21 has a bad extended attribute block 576. Clear<y>? yes Inode 21 has an invalid extent (logical block 32768, invalid physical block 142098992988167, len 4294934535) Clear<y>? yes Inode 21 has INDEX_FL flag set but is not a directory. Clear HTree index<y>? yes Inode 21, i_size is 2314850208468463228, should be 0. Fix<y>? yes Inode 21, i_blocks is 696, should be 0. Fix<y>? yes Inode 22 is in use, but has dtime set. Fix<y>? yes Inode 22 has a extra size (2078) which is invalid Fix<y>? yes Error while reading over extent tree in inode 22: Corrupt extent header Clear inode<y>? yes Inode 22, i_blocks is 4198448, should be 0. Fix<y>? yes Inode 23 is in use, but has dtime set. Fix<y>? yes Error while reading over extent tree in inode 23: Corrupt extent header Clear inode<y>? yes Inode 23, i_blocks is 4194640, should be 0. Fix<y>? yes Inode 24 is in use, but has dtime set. Fix<y>? yes Inode 24 has a bad extended attribute block 8. Clear<y>? yes Error while reading over extent tree in inode 24: Corrupt extent header Clear inode<y>? yes Inode 24, i_blocks is 88, should be 0. Fix<y>? yes Inode 25 is in use, but has dtime set. Fix<y>? yes Error while reading over extent tree in inode 25: Corrupt extent header Clear inode<y>? yes Inode 25, i_blocks is 140737488617492, should be 0. Fix<y>? yes Error while reading over extent tree in inode 26: Corrupt extent header Clear inode<y>? yes Inode 26, i_blocks is 2199023272050, should be 0. Fix<y>? yes Inode 27 is in use, but has dtime set. Fix<y>? yes Inode 27 has compression flag set on filesystem without compression support. Clear<y>? yes Error while reading over extent tree in inode 27: Corrupt extent header Clear inode<y>? yes Inode 27, i_size is 11601273189866522996, should be 0. Fix<y>? yes Inode 27, i_blocks is 309271464040, should be 0. Fix<y>? yes Inode 28 is in use, but has dtime set. Fix<y>? yes Inode 28 has an invalid extent (logical block 37748736, invalid physical block 551098024514, len 258) Clear<y>? yes Inode 28, i_blocks is 51540000784, should be 0. Fix<y>? no Error while reading over extent tree in inode 29: Corrupt extent header Clear inode<y>? Recreate journal<y>? cancelled! root: e2fsck canceled. root: ***** FILE SYSTEM WAS MODIFIED ***** root: ********** WARNING: Filesystem still has errors ********** root@proxmox:~# --------------- Y he cortado el proceso con Control + C. No sé si seguir o... Saludos y gracias, Ramses Buenas, -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/daf8cf02-a4be-43b5-8858-e51eaea49...@gmail.com