Subject: Re: 1.3_ALPHA fsck problems
To: Dave Huang <khym@bga.com>
From: T. Sean (Theo) Schulze <71410.25@compuserve.com>
List: port-mac68k
Date: 11/16/1997 09:28:20
>On Sat, 15 Nov 1997, T. Sean (Theo) Schulze wrote:
>> I first installed GENREICSBC#48 and confirmed that it would boot and run.
>> Then, I ftp'd the 1.3_ALPHA binaries from ftp.netbsd.org and used
>> Installer 1.11.0 to install them from the Mac OS side (sorry Mark). Now
>> when I try to boot, I get through the boot process until I reach:
>
>> Automatic boot in progress: starting file system checks.
>> Usage: fsck [-dfnpy] [-b block] [-c level] [-m mode] filesystem...
>> Unkonwn error; help1
>
>Hmm... this is getting to be a pretty common problem. (BTW, the installer
>is only up to version 1.1g or so... it's the booter that's up to 1.11).
>You have to do the install from within NetBSD, and make sure you use the
>"--unlink" option when extracting the tar files (see the UPDATE file for
>more information).
>
Well, I am doing it from within NetBSD now. I guess that is what I
should have done first anyway. Someone else mentioned how tar really
kicks butt speed-wise versus the Insatller. I am definately seeing that
now. base only took about the length of time it took me to shower. Last
night it took probably most of an hour.
>To the Installer maintainer (Steve Brown, right?): Would it be difficult
>to make the installer do the unlink? Although it's much better to do an
>upgrade from within NetBSD, it'd be nice if it'd work from MacOS as well
>(like if you don't have enough disk space to put the tarfiles on the
>NetBSD side or something).
Conserving disk space was the reason I was trying to do it from the MacOS
side, so I would second the motion for being able to do it with the
Installer. When I get this thing back on its feet again, I am really
going to have to go through the tar man pages. I want to fugure out what
the --unlink does.
>> fsck -f sd2c
>>
>> I get:
>>
>> sd2c (No such file or directory)Can't stat sd2c
>> Can't stat sd2c: No such file or directory
>
>For this one, fsck -f /dev/rsd2a
>
fsck -f /dev/rsd2a ran, but it didn't solve the overall problem. I am
hoping that the main problem will be solved as we've mentioned above.
Thanks,
Sean.
T. Sean (Theo) Schulze
TSSchulze@aol.com 71410.25 @compuserve.com
***************************************************
Always remember to pillage BEFORE you burn.