When booting up, I get a “panic ialloc, dup alloc” (or other) error message and A/UX won boot. What can I do?
This is due to the fact that some file system damage exists on the Root file system. By default, A/UX Startup will only run ‘fsck’ on the root file system if the system is marked as “dirty.” So even if damage exists, as long as the disk was cleanly ‘umount’ed, ‘fsck’ won’t check it out and fix it. Jim recommends always having A/UX Startup fully check out the disk before booting A/UX. It takes a while, but it’s worth it. To do this, choose Booting from the Preferences menu. Now change the command under “AutoRecovery” to “fsck /dev/default” (it was “fsck -y -p /dev/default”). When you do this, you’ll notice that the radio button changes from “Check root file system” to “Custom command”… that’s OK. After that, A/UX will always run ‘fsck’ on Root. If you are doing this, you might as well have A/UX run a full ‘fsck’ on all file-systems too. Check out fsck(1m) and fstab(4) for how to do this… one way is to just edit /etc/bcheckrc and remove the options to the “/etc/fsck” command. If you
Related Questions
- When booting up, I get a "panic ialloc, dup alloc" (or other) error message and A/UX won boot. What can I do?
- Why do I get an error message, archsw.readin.failed after compiling and booting a new kernel?
- I received a "Floppy disks fail (40)" error message while booting up the computer. What can be wrong?
