bwild@foxi.uka.de (Bernd Wild) (11/16/90)
We purchased an MacIIfx with 16Mb some weeks ago to install A/UX on it, but... After exchange of all memory SIMMs and the complete mother/board we are still unable to get A/UX running with NFS and YP. 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. What's that???? It's impossible to restart the Mac even after pressing the reset button! Only switch-off/switch-on helps! Any ideas? Bernd. ============================================================================== Bernd Wild bwild@fzi.uka.de Forschungszentrum Informatik FZI Dept. Technical Expert Systems and Robotics Haid-und-Neu-Strasse 10-14 D - 7500 Karlsruhe GERMANY Tel.: (+49 | 0) 721 / 6906-310 ==============================================================================
alexis@panix.uucp (Alexis Rosen) (11/18/90)
In article <90.319.16:21:00@ira.uka.de> bwild@foxi.uka.de (Bernd Wild) writes: >We purchased an MacIIfx with 16Mb some weeks ago to install A/UX on it, but... >After exchange of all memory SIMMs and the complete mother/board >we are still unable to get A/UX running with NFS and YP. 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. What's that???? It's telling you that it has discovered a single inode allocated to two different files. Try running fsck on the guilty party. But that should be done automatically on boot when it discovers that the disk is "dirty" so there may be deeper problems. You didn't my any chance do something werid with dp, did you? (Though I'm not sure that even that could cause this message.) It could also mean just about _anything_ if your system is really messed up. I'd suggest reformatting and repartitioning the disk from scratch, if nobody else has any better ideas. --- Alexis Rosen Owner/Sysadmin, PANIX Public Access Unix, NY {cmcl2,apple}!panix!alexis
jordan@Morgan.COM (Jordan Hayes) (11/22/90)
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. /jordan
alexis@panix.uucp (Alexis Rosen) (11/26/90)
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