[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: RH 9 install - can I use fdisk within the install program?



Rick,
   Great set of instructions. I'll be working on this tomorrow and will
report back how it goes.

Thanks very much,
Mark

On Mon, 2003-06-30 at 15:57, Rick Stevens wrote:
> Mark Knecht wrote:
> >>Disk druid may not support "simulated" SCSI drives (like the 1394).
> >>That requires the "sg" driver.  You could install and use fdisk to
> >>partition it, as you said fdisk sees it.
> > 
> > 
> > Is this a driver that can be somehow passed to Linux Install at the command
> > line so that it could see the 1394 drive?
> 
> It's already there, since fdisk can see the drive.  I don't think disk
> druid will talk to "sg" drives.  You can install and use fdisk to do
> the partitioning rather than DD and since fdisk _can_ see the drive, you
> may get by that way.
> 
> > One other thought. The machine already has everything on the EIDE drive. Can
> > I somehow just copy the partitions from the EIDE drive to the 1394 drive,
> > and then make a new fstab file that replaces hda5 with sda3, etc? I might
> > have to blow away /var or something, but that wouldn't bother me at all.
> 
> I think that'd work.  You may have to rebuild the initrd image and
> force-feed it the sg driver because once the basic system comes up, it
> will "pivotroot" to /, and since that's on the 1394 drive, you'll need
> the sg driver to see it.
> 
> After building the system and copying your /, /usr, and /var to the 1394
> drive, do an "lsmod" and get a list of all the modules needed for the
> 1394 to work, then rebuild initrd via:
> 
> 	cd /boot
> 	mkinitrd -f [--with=module ] initrd-version.img version
> 
> e.g.
> 
> 	mkinitrd -f --with=sg --with=sr_mod initrd-2.4.20-9.img 2.4.20-9
> 
> 
> (repeat the "--with=" for each module you think you need).  mkinitrd is
> supposed to read /etc/modules.conf (to include any SCSI modules you
> need) and /etc/fstab (to get a list of modules necessary to support
> the root filesystem, e.g. ext3 and such) before writing the image, but
> I don't know how reliable that is.  You can also add a "-v" to get it to
> spew messages about what it's doing and make sure the needed modules get
> in there.
> 
> > I know nothing of doing this, other than the standard part of starting Linux
> > where it asks you if you want to do things like this...
> > 
> > 
> >>I think it's an "sg" issue, not a SCSI issue (I've installed HUNDREDS of
> >>RHs on SCSI drives).
> > 
> > 
> > I'll do some googling. Thanks!
> 
> Good luck, kemosabe!
> ----------------------------------------------------------------------
> - Rick Stevens, Senior Systems Engineer     rstevens vitalstream com -
> - VitalStream, Inc.                       http://www.vitalstream.com -
> -                                                                    -
> - If at first you don't succeed, quit. No sense being a damned fool! -
> ----------------------------------------------------------------------
> 
> 
> _______________________________________________
> Redhat-install-list mailing list
> Redhat-install-list redhat com
> https://www.redhat.com/mailman/listinfo/redhat-install-list
> To Unsubscribe Go To ABOVE URL or send a message to:
> redhat-install-list-request redhat com
> Subject: unsubscribe




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]