Hallo,
Habe hier eine Hitachi Deskstar HDT725032VLA360 welche laufend die
partitionen verliert. Sie wurde bereits zweimal ausgetauscht (von LDLC
in Paris) und nun kommt sie von Hitachi zurück (Die PLatte ist nicht
defekt) und macht mit den problemen weiter.
Es spielt keine rolle, an welchem SATA controller ich sie habe.
AsusTek A7V600-X
VIA EPIA LN10000EAG
MSI K9N SLI-2F
USB2.0/SATA Adapter
Die Platte sieht so aus:
----[ command 'cfdisk /dev/sdb' ]---------------------------------------
cfdisk 2.12p
Disk Drive: /dev/sdb
Size: 320072933376 bytes, 320.0 GB
Heads: 255 Sectors per Track: 63 Cylinders: 38913
Name Flags Part Type FS Type [Label] Size (MB)
-----------------------------------------------------------------------------
sdb1 Boot Primary Linux ext2 [Debian_Rescue] 1003,49
sdb2 Primary Linux swap / Solaris 1003,49
sdb3 Primary Linux ext3 [Temp] 10001,95
sdb5 Logical Linux ext3 [Debian_Prod_1] 1998,75
sdb6 Logical Linux ext3 [Debian_Prod_1log] 1003,49
sdb7 Logical Linux ext3 [Debian_Prod_2] 1998,75
sdb8 Logical Linux ext3 [Debian_Prod_2log] 1003,49
sdb9 Logical Linux ext3 [Debian_Webspace] 29997,60
sdb10 Logical Linux ext3 [Debian_Xmms] 29997,60
sdb11 Logical Linux ext2 [Debian_Rel_old] 29997,60
sdb12 Logical Linux ext2 [Debian_Rel_new] 29997,60
sdb13 Logical Linux ext2 [Debian_Archive] 182066,58
[Bootable] [ Delete ] [ Help ] [Maximize] [ Print ] [ Quit ]
[ Type ] [ Units ] [ Write ]
Toggle bootable flag of the current partition
------------------------------------------------------------------------
Nun kann ich nach einem Neustart des Rechners nicht mehr /dev/sdb1
booten, bzw., /dev/sdb11m /dev/sdb12 und /dev/sdb13 mounten.
----[ STDIN ]-----------------------------------------------------------
tp570:/media/sdb# fsck.ext3 -f -c /dev/sdb1
e2fsck 1.37 (21-Mar-2005)
Checking for bad blocks (read-only test): done 932
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Debian_Rescue: ***** FILE SYSTEM WAS MODIFIED *****
Debian_Rescue: 12/100800 files (0.0% non-contiguous), 12905/979932 blocks
tp570:/media/sdb# fsck.ext3 -f -c /dev/sdb11
e2fsck 1.37 (21-Mar-2005)
Can't find external journal
tp570:/media/sdb# fsck.ext3 -f -c /dev/sdb12
e2fsck 1.37 (21-Mar-2005)
Superblock has a bad ext3 journal (inode 8).
Clear<y>? yes
*** ext3 journal has been deleted - filesystem is now ext2 only ***
Checking for bad blocks (read-only test): done 496
Pass 1: Checking inodes, blocks, and sizes
Journal inode is not in use, but contains data. Clear<y>? yes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(240--246) -503
Fix<y>? yes
Free blocks count wrong for group #0 (7962, counted=7970).
Fix<y>? yes
Free blocks count wrong (24598098, counted=24598106).
Fix<y>? yes
Debian_Rel_new: ***** FILE SYSTEM WAS MODIFIED *****
Debian_Rel_new: 61223/3003840 files (0.4% non-contiguous), 4696390/29294496 blocks
tp570:/media/sdb# fsck.ext3 -f -c /dev/sdb13
e2fsck 1.37 (21-Mar-2005)
Can't find external journal
------------------------------------------------------------------------
Die Frage ist, wie mache ich auf /dev/sdb11 und /dev/sdb13 eine fsck,
wenn fsck behauptet, ich hätte ein EXTERNES Journal welches es nicht
finden kann.
Ich habe keine Option gefunden, ein fsck zu erzwingen wenn so ein Fehler
auftritt...
Irgendwelche Ideen?
Beim mounten siehts so aus:
----[ STDIN ]-----------------------------------------------------------
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
mount: wrong fs type, bad option, bad superblock on /dev/sdb11,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
mount: wrong fs type, bad option, bad superblock on /dev/sdb12,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
mount: wrong fs type, bad option, bad superblock on /dev/sdb13,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
------------------------------------------------------------------------
und
----[ command 'df -m' ]-------------------------------------------------
Filesystem 1M-blocks Used Available Use% Mounted on
/dev/hda1 1875 1768 12 100% /
/dev/hda5 1875 1756 119 94% /home
/dev/hda6 6544 6544 1 100% /home2
/dev/hda3 938 937 1 100% /home3
/dev/sdb3 9532 9 9047 1% /media/sdb/3
/dev/sdb5 1876 9 1773 1% /media/sdb/5
/dev/sdb6 942 9 886 1% /media/sdb/6
/dev/sdb7 1876 9 1773 1% /media/sdb/7
/dev/sdb8 942 9 886 1% /media/sdb/8
/dev/sdb9 27996 33 26533 1% /media/sdb/9
/dev/sdb10 28576 10532 16614 39% /media/sdb/10
------------------------------------------------------------------------
Thanks, Greetings and nice Day/Evening
Michelle Konzack
--
Linux-User #280138 with the Linux Counter, http://counter.li.org/
##################### Debian GNU/Linux Consultant #####################
Michelle Konzack Apt. 917 ICQ #328449886
+49/177/9351947 50, rue de Soultz MSN LinuxMichi
+33/6/61925193 67100 Strasbourg/France IRC #Debian (irc.icq.com)
Attachment:
signature.pgp
Description: Digital signature