Re: SCSI Problem!!

[Adinda Praditya <abdmalik mail1 cso ui ac id>]

> 		Hello Adinda,
> 
> > But when i tried to set my sound, from 'setup' menu, i
> > found an error. This is the error message i got:
> >  ATAPI device hdd:
> >  end_request: I/O error, dev 16:40 (hdd), sector 1354368
> 
>  This is not a SCSI error, but an error with your ATAPI (=IDE) CDrom. As far 
> as I can see your problem is either:
> 1) You are trying to mount an audio CD, which is impossible
> 2) The IDE cable on your CDrom is not connected correctly
> 3) The CD disk is bad
> 4) The CD player is bad

These are not a problem for me. Actually the error message i sent before i
got from a replied mail from my friend. this is the original one :

----
ATAPI device hdd:
  Error: Unit attention -- (Sense key=0x06)
  Power on, reset or bus device reset occurred -- (asc=0x29, ascq=0x00)
  hdd: irq timeout: status=0xd0 { Busy }
  hdd: ATAPI reset complete
  end_request: I/O error, dev 16:40 (hdd), sector 1354368
  ATAPI device hdd:
  Error: Unit attention -- (Sense key=0x06)
  Power on, reset or bus device reset occurred -- (asc=0x29,
ascq=0x00)timeout: status=0xd0 { Busy } }
  hdd: ATAPI reset complete
  end_request: I/O error, dev 16:40 (hdd), sector 1354376
  ATAPI device hdd:ention -- (Sense key=0x06)
  Error: Unit attention -- (Sense key=0x06)red -- (asc=0x29, ascq=0x00)
  Power on, reset or bus device reset occurred -- (asc=0x29, ascq=0x00)
---

> 
> > My friend told me to do these:
> >   1. boot: INIT 1.
> >   2. Unmount /dev/sda5 (its mount point is /)
> >   3. run 'e2fsck /dev/sda5
> > 
> > And I did them all. When i did no. 3, it said "/dev/sda5: clean, xxxx/xxxx
> > files ....." then i 'mount' it said ..."already mounted, ... according
> > to .... is mounted on ...." Did i do wrong when i did No. 2?
> 
>  The command should be umount /dev/sda5. Then again, you cannot unmount your / 
> filesystem, since the system is running from that. You have been running fsck 
> on a live filesystem. Not such a good idea. Didn't you get any warnings?

Yes, i run 'umount /dev/sda5. No, i didn't get it. For addition, here is
my fstab: 
---
/dev/sda5               /                       ext2    defaults        1
1
/dev/sda6               /backup                 ext2    defaults        1
2
/dev/sda1               /boot                   ext2    defaults        1
2
/dev/cdrom              /mnt/cdrom              iso9660 noauto,owner,ro 0
0
/dev/hda1               /mnt/praditya1          vfat    defaults        0
0
/dev/fd0                /mnt/floppy             auto    noauto,owner    0
0
none                    /proc                   proc    defaults        0
0
none                    /dev/pts                devpts  gid=5,mode=620  0
0
/dev/sda7               swap                    swap    defaults        0
0
/dev/hdc1	/mnt/data	vfat	 user,exec,dev,suid,rw 1 1
----


>  If you want to fsck your / you could mark the filesystem as dirty, so it will 
> be checked at boot. A *crude* way to do this is to sync the filesystem a 
> couple of times and switch the computer off. This is best done from the 
> command line and not from X. Make sure nothing is written to disk before the 
> syncs and the power down. By the way, I am not responisble for any data loss 
> that might occur due to this dirty trick :).
>  Of course you can also fsck /dev/sda5 from a rescue system. Try booting from 
> the installation CD. This is definitely a neater way to proceed.

How can i do that? tell me step by step.
 
the folowing i'll try them. i'll let you know. thanks for your help.

> > When i tried to set back the run level, the /etc/inittab is read-only! How
> > can i get back to run level 3 or 5? Any suggestion?
 
>  You didn't mention you edited your /etc/inittab. You could have just issued a 
> init 1. I also don't understand why your inittab would be readonly, except 
> maybe after the fsck on the live filesystem. Check file permissions, or try to 
> edit the file from a rescue system. You could just try issueing a init 3 and 
> see if your filesystem is now writable.
> 
> > When i installed LILO (during
> > the RH installation) i set it on MBR. It Shows "LI" only.
> 
>  This might be a SCSI/IDE problem. Can you boot from SCSI? Look at man 
> lilo.conf and check for the parameters "disk=" and "bios=". You might have to 
> enter an entry such as
> disk=/dev/sda
> bios=0x80
> Or there might be something wrong with your disk geometry settings. Check your 
> BIOS settings. Maybe the option "linear" in lilo.conf might help. And check 
> that your /boot partition is below the 1024th cylinder (unless you use a 
> recent lilo (not the one on RedHat 6.2).
>  If things don't work out, be a little more specific about your system 
> parameters (what kind of hd's/sd's, lilo.conf, SCSI adapter, etc.).
> 
> 					Bye,
> 
> 					Leonard.
> 
> 
> 
> _______________________________________________
> Redhat-install-list mailing list
> Redhat-install-list redhat com
> https://listman.redhat.com/mailman/listinfo/redhat-install-list
>