You are not logged in.
Pages: 1
[root@MediaBox angelus]# mkfs -t ext3 /dev/sdb1
mke2fs 1.41.3 (12-Oct-2008)
Dateisystem-Label=
OS-Typ: Linux
Blockgröße=4096 (log=2)
Fragmentgröße=4096 (log=2)
4890624 Inodes, 19543064 Blöcke
977153 Blöcke (5.00%) reserviert für den Superuser
Erster Datenblock=0
Maximale Dateisystem-Blöcke=0
597 Blockgruppen
32768 Blöcke pro Gruppe, 32768 Fragmente pro Gruppe
8192 Inodes pro Gruppe
Superblock-Sicherungskopien gespeichert in den Blöcken:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Schreibe Inode-Tabellen: erledigt
Erstelle Journal (32768 Blöcke): erledigt
Schreibe Superblöcke und Dateisystem-Accountinginformationen: erledigt
Das Dateisystem wird automatisch nach jeweils 26 Einhäng-Vorgängen bzw.
alle 180 Tage überprüft, je nachdem, was zuerst eintritt. Veränderbar mit
tune2fs -c oder -t .[root@MediaBox angelus]# mount /dev/sdb1
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or helper program, or other error
Manchmal liefert das Syslog wertvolle Informationen – versuchen
Sie dmesg | tail oder so[root@MediaBox angelus]# dmesg | tail
sd 3:0:1:0: [sdb] Mode Sense: 00 3a 00 00
sd 3:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdb:
sd 3:0:1:0: [sdb] 156355584 512-byte hardware sectors (80054 MB)
sd 3:0:1:0: [sdb] Write Protect is off
sd 3:0:1:0: [sdb] Mode Sense: 00 3a 00 00
sd 3:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdb: sdb1
JBD: no valid journal superblock found
EXT3-fs: error loading journal.wtf is going on with mkfs and ext3? oO
i can create 10 times and format 10 times /dev/sdb1 but everytime the same error and reinstall e2fsprogs doesn't solve the problem oO
HELP!
Offline
Try this:
# mke2fs -j /dev/sdb1ARCH|awesome3.0 powered by Pentium M 750 | 512MB DDR2-533 | Radeon X300 M
The journey is the reward.
Offline
Try this:
# mke2fs -j /dev/sdb1
[root@MediaBox ~]# mke2fs -j /dev/sdb1
mke2fs 1.41.3 (12-Oct-2008)
Dateisystem-Label=
OS-Typ: Linux
Blockgröße=4096 (log=2)
Fragmentgröße=4096 (log=2)
4890624 Inodes, 19543064 Blöcke
977153 Blöcke (5.00%) reserviert für den Superuser
Erster Datenblock=0
Maximale Dateisystem-Blöcke=0
597 Blockgruppen
32768 Blöcke pro Gruppe, 32768 Fragmente pro Gruppe
8192 Inodes pro Gruppe
Superblock-Sicherungskopien gespeichert in den Blöcken:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Schreibe Inode-Tabellen: erledigt
Erstelle Journal (32768 Blöcke): erledigt
Schreibe Superblöcke und Dateisystem-Accountinginformationen: erledigt
Das Dateisystem wird automatisch nach jeweils 25 Einhäng-Vorgängen bzw.
alle 180 Tage überprüft, je nachdem, was zuerst eintritt. Veränderbar mit
tune2fs -c oder -t .[root@MediaBox ~]# mount /dev/sdb1
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or helper program, or other error
Manchmal liefert das Syslog wertvolle Informationen – versuchen
Sie dmesg | tail oder so
[root@MediaBox ~]#[root@MediaBox ~]# dmesg | tail
padlock: VIA PadLock not detected.
warning: `cdrecord' uses 32-bit capabilities (legacy support in use)
JBD: no valid journal superblock found
EXT3-fs: error loading journal.
[root@MediaBox ~]#Same error again...
Help
Offline
What is the fstab entry for /dev/sdb1?
ARCH|awesome3.0 powered by Pentium M 750 | 512MB DDR2-533 | Radeon X300 M
The journey is the reward.
Offline
What is the fstab entry for /dev/sdb1?
[root@MediaBox ~]# cat /etc/fstab
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/cdrom /mnt/dvd iso9660,udf ro,user,noauto 0 0
/dev/sr1 /mnt/cd iso9660,udf ro,user,noauto 0 0
/dev/fd /mnt/fl vfat user,noauto 0 0
/dev/sda1 swap swap defaults 0 0
/dev/sda2 / ext3 defaults 0 1
/dev/sdb1 /home/angelus/videos/HDD2 ext3 defaults,noatime,data=journal 0 0
[root@MediaBox ~]#Offline
I don't know why it's still corrupt after a fresh format. Maybe someone else will know. I guess you can try to repair it with fsck:
# e2fsck -pvf /dev/sdb1ARCH|awesome3.0 powered by Pentium M 750 | 512MB DDR2-533 | Radeon X300 M
The journey is the reward.
Offline
I don't know why it's still corrupt after a fresh format. Maybe someone else will know. I guess you can try to repair it with fsck:
# e2fsck -pvf /dev/sdb1
[root@MediaBox ~]# e2fsck -pvf /dev/sdb1
11 inodes used (0.00%)
0 non-contiguous inodes (0.0%)
# von Inodes mit ind/dind/tind Blöcken: 0/0/0
352990 blocks used (1.81%)
0 bad blocks
1 large file
0 regular files
2 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
2 files
[root@MediaBox ~]#[root@MediaBox ~]# e2fsck -pvf /dev/sdb1
11 inodes used (0.00%)
0 non-contiguous inodes (0.0%)
# von Inodes mit ind/dind/tind Blöcken: 0/0/0
352990 blocks used (1.81%)
0 bad blocks
1 large file
0 regular files
2 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
2 files
[root@MediaBox ~]# mount /dev/sdb
sdb sdb1
[root@MediaBox ~]# mount /dev/sdb1
[root@MediaBox ~]#mkfs bad? or what?
Offline
Well like I said, I don't know why your initial mke2fs is corrupt, but at least e2fsck seems to have fixed it for you (I think?). Perhaps you should file a bug report for the e2fsprogs maintainer to see/diagnose.
ARCH|awesome3.0 powered by Pentium M 750 | 512MB DDR2-533 | Radeon X300 M
The journey is the reward.
Offline
You might try taking that journal option out of your fstab, seeing if that helps. From what I can see from your dmesg | tail, it can't find a journal, so it can't mount. Try taking that option out of the fstab and see if it helps.
Offline
Pages: 1