calvinc@sandstorm.Berkeley.EDU (Calvin Cheng) (04/01/91)
I have been encountering 2 big problems with A/Ux which I haven't been able to solve. Firstly, I can only logged on under the Mac-24/32 environments from the root and not from any other account. When I attempt to do that, the Finder complains about the volume "/" requiring minor repairs. I have clicked on both Ok and Cancel buttons but I am still forced to log out or restart. The strange thing is that I am using the same System Folder from these accounts as the root. Why does it work with the root and not the other accounts? I have been messing around a little with the "/" volume but if it works for root, it should work for the rest. Next, I have A/Ux installed on the 105MB Quantum using partitions created by Silverlining 5.27. My other hard disk is a 40MB Sony which I have installed with the TPI Manager program from Total Peripherals with only MacOS files. A/Ux refuses to recognize the volume (doesn't show up under the Finder) whereas the 5MB partition on the 105MB Quantum shows up as do floppy disks inserted into the FDHD. The guys at Total Peripherals dont seem to be too helpful. I have very sketchy information about how the TPI driver works. It could be that the partitioning table was not set up correctly to indicate all the info that A/Ux needs or that the driver software is not compatible with A/Ux. The best answer I get is to reformat the hard disk using Silverlining. Is there a better way that doesn't require backing up my hard disk (almost full) and then restoring it again especially in the absence of software that lets me fiddle with the partitioning table etc. Thanx Calvin Cheng << The Best is Yet to Be! >>
tony@kahu.marcam.dsir.govt.nz (Tony Cooper) (04/02/91)
This is my first posting from a new news program. It is a UNIX system so it should be a good deal more reliable than the Vax/VMS system I was using. I posted some other articles last week from a Vax and they never made it. The way to mount an HFS volume is to mount it under MacOS first. Then, and only then, boot A/UX. A/UX will only mount the first HFS partition on a disk. And then ONLY when it was mounted under MacOS first. When you have problems mounting HFS volumes here is how you can diagnose what is wrong. If your SCSI id is x then do (as root) dp /dev/rdsk/cxd0s31 This will either work or it won't. If it works then you will end up with a prompt and you type in P. It will list all your partitions. Have a look for the HFS partition(s) which are indicated by Type: "Apple_HFS". The first such partition listed is the one that A/UX will try to mount. Study it's parameters to see if they are reasonable and to see if the partition is the right one. You will have to figure that out for yourself. Read dp(1m) to see what the fields mean. If dp does not work then you have no chance of mounting the HFS volume. What you do depends on the error message dp gives (maybe the drive is not switched on, maybe the partition table is wrong). If the partition table is wrong then your drive formatting software is out of date. If the drive is not switched on then switch it on. If dp works then the next step is to do as root dd in=/dev/rdsk/cxd0s30 count=1 | od -c You should get LK as the first two bytes. Then the MacOS boot block info some of which is words like Finder and Macsbug and dissasembler. If you don't get this then there is not a valid HFS filesystem in the first HFS partition. Something is wrong somewhere - maybe with your disk partitioning software. If this works then I have no idea what to do next. It should work. You can try force mounting the partition with HFSmount. Type HFSmount /dev/dsk/cxd0s30 and see what happens. You have to get a copy of HFSmount first. It hasn't been released yet. Just wait till I have tested it thoroughly under A/UX 2.0.1. Something else you can try is HFSmount With no arguments it mounts every HFS partition it can find on your SCSI bus. If your HFS partition is lurking there somewhere HFSmount will find it. But don't wait for HFSmount. Your single HFS partition should mount by itself. I just included this last bit on HFSmount to let people know it status. Tony Cooper sramtrc@albert.dsir.govt.nz
urlichs@smurf.sub.org (Matthias Urlichs) (04/03/91)
First, if you get a stupid error message saying "More data than device
expected" when you try to dp the drive, then you need to run Tony's "Fix
Error Page" program under MacOS before doing anything else.
This applies mostly to Syquest cartridges (you'll have to modify all of
them as the parameters are stored on the cartridge), but some hard disks are
also affected.
In comp.unix.aux, article <1991Apr1.231933.14564@am.dsir.govt.nz>,
Tony Cooper writes:
<
< The way to mount an HFS volume is to mount it under MacOS first. Then, and
< only then, boot A/UX. A/UX will only mount the first HFS partition on a
< disk. And then ONLY when it was mounted under MacOS first.
<
Actually, only if the appropriate MacOS driver was installed and operational.
That's important when using Syquests and your MacOS driver doesn't
understand the partition map. Unfortunately, some of these older Syquest
drivers will also fail to look whether the bus is busy when they check for a
cartridge, the effect of which is that A/UX Startup hangs while displaying
the "Checking" or "Loading" status messages.
They will also lock the drive's eject mechanism. Time to get a driver update.
< [ using dp ]
The most common problem seems to be that the physical size is correct but the
logical size is zero. The fix is obvious:
[ dp hard disk, print map, find HFS partition(s) ]
c N (with N the first HFS partition map entry's number)
) XXX (with XXX the partition's physical size)
p (check that you did everything correctly)
qwq (end editing, write map, end dP)
<
< If the partition table
< is wrong then your drive formatting software is out of date.
<
Be aware that it'll probably become bad again the next time you use your
regular partitioning software.
< dd in=/dev/rdsk/cxd0s30 count=1 | od -c
Better (with x your SCSI ID):
% dd in=/dev/dsk/cxd0s30 bs=512 skip=2 count=1 | od -c | more
The first two letters are BD (for "Big Disk", or HFS).
This will look OK even if you never installed a System on that partition.
< [ HFSMount ]
Will that beast work with multiple HFS partitions per drive?
--
Matthias Urlichs -- urlichs@smurf.sub.org -- urlichs@smurf.ira.uka.de /(o\
Humboldtstrasse 7 - 7500 Karlsruhe 1 - FRG -- +49-721-621127(0700-2330) \o)/