Nikos Mouat (nikm@conjungi.com)
Tue, 12 Jan 1999 08:46:32 -0800 (PST)
I have similiar problems on my machinie when I try and boot from a kernel
which was 'mv'-ed to the / directory. I think there is some kind of
problem with handling inodes over a certain # on ANS's.. I imaging that
you could work around this by booting off an external disk and mounting
your internal disk. Then mv your current quik.conf to quik.conf.old and
reboot.. if that doesn't work try doing a 'mv quik.conf quik.conf.old ; cp
quik.conf.old quik.conf' which will create a new inode for the file which
hopefully the booter will like.. if that doesn't work do:
cp /mnt/etc/quik.conf /mnt/quik.conf
cp /mnt/quik.conf /
quik -C /quik.conf
now the reason you put it on your internal disk root (/mnt) and your
exernal disk root (/) is that quik stores the full path name to the
quik.conf somehwere that is used by the boot loader so if you do 'quik -C
/mnt/quik.conf' it will try and look for /mnt/quik.conf on the internal
disk when you boot from it..
let me know if none of these thing work..
nm
On 11 Jan 1999, Larry Orchier wrote:
> Reply to: Re: trouble with quik
> I was trying to get the ANS 500 to boot automatically from the internal drive.
>
> I only had an internal drive in the machine, which would boot LINUX from OF
>
> I typed in the following from the terminal on linux
>
> /sbin/quik -v
>
>
> Ever since then, I seem to have lost Linux. My previous open firmware commands and setenv values don't get me past errors.
>
>
> scsi-int/> scsi-int/sd@2:0 Second state Quik loader
>
> Read error on block 573460
> Inode error # 2133571367 while loading file /etc/quik.conf
> Couldn't load /etc/quik.conf
>
>
> Is there a way of using the external drive to restore the internal?
>
> Do I have to start from the beginning? If so, how far back do I have to start?
>
This archive was generated by hypermail 2.0b3 on Tue Jan 12 1999 - 08:51:08 PST