redhat 7.0 won't shut down correctly

When shutting down my redhat 7.0 system, it gets to "unmounting mounted devices" and jsut stops.  the hard drive light is going, and i am forced to power it off at the switch as it won't shut down.  I ran fsck (fsck /dev/hdb) and it displayed "parallelizing fsck ..." and then went to a new line and didn't continue.  I don't know exactly when this started, but i am still using the stock kernel (un-modified) that came with redhat 7.0 (2.2.16).  I recently modified the boot process to enable ide-scsi emulation on the cd drive (hdd).  I did so by adding append="hdd=ide-scsi" in teh lilo.conf file and insmod'ing ide-scsi in rc.local.  it also recognizes my zip drive (hdc) as being scsi too now.  any ideas?
Who is Participating?
xberryConnect With a Mentor Commented:
HUh, looks as if you did confuse your kernel with your boot process modifications. What you put into lilo.conf with the ' append ' line ONLY applies to functions that are built INTO the kernel but not to loadable modules. Apart from that: bootparameters starting with hd directly address
harddisks but never CD ROM drives. Technically you told your Computer to emulate SCSI for the second device on your second IDE controller, with the result that
a) your zip drive is misrecognized
b) when the halt script is running the various configuration scripts in order to unmount devices then it will find itself unable to unmount your falsely configured 'SCSI' zip device, thus stopping the process & leaving it ' active ' together with the ide controller & any other device hanging on it.

You should at ANY case remove that false append line in your lilo.conf in order to shut down your system the 'normal' way.

If your ide-scsi emulator does exist as a loadable module then you may leave the insmod line in rc.local for sake of your CD-ROM. I recomend to insert any modules with the ' modprobe ' command though.
blackcAuthor Commented:
it does exist as a loadable module.  the problem is, without the line in the lilo.conf file, the ide-cdrom or whatever the normal ide cd module gets ahold of  the cd first and i can't emulate scsi, and thus can't burn cds.  i have to be able to emulate scsi for my cdrom drive, and i seem to remember that my zipdrive was that way the last time i confgured my redhat 7.0 system.  And it shut down just fine.  how would i modify the closing unmount scripts to unmount the zip as scsi, as opposed to ide?  first i will reboot with the modifications taken out, and see if it shutds down normally.  that'll tell us something i hope.
blackcAuthor Commented:
when i removed those references the system shut down without a problem.  However, i previously tried to recompile my kernel to enable the ide-scsi emulation for the cdrom.  it would get to checking filesystems at boot and just stop.  This method of enabling emulation was given a few days ago on this forum.  I need to burn cds on this machine, but i also need to shut it down.  the most prominant solution to me is to edit the shutdown scripts.  can anyone tell me where they reside?
blackcAuthor Commented:
you didn't really answer the question to my satisfaction (just because then the cd burner wouldn't work) but you did point me in the correct direction.  What i did was to remove both lines starting emulation and reboot.  from a clean system, i mounted the zip drive as an ide device.  it worked.  then i installed the ide-scsi module and ran cdrecord -scanbus.  it only showed my cd drive, the desired results.  i looked at the listed modules, and ide-floppy was loaded for the zip drive.  so in my rc.local file where i installed the ide-scsi emulation, i first installed ide-floppy.   now the zip is recognized as ide, and the cdrw is scsi again.  AND as an added bonus, the system even shuts down properly :-)
And as an extra bonus on top you obviously found an interesting & profound way how to mount an internal IDE zip drive to your system. I've read that IDE Zip drives are rare & no adequate solution given in the howtos. So your solution to mount it as ide-floppy device is a nice surprise & sure a precious contribution to the pool of solutions at EE.  
All in all I'd call that a success, wouldn't you ?

I'm happy because it worked out fine for you.
Thanks a lot.

All Courses

From novice to tech pro — start learning today.