On Tue, 2006-02-21 at 11:01 +0700, Amrit Angsusingh wrote: > 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? You might check jumper settings on all drives. I have had good luck with modern drives and cables with using cable select for the drive jumpering. Others say that all drives should be jumpered to master/slave even when using the CS cables. If a drive is attached to the end connection of a CS cable (black connector) it must be jumpered to master or CS. Similarly if connected to the middle connector (usually grey) if must be jumpered to slave or CS. Those connectors are wired as master (end) and slave (middle) so the jumpering must match. I recommend always using CS for the drive jumpering based on my experience with some problems seen when using master/slave jumpering on the CS cables. YMMV > > 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 line > dev/hdd1 /mnt/idedisk1 auto amconsole,exec,noauto,managed > 0 0 > and the fourth system will be read only and could not be unmount. > Amrit This certainly seems like a problem addressing the drive and may be jumper related or drive/cable related.
