by pando87 » Mon Jul 23, 2012 5:43 am
ubuntu@ubuntu:~$ sudo mke2fs -j -m 1 /dev/sdb5
mke2fs 1.42 (29-Nov-2011)
ext2fs_check_if_mount: Input/output error while determining whether /dev/sdb5 is mounted.
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
96256 inodes, 384536 blocks
3845 blocks (1.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=67633152
47 block groups
8192 blocks per group, 8192 fragments per group
2048 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185
Allocating group tables: done
Writing inode tables: done
Creating journal (8192 blocks): mke2fs: Input/output error
while trying to create journal
ubuntu@ubuntu:~$ sudo mke2fs -j -m 1 /dev/sdb5
mke2fs 1.42 (29-Nov-2011)
ext2fs_check_if_mount: Input/output error while determining whether /dev/sdb5 is mounted.
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
96256 inodes, 384536 blocks
3845 blocks (1.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=67633152
47 block groups
8192 blocks per group, 8192 fragments per group
2048 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185
Allocating group tables: done
Writing inode tables: done
Creating journal (8192 blocks): mke2fs: Input/output error
while trying to create journal
ubuntu@ubuntu:~$ sudo fsck -f /dev/sdb5
fsck from util-linux 2.20.1
e2fsck 1.42 (29-Nov-2011)
ext2fs_check_if_mount: Input/output error while determining whether /dev/sdb5 is mounted.
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdb5
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>