Samsung phones only from AT&T
Troubleshooting DiskWarrior 3.0: System cannot restart when booted from CD
From Wednesday, June 18th
Alsoft's technical support department has confirmed that DiskWarrior 3.0 has trouble restarting dual-processor Power Macintosh G4 MDD systems and possibly other 2003 (non Mac OS 9 booting) Macs when users start up and repair their system from the DiskWarrior CD.
After you have booted from the DiskWarrior CD, and completed repairs, attempting to restart your system results in an endless stall. This issue has been confirmed on Apple's Dual 1.42 GHz Power Mac G4.
The technical staff at Alsoft writes:
"This problem is not the result of DiskWarrior but rather an issue with some dual processor machines and the System folder on the CD. The System folder on the DiskWarrior CD is provided by Apple. We are not authorized by Apple to change the files in the System folder so there is not much that can be done to resolve this issue at this time.
"We have contacted Apple and they are aware of the situation. [...] For the time being if you restart the computer and it does not restart then you will need to manually restart it by pressing the power button on the front of the machine.
UPDATE: Some users experiencing this problem report that during the reboot after running DiskWarrior, you can hold down the mouse to eject the CD and startup will proceed as normal.
Feedback? Late-breakers@macfixit.com.
Resources
my dual processor system and then restarting and going through the
usual boot process, my display came up as a negative color image.
Trashing all obvious color related preferences and adjusting the Display
preferences did not fix the problem. However, first setting the Universal
Access screen preference to Black & White and then adjusting the Display
preferences restored the "positive" millions of colors. This, of course,
just might be coincidental with booting with DW3, but the color fix was
not obvious.
trouble. 10.2.6 here. Thanx for the heads up I'll use Drive 2 from now on
till its resolved.. As an added query:
I have been using the beta Norton 8 and it seems to find alot wrong with
the System name, wrapper, and other troubling info. I usually use it After
DW3. So I wonder is one right, and one wrong? I know they do different
things.
I use CarbonCopyCloner from Bombitch, seems to work great! I
wondered if because it cloans the drive, the Fix Utilities get confused
about what the wrapper, System Name and other changed perameters
should be.
Does DW3 notice its cloned and leave these items be & Norton see Max
(Drive2) and think, why does this drive think its 'Macintosh HD', the
'wrong' info? As once after repair both Dives came up as Macitosh HD in
the Startup DiskControl Panel? (my second drive is named Max (maxtor
120GB FDB). So does this factor into the issues? I think it must. Thebn
should I allow or not allow the changes( I always alow it to fix what it
thinks it should).
Does this make sense or have I confused you beyond repair? Thanx
Norton 8 is beta, and sadly, Norton has been unreliable in my experience
since OS X or slightly before. I have found its information quite, quite wrong
on several occasions. I'm steering clear of it until I hear people saying it's
safe again.
I DiskWarrior 3'd my system last week, and it resolved a problem I've had for
6 weeks, and it's been very fast since then. Norton hasn't helped in a while.
<br /><br />
Sounds like a cache cleanup is what you need.
AppleCare TechTool 303 CD I just received after asking for an OSX bootable
one DOES restart without a hitch...
Have fun, Hermie
happened to me on a Quicksilver 867, 896 Ram Superdrive model.
Check this forum thread:
http://www.macfixitforums.com/php/
showflat.php?Cat=&Board=xutilities&Number=501866&page=&view=&s
b=&o=&fpart=all&vc=1
So, this nonsense about Apple and system folders doesn't hold true.
Finger pointing is never a good way to duck out of problems.
Professionalism would have it that software companies would willingly
work together.
My Quicksilver 867 worked flawlessly after DiskWarrior.
I agree with you on pointing fingers. With OS X, there's a deeper problem: it
seems with each change of the OS, you may very well lose bootability.
There's got to be a way of making an emergency startup disk that you can
update. It would be good if Apple made that part of the system. Say Disk
Utility, when you make a disk image, asks you if you want it bootable or not?
If so, you get an OS with it, and you can add DiskWarrior, Norton, DriveTen
or whatever and then burn it.
The idea of having a bootable CD as part of the system utilities would be
welcomed for certain. In the meantime, you can make one yourself
using BootCD v0.5.3. However, I made one with OS 10.2.6 and
DiskWarrior3.0 but still suffered from the force restart after running the
software. I don't believe that was a BootCD problem though. It works
fine with other disk utility software.
I also made an emergency disk with Boot CD, adding DiskWarrior 3. And I
have the same restart problem with the BootCD CD as I do with the
DiskWarrior CD. This suggests to me an issue with OS X and bootable CDs.
As the BootCD version does not use the System file Apple supplied to Alsoft, I
don't see where this problem is Alsoft's fault. And it bodes ill for TechTool
and Norton as well as we wait for bootable OS X versions of these products.
Using another hard drive (or partition on another drive), as suggested above,
would have another advantage over using a CD in addition to stability: it
would boot faster and run faster. I have an OS 9 partition for this purpose; I
guess I'll have to make an OS X partition as well. [QuickSilver G4
dual 1 GHz with 1.5 GB of RAM, OS X 10.2.6]
---
Don't anthropomorphize computers.
They hate that.
Try removing all traces of DW from all your drives; master, spare clone
partition and external firewire or whatever. Then boot from the spare
clone and run DW off the factory CD from there on your master drive.
I had the problem described on my Quicksilver 867/Superdrive and on
my PB 12". I did not have the issue on my Dual 1.42.
On my machines with the problems, i had to do an archive and install
of the system files to get the ability to boot up at all. It was a real pain
and took hours. I have always had great results with DW--so this was
totally unexpected. Sorry others are having similar issues, but I am
glad I am not the only one.
---
zowner
500MHz 10.2.6 after having used the DW3 CD to boot
up. My workaround is to hold down the Option key on
the restart and choose my iMac HD icon from the Open
Firmware options. No problems after that.
freeware BootCD to burn an emergency boot CD with DW3 and/or
Drive 10 as well as any other repair goodies on it.
Since BootCD uses your existing system to build the boot disk, you
should have a bootable disk customized to the specific machine that
created the boot CD.
Install DW3 on your hard drive and then add it to the BootCD image at
the appropriate point prior to burning.
Creating a Boot Disk with BootCD and DW3 does not avert this problem,
at least not on my 12 inch PB. After using DW3, a restart results in an
endless boot stall requiring a forced restart.
my iMac after performing a DW3 routine and quitting it
results in a long wait before the iMac eventually reboots
off the DW3 CD again, but it doesn't go into an endless
stall as some people report. Once I reboot normally off
my iMac HD using the Option key then choose OS
method, if I run Disk Utility it does not find any privileges
that need fixing, or anything.
Seems to me that when DW3 is quit and goes to its
Restart dialog box, it is supposed to automatically point
back to the HD it has just fixed to reboot from, but that's
not happening, so eventually it falls back to the first
System Folder it can find, being its own boot CD.
my iMac, is that it booted to the OS X equivalent of the
question-mark. Pressing the Option key allowed me to
reselect my HD, and that was OK. When I went into
System Prefs -> StartUp Disk, my 10.2.6 System Folder
was NOT 'blessed'. I reselected it, it asked me to
confirm the change, and now it restarts as expected.
[1] I put in the TechTools CD that was sent to me by Apple Care and
restarted from that CD. (I do not have TT installed on my hard disk.)
[2] I ran all the TT tests, passed, and quitted the program.
[3] As soon as the computer restarted, I opened the CD drive, took out TT
and put in DiskWarrior 3 and restarted from the DW CD.
[4] I did rebuild directories and quitted the program.
[5] Voila: the computer restarted! (I have a dual 867 G4.)
- by RAngol July 9, 2003 2:12 PM PDT
- I have a multi drive setup with a variety of boot drives. My problem is
- Like this Reply to this comment
-
(19 Comments)that with DW3 installed on main OSX 10.2.6 boot disk I cannot "repair" a
vanilla OSX 10.2.6 install on a Master disk on second bus (Tempo 133
PCI ATA card) because it's "busy." It's always "busy." I don't have a clue
what's going on with this and taking a look at 'top' wasn't enlightening.
I can boot to that OSX drive, as suggested, and run DW3 with no
problem on the main drive (and the one that primarily concerns me.
Either of the two OSX boot drives can "repair" several external FW drives,
internal OS9 and/or Classic boot drives (ATA). I don't have a clue what's
"busy" on that second OSX boot drive.
(clarification: Let's assume I have four drives mounted, 2 masters and 2
slaves...the first two are on the main Apple bus of this DP Mac...the next
two are on a separate bus provided by the ATA PCI 133 card from
Sonnet)
I also cannot run Disk Utility on that other boot drive, but mention this
here because I rarely run that and always encounter the problem with
DW3. Sure would like to know what's "busy" (open app or process) on
that other drive.........
I experience no problems with 12 inch Alum Book including several
external FW drives which also boot OSX. Wonder if my problem is
related to DP in some way? Not certain. There's just some process
that's active on a boot drive which is only in use as non-boot at the
time.
Booting, restarting, et al with DW3 is a very annoying problem. Blame
rightly lies with Apple, not Alsoft, apparently. Someone at Apple
appears to have said "good enough" and shipped it to Alsoft..... :(