On Feb 1, 2004, at 10:41 pm, Kris Tilford wrote:
I did an erase and re-install and again everything was going fine. I avoided the security update this time.
Yes, it's starting to appear that the Security Update isn't so hot, perhaps too secure.
Funny - I haven't installed it on my other two 10.3 machines yet - maybe I knew something they didn't??
You just found the infamous "SCSI bug" which is probably the second worst Panther bug (the Firewire bug being the worst). I've had some success by unplugging the ABD devices (assuming you're not using USB keyboard & mouse) right after the boot. On this boot, I've had all my SCSI devices mount. You'll have no keyboard & mouse; but if you plug them back in and hit "ctl-cmd-pwr" it will reboot. On this reboot it will use the 'journal' to mount all the SCSI most of the time. It's some sort of timing problem, and perhaps the journal replay, etc. just adds a delay that allows them to mount, I don't know this stuff. I just know it usually works for me.
I'm struggling with the Firewire bug, and it appears that Apple will have to issue an update to solve this horrible problem. I paved a Firewire drive, installed Panther clean and upgraded. On the first reboot after the Security Update it was slashed out. Utilities found lots of stuff, and didn't fix it so far. I suppose I can try again? I'm not convinced the Security Update is really the cause of either your SCSI slash or my Firewire slash since others had this problem before the Security Update. I think it's just coincidence. The Firewire bug produces disk corruption only if this Firewire drive is attached during a Startup, Restart, Shutdown or Sleep. All other times it's fine. This means Firewire booting isn't probably advisable with Panther. I have 5 or more FIrewire enclosures, and only the one with the Indigita chipset is immune (I'm booted from it now on a 7500). Oxford 911 was what just killed the clean installation of Panther. This was booting a "pristine" System on an iBook (no XPF), with the latest Oxford firmware. Total bummer since Oxford had been so rock solid in Jaguar.
I solved that (Throttled it to 24 so it had as much time as it wanted to boot) but now i have a different problem.
I have just installed an ACARD AEC-6712WM U2W SCSI card in my 9600. It works fine and boots 9.1 no problem. I setup XPF and rebooted to try and raise Panther but it won't boot. It's not a waiting for root problem this time, it appears to be a problem with the Journaling FS on the hard disk (which I moved off an a adapter on the internal bus).
I get the normal kernel boot up and the 'got boot device' message finds the card with the hard disk on and identifies it correctly. The BSD root reports OK. Then I get a message like:
jnl: journal start/end pointers rest! (jnl 0x1d17dc4; s 0x33e600 e 0x33e600)
Which looks like an FS problem with the journalling FS. Something significant is the hard disk's LED is locked on until i reboot.
Eventually, and this is after a LONG time (it happened while I was typing this and doing a few other things so i guess it was about 20 mins, maybe 30) I get this error:
MESH: 0 0 runDBDMA - Arbitrate/Reselect problem.
Which repeats at regular intervals of about 10 mins (I have 3 up currently).
Soooo.... any ideas?
-- Mark Benson
AIM - SilValleyPirate MSN - [EMAIL PROTECTED] Visit FlatPackMacs online: <http://fpm.68kmac.com> Visit my Homepage: <http://homepage.mac.com/markbenson>
"Never send a human to do a machine's job."
-The Matrix
-- Unsupported OS X is sponsored by <http://lowendmac.com/>
Support Low End Mac <http://lowendmac.com/lists/support.html>
Unsupported OS X list info <http://lowendmac.com/lists/unsupported.html> --> AOL users, remove "mailto:"; Send list messages to: <mailto:[EMAIL PROTECTED]> To unsubscribe, email: <mailto:[EMAIL PROTECTED]> For digest mode, email: <mailto:[EMAIL PROTECTED]> Subscription questions: <mailto:[EMAIL PROTECTED]> Archive <http://www.mail-archive.com/unsupportedosx%40mail.maclaunch.com/>
Using a Mac? Free email & more at Applelinks! http://www.applelinks.com
