SCOUG-HELP Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Sun, 19 Jan 2003 14:38:28 PST8
From:	Harry Chris Motin <hmotin@attglobal.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: Re: Long Boot up Time

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

Thanks, Steven.

_________________________________________________________________________________________

Steven Levine wrote:
>
> =====================================================
> If you are responding to someone asking for help who
> may not be a member of this list, be sure to use the
> REPLY TO ALL feature of your email program.
> =====================================================
>
> In <3E2ACC17.8A872342@attglobal.net>, on 01/19/03
> at 08:02 AM, Harry Chris Motin said:
>
> >OK! I guess we can put that to bed now, based on my timing of the bootup
> >with the changed CONFIG.SYS line for HPFS.IFS
>
> I would agree.
>
> >HD's. I installed a 36 GB SCSI drive as the second unit (D:). Finally, as
> >the last step, I replaced the EIDE HD with a larger 73GB SCSI unit. The
> >bootup has always been slow (~10 minutes) for this computer. It has not
> >mattered what HD's I've used. The (only) advantage of the SCSI's is the
> >significantly better read and write response, compared to EIDE. That has
> >been very noticeable.
>
> OK, so all your disk drives are on the SCSI bus. SCSI drives are
> definitely slower during boot up than during normal operation. I would
> work with the SCSI card and the drivers. Make sure the BIOS is current
> and try a few different versions of the AICU160 driver. There were a
> couple of versions of the driver that used a very slow I/O methods during
> boot up. This was most noticable during chkdsk, but it probably also
> effects boot time.
>
> >I agree. I'll try it, even though the ConfigTool has a warning about data
> >loss for non-default values of CRECL
>
> Yes, I've read that. Just keep it in mind. I'm sure it only effects a
> small subset of systems.
>
> Do you boot the system every day or is it up 24x7? If you are booting
> every day and your data is organized to support it, you might want to
> consider a workaround. Autocheck only the drives that contain the OS,
> programs and active data. Then, if needed, you can run chkdsk manually
> for the other drives after the boot completes.
>
> Since crashes that require a chkdsk are rare around here, I tend to bypass
> the config.sys autocheck. Instead, I boot to a small maintenance
> partition that's organized so only the boot partition needs a chkdsk.
> Once booted I run the other chkdsks from the command line. These run much
> faster than boot time chkdsks.
>
> >The first two, above, are for my Adaptec SCSI adapter, to which my 2 HD's
> >are attached. The second 2 I retained from when I had EIDE HD's. Since I
> >still have EIDE units (the 2 CD's), I retained them. I have no idea
> >whether or not they should still be in the CONFIG.SYS
>
> These make sense given your hardware.
>
> >Anyhow, bottom line: Daniela's drivers should not be involved with the
> >initialization, timing, etc. of my HPFS HD's.
>
> I wasn't sure. Most folks do it the other way around. IDE drives and
> SCSI burners and scanners.
>
> >It's the maximum allowable partition size for booting to OS/2. It's a
> >matter of taste. For example, I believe Steven has a smaller boot
> >partition and he then places his various OS/2 apps on another partition.
>
> This is a preference thing. There's really nothing wrong with the large
> partition size other than the long chkdsk time, but with the amount of
> disk space you have, there's no way around this other than avoiding hard
> crashes.
>
> >partitions except C: (that gets me a 3 minute boot up). If I were to get
> >JFS and apply that to all partitions except C:, would that do the trick.
> >If I have JFS, does that eliminate the need for the system to autocheck
> >those paritions?
>
> I believe JFS will initialize faster. It will chkdsk orders of magnitude
> faster. This is one of the major improvements over HPFS along with larger
> cache sizes. The downside is that JFS is young compared to HPFS so
> there's a higher probability of catastropic filesystem failure. That said
> the latest drivers are stable and many folks are using them without
> problems.
>
> Steven
>
> --
> ---------------------------------------------------------------------
> "Steven Levine" MR2/ICE 2.35 #10183 Warp4/FP15/14.085_W4
> www.scoug.com irc.webbnet.org #scoug (Wed 7pm PST)
> ---------------------------------------------------------------------
>
> =====================================================
>
> To unsubscribe from this list, send an email message
> to "steward@scoug.com". In the body of the message,
> put the command "unsubscribe scoug-help".
>
> For problems, contact the list owner at
> "rollin@scoug.com".
>
> =====================================================

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================

Return to [ 19 | January | 2003 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.