I do the mkfs again and here is the result of mkfs
-------------------------------------------
[root@web ~]# umount /backup
[root@web ~]# mkfs -V -t ext3 /dev/hdd1
mkfs version 2.12a (Oct 19 2004)
mkfs.ext3 /dev/hdd1
mke2fs 1.35 (28-Feb-2004)
max_blocks 4294967295, rsv_groups = 0, rsv_gdb = 1024
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
24428544 inodes, 48839600 blocks
2441980 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=50331648
1491 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
[root@web ~]# mkfs -V -t ext3 /dev/hdd1
mkfs version 2.12a (Oct 19 2004)
mkfs.ext3 /dev/hdd1
mke2fs 1.35 (28-Feb-2004)
max_blocks 4294967295, rsv_groups = 0, rsv_gdb = 1024
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
24428544 inodes, 48839600 blocks
2441980 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=50331648
1491 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Writing inode tables: done
ext2fs_mkdir: Attempt to read block from filesystem resulted in short read while creating root dir
-----------------------
After I do this I cannot mount or fdisk the /dev/hdd1.
[root@web /]# mount -t ext3 /dev/hdd1 /backup1
mount: mount point /backup1 does not exist
[root@web /]# mount -t ext3 /dev/hdd1 /backup
mount: wrong fs type, bad option, bad superblock on /dev/hdd1,
or too many mounted file systems
[root@web /]# fdisk /dev/hdd
Unable to read /dev/hdd
[root@web /]#
------------------------------------
What happen to me? Any suggestion.
Amrit
Writing inode tables: done
ext2fs_mkdir: Attempt to read block from filesystem resulted in short read while creating root dir
[root@web ~]#
2006/2/21, Amrit Angsusingh <amritangs@xxxxxxxxx>:
Although I certainly sure that I do already use the fdisk and mkfs on Hdd , I will do it again. But is there any other reason for that for ex. setting jumper on hdd?After I do 'mkfs' it and set the fstab to ext3 then I reboot the system , the FC3 cannot mount the /dev/hdd1 and the system hang up for a long time [more than 1/2 hour] and it asked for root password to enter the system to recover and I must marked the fstab /dev/hdd1 and then reboot , the server will boot properly but the fstab will then automatically create the linedev/hdd1 /mnt/idedisk1 auto amconsole,exec,noauto,managed 0 0and the fourth system will be read only and could not be unmount.
Amrit
2006/2/21, Bruno Wolff III <bruno@xxxxxxxx>:On Mon, Feb 20, 2006 at 23:53:47 +0700,
Amrit Angsusingh < amritangs@xxxxxxxxx > wrote:
> I used pentium 4 mechine with 256 Mb ram and fedora core 3 for web server
> and four IDE HDDs [160 Gbx4] on both primary ans secondary IDE. The bios
> also detected all 4 HDD but after starting FC3 the system mount secondary
> slave HDD /dev/hdd1 as /mnt/idedisk1
> /dev/hda1 / ext3 defaults 1 1
> none /dev/pts devpts gid=5,mode=620 0 0
> none /dev/shm tmpfs defaults 0 0
> /dev/hdc1 /mec ext3 defaults 1 2
> none /proc proc defaults 0 0
> none /sys sysfs defaults 0 0
> /dev/hdb1 /var ext3 defaults 1 2
> /dev/hda2 swap swap defaults 0 0
>
> /dev/hdd1 /mnt/idedisk1 auto amconsole,exec,noauto,managed 0 0
>
> which appeared to be the read only device. I cannot umount this device and
> mount it to /dev/hdd1 ext3 . I would like to use this HDD to store the
> nackup data. Does any one tell me how to do this?
Have you put a file system on it yet? If not you can use mkfs to do that.
--
Amrit Angsusingh
Thailand
--
Amrit Angsusingh
Thailand
