[1827] in RedHat Linux List

home help back first fref pref prev next nref lref last post

Re: Need RMA or a fix!

daemon@ATHENA.MIT.EDU (Walter B Kulecz PhD)
Wed Oct 30 11:50:15 1996

Date: Wed, 30 Oct 1996 10:43:01 -0600 (CST)
From: Walter B Kulecz PhD <wally@wahine.jsc.nasa.gov>
To: redhat-list@redhat.com
In-Reply-To: <199610300503.AAA21313@redhat.com>
Resent-From: redhat-list@redhat.com
Reply-To: redhat-list@redhat.com

>> Will creating /mnt/etc/fstab and /mnt/etc/lilo.conf by hand and running 
>> /mnt/sbin/lilo fix things? What do I put in lilo.conf? I assume the 
>> standard fstab from 3.0.3 would work.
>
>Yep, will help, at least it did for me.
>
>boot=/dev/hda
>map=/boot/map
>install=/boot/boot.b
>prompt
>timeout=10
>image=/boot/vmlinuz
>        label=linux
>        root=/dev/hda1
>        read-only
>
Doesn't work work form the install RAMDISK system as things are too different
i.e.  no /dev and /boot directories to name but a few.

I created an fstab in /mnt/etc, went back to Alt-F1 console and pressed 
F12 which rebooted the system.  I left the floppy in, interrupted the 
boot and did "boot: linux root=/dev/hda1" what happened next was not pretty.

Tons of inode errors ... prepare for amegedon message .. got dropped into 
"repair filesystem" shell.  I ran fsck /dev/hda1 and it seemed to fix 
what it found, fsck /dev/sdb1 was clean.

The reboot seems to hang on starting innd so I asume the module config 
didn't work to find my NE2000 clone network card.

Lots of [: =: unary operator expected errors from the rc scripts.

Anyone got the phone number or Email address to use to get an RMA?  I don't 
have time to waste on this.  I take a refund and wait for 4.1 or whatever.

To get as far as I got in the install without errors and then bomb lost 
all my confidence.


>Just a question, can you boot off a Syquest disk?  Will lilo install into
>the MBR of a syquest disk as I have told it to above?

Have had no problems with DOS, Win 3.1, WfWg 3.11, Win95, NT 3.5, NT 4.0,
OS/2 3.0, Redhat 2.1 or Slackware 3.0 (from infomagic) from the 7 devices
on the SCSI chain you might guess my strategy, boot from syquest cart,
data/programs on SCSI drive.  The only problem up to now is 128 MB drive 
C: is a bit small for Win95 and NT 4.0  too many stupid install programs 
insist on writing crap to \windows\system.  I got this drive when they 
first came out as I was tired for fighting multiboot install problems.  
Been salvation up to now.  Too bad the EZ230 wasn't their initial 
offering, I tend to doubt Syquest will be around much longer.

The lilo you suggest (except for the /boot/) entries is basically what I 
had for Slackware test install.
  
--wally.



--
  PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
  ________________________________________________________________________
  http://www.redhat.com/RedHat-FAQ   http://www.redhat.com/RedHat-Errata
  http://www.redhat.com/RedHat-Tips  http://www.redhat.com/mailing-lists
  ------------------------------------------------------------------------
To unsubscribe: mail -s unsubscribe redhat-list-request@redhat.com < /dev/null


home help back first fref pref prev next nref lref last post