i made a fsck and lost the system
4 Attachment(s)
Hi everyone...
I have 2 hds, and they are like that: sda debian kde sdb debian xfce + XP Using sdb as main system, i UNMOUNt the sda and give this commmand: fsck.ext4 /dev/sda1 tune2fs /dev/sda1 Well, after that, now sda and XP (in sdb) works, BUT XFCE in SDB does not... Appears messages in BOTH systems...the messages that appears in both are something about READ DMA (see picture...) In sda, after a while, the system enters...in the sdb, stops in something like initramfs (see picture) In boot, grub still shows me all systems... As advice someone tells me to use testdisk...well, i didnt know how to use it... Someone can help me? |
You have a disk with at least one bad sector. testdisk is not the right tool for dealing with that. Take a look at the smartmontools Bad Block HOWTO. From the messages in the thumbnails, sector 6146 is bad, and that is in some file in partition sdb1. I would need to see the output from "fdisk -l /dev/sdb" to proceed.
|
Sorry, slightly off-topic: I have to know - why two partitions just for different DEs? I'd imagine those are easily switchable within the same installation.
|
Quote:
|
Hi everyone...
Ondoho: I had two different distros in different hds just for in case happens what happened...in case i lost one of them...:) Rknichols: Here is the output: #fdisk -l /dev/sdb Disco /dev/sdb: 1,4 TiB, 1500301910016 bytes, 2930277168 setores Unidades: setor de 1 * 512 = 512 bytes Tamanho de setor (lógico/físico): 512 bytes / 512 bytes Tamanho E/S (mínimo/ótimo): 512 bytes / 512 bytes Tipo de rótulo do disco: dos Identificador do disco: 0x00085ecc Dispositivo Inicializar Início Fim Setores Tamanho Id Tipo /dev/sdb1 * 2048 1459095551 1459093504 695,8G 83 Linux /dev/sdb2 1459103625 2918175119 1459071495 695,8G 7 HPFS/NTFS/exFAT /dev/sdb3 2918191104 2930276351 12085248 5,8G 82 Linux swap / Solari root@linux2:/home/linux2# |
OK, let's start going through the steps in the HOWTO. Assuming that /dev/sdb1 is another ext2/3/4 filesystem (I know -- bad to assume. Is it??), run (as root)
Code:
tune2fs -l /dev/sdb1 | grep Block Code:
debugfs /dev/sdb1 Hopefully you can follow the subsequent steps in the HOWTO from there. If not, post the results from the above, and I'll try to help a bit more. |
Unfortunatelly, something went wrong:
# tune2fs -l /dev/sdb1 | grep Block Block count: 182386688 Block size: 4096 Blocks per group: 32768 root@linux2:/home/linux2# debugfs /dev/sdb1 debugfs 1.42.5 (29-Jul-2012) debugfs: testb 512 Block 512 marked in use debugfs: icheck 512 icheck: Attempt to read block from filesystem resulted in short read while calling ext2fs_block_iterate Block Inode number 512 <block not found> debugfs: Didnt find in how to this issue... Dumb question: what happens if i give this commands? e2fsck -f /dev/sdb1 e2fsck -f -b 8193 /dev/sdb1 * (i dunno if i use 8193 or 16384 or 32768) in case of use this command... |
Quote:
Quote:
Let's see how bad this drive might be. Post the output from Code:
smartctl -A /dev/sdb You will probably need to get another disk drive at least as large as this one and use ddrescue to make an image of the sectors that can be recovered. You can find ddrescue plus a lot of other useful tools on SystemRescueCD. |
Here is:
Code:
smartctl -A /dev/sdb |
Quote:
You need to recover as much as possible by using ddrescue to make an image onto a new disk. You could then zero out the entire disk, which should cause all the bad sectors to be remapped, and then see what shape the disk is in by looking at parameter 5, "Reallocated_Sector_Ct", but even if it's no more than the 123 known bad sectors, that is too many to consider the drive to be trustworthy. It's still worth taking a look, though. Sometimes sectors are bad due to transient conditions (vibration, power glitch) rather than physical medium faults. Those sectors become "good" (not reallocated) when they are rewritten. Really, you should make a second copy of the image for your recovery work. At some point you're going to have to run fsck on the image, and you shouldn't be doing that on your only good copy. |
Hmmmmmm....
rknichols im reconsidering erase all the partition and install all debian again...its the fast and non-headache option...i already made a backup of all my files i have in that partition, so ill not lose anything. If i install an fresh debian above this one, it will fix this blocks? or have something i have to do before install the new fresh one? Thanx for all the support until now! ;) |
Quote:
What is in that NTFS partition (sdb2)? If you don't want to zero that partition too, you should at least do a quick scan for bad blocks: Code:
dd if=/dev/sdb2 of=/dev/null bs=32k conv=noerror |
All times are GMT -5. The time now is 06:25 PM. |