Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!rpi!sci.ccny.cuny.edu!phri!cmcl2!panix!alexis
From: alexis@panix.uucp (Alexis Rosen)
Newsgroups: comp.unix.aux
Subject: Re: A/UX trouble
Message-ID: <1990Nov26.090219.16915@panix.uucp>
Date: 26 Nov 90 09:02:19 GMT
References: <90.319.16:21:00@ira.uka.de> <1990Nov18.101337.1947@panix.uucp> <2243@s6.Morgan.COM>
Organization: PANIX - Public Access Unix Systems of NY
Lines: 25

In article <2243@s6.Morgan.COM> jordan@Morgan.COM (Jordan Hayes) writes:
>Alexis Rosen <alexis@panix.uucp> writes:
>	> During the boot process when A/UX checks its file system and
>	> install the processes it gives us only the notice "panic:
>	> ialloc: dup alloc" after one-third of the progress bar.
>	It's telling you that it has discovered a single inode
>	allocated to two different files. Try running fsck on the
>	guilty party.
>
>Good advice.
>
>	I'd suggest reformatting and repartitioning the disk from
>	scratch, if nobody else has any better ideas.
>
>Bad advice, unless you like wasting time.  After you launch the boot
>process from MacOS, click the Cancel button ... this will bring you up
>single user.  Run fsck from there, and then reboot.

Huh? Is this not what I first said? "Try running fsck..."
The second paragraph was fallback- that is, if fsck didn't do the trick.

---
Alexis Rosen
Owner/Sysadmin, PANIX Public Access Unix, NY
{cmcl2,apple}!panix!alexis