2st Kraschade hårddiskar sammtidigt.

[gislemark]

När jag efter helgen kom hem och skulle starta min dator så ville den inte ladda Ubuntu.

Jag testade att starta med skiva. - Den fungerade inte heller.
Testade att plocka ur alla expantionskort- ingen skillnad.
Jag testade att plocka ur min ena hårddisk, den utan operativsystem.- Ingen skillnad.
Jag tog ur båda håddiskarna - Ubuntu startade med skiva.
Jag satte tillbax min första hårddisk igen. - Ubuntu startar med skiva. Ubuntu raporterar "Disk has a few bad sectors"

Får även fram föjande felkod:
Error mounting: mount exited with exit code 32: mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

Så nu sitter jag med 2 st värdelösa hårddiskar.
Går den att rädda?
Eller måste jag köpa en ny?

[webaake]

Kanske du kan pröva att boota från Live CD'n och öppna en terminal och köra kommandot;

Kod: Markera allt

sudo e2fsck -f -y -v -C0 -D /dev/hdd1

Byt ut /dev/hdd1 mot det du har. I terminalprogrammet kan du få fram det med

Kod: Markera allt

sudo fdisk -l

. e2fsck är det samma som chkdsk fast mycket bättre.

Osannolikt att två HD pajar samtidigt.

[gislemark]

Kanske du kan pröva att boota från Live CD'n och öppna en terminal och köra kommandot;

Kod: Markera allt

sudo e2fsck -f -y -v -C0 -D /dev/hdd1

Byt ut /dev/hdd1 mot det du har. I terminalprogrammet kan du få fram det med

Kod: Markera allt

sudo fdisk -l

. e2fsck är det samma som chkdsk fast mycket bättre.

Osannolikt att två HD pajar samtidigt.

Jag kör Ubuntu från skivan, det fungerar utmärkt.
Jag har för tillfället endast en hårddisk inkopplad pga att när den andra är inkopplad vägrar Ubuntu att starta ifrån skiva.

Jag körde kommandona som du beskrev. Jag fick följande resultat.

Kod: Markera allt

ubuntu@ubuntu:~$ sudo fdisk -l

Disk /dev/sda: 82.3 GB, 82348277760 bytes
255 heads, 63 sectors/track, 10011 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x24af24ae

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1       10011    80413326    0  Empty

Disk /dev/sdb: 239 MB, 239337472 bytes
16 heads, 32 sectors/track, 913 cylinders
Units = cylinders of 512 * 512 = 262144 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1         912      233453+   6  FAT16
ubuntu@ubuntu:~$ sudo e2fsck -f -y -v -C0 -D /dev/sda
e2fsck 1.41.9 (22-Aug-2009)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/sda

The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
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>

[Lars]

Det beror på att /dev/sda inte är en partition, använd /dev/sda1 istället.

[gislemark]

Får följande resultata:

Kod: Markera allt

ubuntu@ubuntu:~$ sudo e2fsck -f -y -v -C0 -D /dev/sda11
e2fsck 1.41.9 (22-Aug-2009)
e2fsck: No such file or directory while trying to open /dev/sda11

The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
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>

ubuntu@ubuntu:~$ sudo e2fsck -f -y -v -C0 -D /dev/sda1
e2fsck 1.41.9 (22-Aug-2009)
Error reading block 9994240 (Attempt to read block from filesystem resulted in short read).  Ignore error? yes

Force rewrite? yes

Superblock has an invalid journal (inode 8).
Clear? yes

*** ext3 journal has been deleted - filesystem is now ext2 only ***

Superblock has_journal flag is clear, but a journal inode is present.
Clear? yes

Error reading block 9254 (Attempt to read block from filesystem resulted in short read).  Ignore error? yes

Force rewrite? yes

Resize inode not valid.  Recreate? yes

Pass 1: Checking inodes, blocks, and sizes
Journal inode is not in use, but contains data.  Clear? yes

Pass 2: Checking directory structure                                           
Error reading block 9249 (Attempt to read block from filesystem resulted in short read) while reading directory block.  Ignore error? yes

Force rewrite? yes

Missing '.' in directory inode 2.
Fix? yes

Setting filetype for entry '.' in ... (2) to 2.
Missing '..' in directory inode 2.
Fix? yes

Setting filetype for entry '..' in ... (2) to 2.
Error reading block 9251 (Attempt to read block from filesystem resulted in short read) while reading directory block.  Ignore error? yes

Force rewrite? yes

Error reading block 9252 (Attempt to read block from filesystem resulted in short read) while reading directory block.  Ignore error? yes

Force rewrite? yes

Error reading block 9253 (Attempt to read block from filesystem resulted in short read) while reading directory block.  Ignore error? yes

Force rewrite? yes

Pass 3: Checking directory connectivity                                        
'..' in / (2) is <The NULL inode> (0), should be / (2).                        
Fix? yes

Unconnected directory inode 11 (/???)
Connect to /lost+found? yes

/lost+found not found.  Create? yes

Error reading block 1572864 (Attempt to read block from filesystem resulted in short read) while reading inode and block bitmaps.  Ignore error? yes

Force rewrite? yes

Error reading block 1572865 (Attempt to read block from filesystem resulted in short read) while reading inode and block bitmaps.  Ignore error? yes

Force rewrite? yes

Error reading block 5767168 (Attempt to read block from filesystem resulted in short read) while reading inode and block bitmaps.  Ignore error? yes

Force rewrite? yes

Error reading block 6291456 (Attempt to read block from filesystem resulted in short read) while reading inode and block bitmaps.  Ignore error? yes

Force rewrite? yes

Error reading block 7864320 (Attempt to read block from filesystem resulted in short read) while reading inode and block bitmaps.  Ignore error? yes

Force rewrite? yes

Error reading block 7864323 (Attempt to read block from filesystem resulted in short read) while reading inode and block bitmaps.  Ignore error? yes

Force rewrite? yes

Error reading block 13631488 (Attempt to read block from filesystem resulted in short read) while reading inode and block bitmaps.  Ignore error? yes

Force rewrite? yes

Error reading block 15204352 (Attempt to read block from filesystem resulted in short read) while reading inode and block bitmaps.  Ignore error? yes

Force rewrite? yes

Error reading block 15728640 (Attempt to read block from filesystem resulted in short read) while reading inode and block bitmaps.  Ignore error? yes

Force rewrite? yes

Error reading block 16252928 (Attempt to read block from filesystem resulted in short read) while reading inode and block bitmaps.  Ignore error? yes

Force rewrite? yes

Error reading block 19922949 (Attempt to read block from filesystem resulted in short read) while reading inode and block bitmaps.  Ignore error? yes

Force rewrite? yes

Pass 3A: Optimizing directories                                                
Pass 4: Checking reference counts
Inode 11 ref count is 3, should be 2.  Fix? yes

Pass 5: Checking group summary information                                     
Block bitmap differences:  +(1572864--1581087) +(1605632--1606656) +(5767168--5775391) +(6291456--6299679) +(7864320--7872543) +(7962624--7963648) -(9994240--10027007) +(13631488--13639711) +(15204352--15212575) +(15728640--15736863) +(16252928--16261151)
Fix? yes

Free blocks count wrong for group #0 (23513, counted=23514).                   
Fix? yes

Free blocks count wrong for group #305 (0, counted=32768).
Fix? yes

Free blocks count wrong (19741636, counted=19774405).
Fix? yes

Recreate journal? yes                                                          

Creating journal (32768 blocks):  Done.

*** journal has been re-created - filesystem is now ext3 again ***

/dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****

      12 inodes used (0.00%)
       0 non-contiguous files (0.0%)
       0 non-contiguous directories (0.0%)
         # of inodes with ind/dind/tind blocks: 0/0/0
  361694 blocks used (1.80%)
       0 bad blocks
       0 large files

       0 regular files
       2 directories
       0 character device files
       0 block device files
       0 fifos
4294967295 links
       0 symbolic links (0 fast symbolic links)
       0 sockets
--------
       1 file
Error writing block 98304 (Attempt to write block from filesystem resulted in short write).  Ignore error? yes

Error writing block 294912 (Attempt to write block from filesystem resulted in short write).  Ignore error? yes

Error writing block 819200 (Attempt to write block from filesystem resulted in short write).  Ignore error? yes

Error writing block 2654208 (Attempt to write block from filesystem resulted in short write).  Ignore error? yes

Vad är nästa åtgärd??

[Lars]

Kolla med diskverktyget i Karmic om du har hårdvarufel på diskarna, eller använd smartctl.

Går det att boota från disken nu?

[gislemark]

Kolla med diskverktyget i Karmic om du har hårdvarufel på diskarna, eller använd smartctl.

Går det att boota från disken nu?

Det står:

Disk has 44 bad sectors

[webaake]

Är diskverktyget (Palimpsest) tillförlitligt?

[Lars]

Är diskverktyget (Palimpsest) tillförlitligt?

Det är bara ett grafiskt gränssnitt som läser S.M.A.R.T.-informationen direkt från disken. Om du litar på vad disken rapporterar för fel så kan du också lita på Palimpsest.

[Bowmore]

Man ska nog inte lita fullt ut på Palimpsest med tanke på denna bugg.