Cannot boot arch

Hey folks.
Got a brand new HP dv6 laptop with an AMD Phenom quad core processor that's refusing to boot. I got through the install ok, and the reboot after the install. I was installing the gnome desktop environment and took the dog out while waiting on the huge download/install. When I came back, my laptop screen was blacked out, and didn't respond to any keyboard/mouse stimuli.
I did a hard power off, and started it back up, and tried to boot arch. Among the startup fly-by info, I saw:
CPU 1: Not responding
CPU 2: Not responding
CPU 3: OK
After this, a few more lines go by, and then the system locks up with a blacked out screen and a flashing caps lock light. Same happens when I try and boot into Arch recovery. Windows still boots just fine.
It's a 64 bit install.

To respond to ewaller's suggestions:
Neither Ctrl + Alt + F12 elicits a response, nor Ctrl + Alt + F1-F6.
In my best attempt at trying to provide more information, I've used my android to take a video of the laptop starting up, up to the blank black screen, hopefully it can be of use. On a mildly related note, I think it's weird that I can see myself in the reflection of the screen once it goes black, but I'm trying to fix my laptop here, so bear with me
Video is .3gp format, usual mobile video format, VLC can play it.
http://goose.honk-honk.org/files/2011-0 … 15_708.3gp
If I can get away without having to do a reinstall, then I'd prefer not to, as the installation seemed to go off without a hitch. But if it appears that's what the actual issue is, I can certainly reinstall.
Thanks.

Similar Messages

[SOLVED]Gummiboot cannot boot arch

Hello. I've been reading the wiki guide until the end when i got stuck. I have windows 8 installed with a UEFI mobo so i just used the same ESP for arch. Now i try to boot arch but get a "vmlinuz not found" message. What did i do wrong?
while still on live cd i mounted the EFI partition (/dev/sda2) to /boot (same root and home partition) and then installed and configured gummiboot as described.
Do i have to add that ESP to the fstab file? Or how to fix it?
Last edited by Juszr (2015-03-31 17:10:49)

Load up the Arch live ISO, mount your partitions and use `arch-chroot` then post the output of:
ls /boot
# efibootmgr -v
lsblk -f
# parted -l
You can use `sprunge` to post the output of the commands.
<command> | curl -F 'sprunge=<-' http://sprunge.us
https://wiki.archlinux.org/index.php/Li … in_clients

Cannot boot Arch (USB or HDD) in UEFI Mode

I have a new MSi GT70-0ND, 1x 128GB SSD (no RAID) and 1x 750GB HDD. The SSD was preloaded with an MSi OEM copy of Windows 8. I did not receive an OEM disc, so I've tried to avoid touching the SSD and the hidden recovery partition on the HDD.
Using Universal USB Installer, installed archiso onto USB flashdrive.
Windows boot device selection menu did not detect the flashdrive.
Checked UEFI BIOS settings - USB set to "Full Initial".
Moved flashdrive from port to port, eventually was detected.
Reboot, received an error relating to bootloader signing.
Rebooted again into UEFI BIOS settings, disabled secure boot.
Rebooted, received infamous "No loader found. Configuration files in \loader\entries\*.conf are needed."
Googled, checked forums, saw gummiboot issues, recommendations to use rEFInd, and dd/UEFI issue.
Transferred archiso to working Arch machine, followed instructions here https://wiki.archlinux.org/index.php/UE … B_from_ISO.
Installed rEFInd using instructions here https://bugs.archlinux.org/task/31894#comment102233. I have since tried various changes to refind.conf and can not discern any difference.
Attempted to boot laptop from flashdrive in UEFI mode after Windows' boot device menu again failed to detect flashdrive multiple times.
Got rEFInd menu, found nothing functional (except Windows bootloader, of course): Arch entry froze the system requiring hard reboot, UEFI Shell v2 gave an assertion error (from memory, it was "String.c(166) String != ((void *)0)"); Googled, seeing some related but no identical errors, UEFI Shell v1 failed to start reporting something like "using load options '<null string>'".
Rebooted in BIOS/Legacy mode, but flashdrive was unbootable (duh)
Again using Universal USB Installer, installed archiso onto flashdrive.
Rebooted in BIOS/Legacy mode, archiso menu appeared, but during udev events, received a drm/nouveau init table error; Hard reboot. Appended
nouveau.modeset=0
to kernel line, everything worked
Installed vanilla Arch system to the HDD including UEFISYS partition.
When it came time to set up and install rEFInd/efibootmgr, of course
modprobe efivars
failed.
Redid flashdrive the UEFI-safe way on Arch machine, attempted to boot in UEFI mode, it appears that menu entries from my /boot/efi (UEFISYS) partition are present, but this is irrelevant as only the Windows bootloader and \refindx64.efi work (loads rEFInd graphical mode, in which nothing works except BOOTX64.efi which quickly flashes a message with a file path (too quickly to read) then loads Windows. UEFI Shell v2 now has same error as v1:
Using load options '<null string'> Error: Not Found while loading shellx64_v2.efi
rEFInd (version 0.5.0) "About" dialog reports EFI Revision 2.31, Firmware: American Megatrends 4.653, Screen Output: Graphics Output (UEFI)
I have tried adding various things to the refind.conf "options" directive, e.g. gpt, loglevel=7, pci=nocrs, add_efi_memmap, archisobasedir=arch, archisolabel=ARCH_201212, acpi=off, etc. in different combinations.
I am at wits' end. Bottom line: nothing but rEFInd (via flashdrive) and Windows works in UEFI boot mode - nothing. Any help will be greatly appreciated. Thank you.

I doubt if this will help you with your main goal, but I've fixed a few memory bugs in rEFInd recently, so the "String.c(166) String != ((void *)0)" error you mentioned might go away if you upgraded to the latest version of rEFInd (0.6.0).
Beyond that, here's a suggestion:
Prepare a USB flash drive or CD-R with rEFInd 0.6.0. Be sure to include an EFI driver for whatever filesystem you used in Arch's /boot (or root, if there's no separate /boot partition) in the flash drive's or CD's EFI/BOOT/drivers_x64 directory. (Note that rEFInd 0.6.0 includes an ext4fs driver.)
Using an emergency disc, create a refind_linux.conf file in Arch's /boot directory. Include, at a minimum, two lines, each of which should include the options "ro root=/dev/{whatever} initrd={\path\to\initrd}", changing the device filename to point to your root and the initrd= specification to point to your two Arch initrd files (one for each line). The path should be relative to the root of whatever filesystem holds those files, so if you've got a separate /boot partition, there would be no directories, just the filename preceded by a backslash; and if you have no separate /boot partition, you'd lead with "\boot\". Note the need for BACKslashes, not forward slashes, in the initrd= specification (but forward slashes in the root= specification).
Reboot using the rEFInd flash drive or CD-R you've prepared. With any luck, rEFInd should come up and show you an Arch option. Try using it. If it fails, try again, but hit Insert and select the second option from the list.
With any luck this will get your system booted in EFI mode, but I can't make any promises about that.

Can't boot Arch for installation. USB stick issue.

I got stuck. I tried to install arch on my dekstop, but booting Arch from USB stick freezes in same point, after running hooks. I tried with two usb sticks, new iso etc. Ubuntu was installed before without any problem from the same stick.
It freezes after showing:
Waiting 30 seconds for device /dev/disk/by-label/ARCH_201108 ...
[4.053579] sd 12:0:0:0: [sdb] No Caching mode page present
[4.053634] sd 12:0:0:0: [sdb] Assuming drive cache: write through
[4.056259] sd 12:0:0:0: [sdb] No Caching mode page present
[4.059035] sd 12:0:0:0: [sdb] Assuming drive cache: write through
In some attempts I also got this:
ata_id[12376]: HDIO_GET_IDENTITY failed for '/dev/sdb': Invalid argument

Problem is sovled, but the solution is really courious.
In fact, there was no issue with usb stick. Display freezes on first showed lines and does not follow the rest. Arch booted successfully but I cannot notice that, because I still see first lines (messages from first post were just warnings). Switching FullHD, 16:9 monitor to old 3:4 display solved the problem.
It's really strange. Should I report it somewhere?
Last edited by 0xddr (2012-05-12 23:30:53)

[SOLVED] Is Refit required for single-boot Arch on Macbook Pro?

I have a Macbook Pro 7.1, and now that the issue with a non-supported chipset has a workaround I am planning to create a single boot Arch system using the latest Archboot that comes with the 2.6.35 kernel.
If I understand well I need the non-efi grub combined with the firmware's bios compatibility mode if I want 2d/3d accelerated gfx, since that does not work currently with grub2-efi. One question I cannot find an answer to though is whether or not I need Refit and an EFI partition for this. The Arch wiki (nor the Debian/Gentoo/Refit docs) is not very clear about this. Is it only needed for multi-boot setups or for all setups that use bios compatibility?
Last edited by rwd (2010-09-06 15:44:00)

Veovis Muad'dib wrote:You need to bless the Arch partition from OS X, probably running from USB or something like that
Do you mean that I need to install Arch besides the existing OSX and 'bless' that arch partition from OSX in order to be able to remove all non-Arch partitions?
Veovis Muad'dib wrote:, and then make sure to never zap the PRAM..
Not that I was planning to do this, but does this remove the possibility to boot Arch?
Veovis Muad'dib wrote:As for if you can change BIOS settings, no. You can change boot disk, but that's it. What would you need to do in the BIOS anyway?.
I just thought it might come in handy for tweaking powermanagement, wake-on-lan, bluetooth and stuff like that.
litemotiv wrote:Also be sure to set your boot partition active if you plan to fdisk, EFI won't be able to see it otherwise.
Thanks all for the info!
Last edited by rwd (2010-08-24 16:13:27)

Booting 'Arch Linux' Error 15: File not found

Booting 'Arch Linux'
root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
kernel /vmlinuz26 root=/dev/sda3 ro vga=792
Error 15: File not found
Press any key to continue...
It's the message that Grub send me choose any option.
Can I solve or I need to format and reinstall?

donniezazen,
Note that you responded to a three year old thread. I cannot tell if you are having a problem, but I doubt this thread has any bearing on it.
Closing. If you are having an issue, please open a new thread. Our policy
Thanks

Booting Arch from SD

Hi, I have made a manual Arch install on a 2GB SD card, and I haven't succeeded in booting it.
Basically I formatted it as ext2, mounted it under some directory, installed the pkgs, starting with filesystem, the base utilities (with pacman -r). Then I installed xorg + kde, so far everything's ok.
My hardware is a laptop with the TI 7xx1 card reader, that isn't mass storage (the driver is tifm_sd), so I cannot boot it from BIOS, and grub can't use it either. So I'm using the grub from my hdd, with kernel26 and a custom initcpio. I have put "MODULES="tifm_sd tifm_7xx1 mmc_block" in my ramdisk, my modules are loaded, and my mmcblk0p1 node gets created successfully at boot time.
I booted with "kernel /boot/vmlinuz26 root=/dev/mmcblk0p1 ro pci=routeirq"
And now I'm stuck with the following:
kinit: mounted root (ext2 filesystem) readonly.
sh: root=/dev/mmcblk0p1: No such file or directory
The error happens in some script apparently, but I can't find which.
Can somebody experimented with the boot system help ? At the moment I am not interested in a fully-functional system, it's just for a performance test, and I'd just like to get past the init stuff.
Thanks!

deuns wrote:
I booted with "kernel /boot/vmlinuz26 root=/dev/mmcblk0p1 ro pci=routeirq"
And now I'm stuck with the following:
kinit: mounted root (ext2 filesystem) readonly.
sh: root=/dev/mmcblk0p1: No such file or directory
The error happens in some script apparently, but I can't find which.
The first line suggests that your root filesystem was mounted successfully. You didn't happen to add init=/bin/sh to the kernel commandline? That is somehow broken. Otherwise I cannot make sense of the second line, as no 'sh' process should be involved now, but control should be given to the init process.

[solved] cannot boot from dd usb and cannot install 64 with unetbootin

hi,
been trying to install arch for almost 24 hours now. i just cannot manage to setup USBs to boot from.
first i was using unetbootin, but when the device not found error came up i tried using the methods recommended in the wiki. however, my hp elitebook 2540p cannot boot from the usb created using dd or imagewriter. so i went back to unetbootin and figured out the error was that the syslinux.cfg file needed to have ../../ replaced by archisobasedir=arch archisolabel=KINGSTON. now however, i cannot seem to figure out how to install a 64 bit system. when i run pacstrap all packages have i686 at the end, which i assume means its the 32 bit one.
help
EDIT: ok i have now used 3 different USB sticks and run
sudo dd if=~/Downloads/archlinux-2012.07.15-netinstall-dual.iso of=/dev/sdd
on them. plugging them into the 2540p the laptop just wont boot. it wont get past the first hp screen, where i normally press esc to enter the menu so i can choose boot options. the usb just blinks and nothing happens. this same problem happens with imagewriter in windows.
Last edited by iOfWhy (2012-07-29 13:01:10)

McDoenerKing wrote:Was the usb stick mounted, when issueing the dd command?
Did you use "of=/dev/sdx1" instead of "of=/dev/sdx" for the dd command?
Which image did you use?
i wrote exactly
sudo dd if=~/Downloads/archlinux-2012.07.15-netinstall-dual.iso of=/dev/sdd
as mentioned in the edit above, the computer wont get past the hp screen where one gets the option to press the esc key... the usb just blinks and nothing happens...
EDIT:
no the usb was not mounted...
the image was checked with both sha1sum and md5sum...
EDIT2:
ok so i think i am in... i reformatted the usb with fat filesystem, and then went through the second instructions from the wiki, ie installing "Without overwriting the USB stick"... But i am still wondering why i couldnt just do the normal dd method. Is it that the hp bios cannot read certain filesystems?
Last edited by iOfWhy (2012-07-28 13:39:40)

Macbook Pro4.1 Cannot Boot Up After Battery Allowed to Drain.

I’m hoping someone can help me troubleshoot some strange behaviour of my Macbook Pro4.1. It’s an early 2008 2.4Ghz Core 2 Duo. I’ve had this running perfectly for the past 2 months with an Apple 65W Magsafe Adaptor, although I recently got an 85w version so I’ve started using that for a bit. I recently read somewhere that it’s good to allow the battery run completely flat once a month or so, so I unplugged the adaptor last week and ran it off the battery for the afternoon. When it was almost done (10% charge left) I went for a shower and came back to find the Macbook powered down. I plugged in the Adaptor back in but I couldn’t get it to start.
I have to say at this point, that my 85w adaptor sometimes needs a wiggle at the magsafe end to get it to work. Despite this though I couldn’t get the green power LED to light or the Macbook to boot up. I then tried my 65W adaptor, which is perfect, and although the LED lights up (first green and then amber) the macbook just doesn’t power up with it. I tried the 85w one again the following day after leaving the macbook disconnected and battery removed overnight, and was pleased to find that it finally booted. Amazingly, despite having no power at all for the whole night it came back with all my applications running, safari tabs and the documents open! Anyway, I noticed from the menu bar that the battery was not charging and I couldn’t seem to get it to charge. I ran it all day and the system profile showed that the Battery was about half full and had a ‘normal’ condition with about 187 charge cycles. However I can’t run the Macbook off the battery. When the power cuts out from the 85w adaptor the whole macbook shuts down. The battery isn’t doing anything, even after charging all day and being half charged. What’s more neither of my 65w adaptors can start the macbook no matter how many times I try them. Only my 85w one can boot it, but it’s defective so very rarely seems to work. The 65W ones worked perfectly before,so I don’t know what’s changed.
I read the Apple guide to resetting the SMC and have now followed the procedure several times, but it hasn’t helped. I cannot boot the Mac any more. Does this Macbook come with an 85w adaptor or 65w? I’m confused because the 65w ones always worked until now. Also, the battery itself is only 60w.
I’m going to purchase another 85w Adaptor, in the meantime any advice would be very welcome. Thanks for reading!

Thanks again for all the input, very much appreciated.
So, in case of any misunderstanding, both my 60w Magsafe Chargers are perfect. I use them with other MacBooks. No problem. I also used them with this MacBook, prior to the battery going flat. Again, no issues. Despite that, even when I've completely removed this battery and tried to boot the Macbook up from just the chargers, nothing happens at all. There is no power. I've reset the SMC which is the obvious culprit. Still nothing.
The only charger I have which can start it is an 85w one. However that's defective, so I don't get a connection long enough to complete a bootup. The question is, is this normal? Should this MBP only work with an 85w and not a 60w?? And if that's the case, how come it worked on a 60w charger for so long? And why is the battery 60w and not 85w?
thanks again

Cannot boot itunes after 10.1.2 upgrade.

Hello there..I had itunes 10.1.1 running fine on my XP - apple updater told me there was a new version (10.1.2) so I upgraded...did the install and now I cannot boot itunes from desktop or anywhere else...tried uninstalling and reinstalling but no luck...no messages, no errors just...no itunes.
Do you think you can help or anyone else who reads this?

I Finally got mine working correctly. I have windows 7 64 bit. I uninstalled everything and reinstalled using the 64 bit. It works now. I don't know if the automatic update selected the 32 bit to update. I rechecked the system requirements, it looks like itunes no longer supports the 64 bit xp system--if that's what your is. I would look into that, and maybe downgrade to the olde itunes.

Mac pro cannot boot after upgrade to 10.8.3

My Mac Pro cannot boot after upgrade to 10.8.3. Anything firmware I can reset or how should I do.
I am using a early 2008 Mac Pro

Can you boot into safe mode? http://support.apple.com/kb/ht1455
If not, how about Recovery? http://support.apple.com/kb/ht4718
If you can, run Disk Utlity and repair the disk. You can try rebooting normally, but I would just reinstall after quitting Disk Utility.

Cannot boot after recovering a FileVault 2 protected disk

I used Lion's new recovery HD partition to restore a four day old Time Machine backup. However, two days ago I enabled FileVault 2, which is probably the cause of the fact that I cannot boot my mac anymore. As the whole disk is locked, I cannot access the recovery partition either. Disk Utility of Snow Leopard install DVD doesn't support unlocking the partition, it is grayed out and therefore I'm not able to mount it. I honestly don't know yet how I can fix this problem. Can you help me?

Unlocking worked using the DVD, but I could never really make it bootable anymore. Reinstallation of Lion on the existing partition didn't work either. Just FYI, when trying to make the disk the startup disk it give me the following error: 'Building boot caches on boot helper partition failed'. The only solution that worked and was good enough for me was to delete the partition, reinstall lion and restoring time machine data on the new installation afterwards.

Curve 8320 corrupts OS periodically and then cannot boot (blinking LED only)

I have a T-Mobile BB Curve 8320 that I've had for about 9 months, and I have what appears to be a recurring problem.
Three times now, the phone has corrupted its OS, and it will not boot. Each time it does it, the symptoms are first the phone is non responsive, and just shows the spinning hourglass cursor. The last time it did it while in the Mail app, which is the one I use almost exclusively. The phone appears to lock up, showing the wait cursor indefinitely. This time I waited a half hour, and it was clear that it wasn't coming back. So I pushed the power button, and it shut down the phone. But then when I tried to turn it back on, the screen never came up, and it just blinked the red LED "forever." (It was about 18-20 hours before I got around to trying to reload it.) The first time this happened was when the phone was running the OS version it shipped with, which I think was 4.3, but I don't recall. But now it has done it twice while running 4.5.0.81, which is the OS distribution T-Mobile makes available for the Curve.
The first two times it did it, I used the application loader to wipe the device and reload the OS. When in this state, BB desktop manager doesn't see the device since it can't boot. But if you click through to the application loader, you can get it to load. (Or you can run the application loader outside of BB desktop manager)
This time, the application loader started up, offered the choice of what to load, and then proceeded into the next phases. Erasing the device succeeds, as does the next phase where it loads the OS. But then it gets to where it is loading application modules, with a progress bar for each module and one for the overall progress. It got halfway through the overall progress, and failed with an "unspecified error", suggesting to try again. I tried it three times, and it failed the same way each time.
After calling T-Mobile, they bounced me over to RIM, and the first guy had me go through the app loader again with the same result. When he started pursuing USB connectivity issues, I asked to speak to someone else. (There are other devices on this system, both mass storage and input, and none of them ever show connectivity issues. )
The second tech had me rerun the application loader, but this time only select the core OS, leaving out all the apps. This succeeded, and then he had me rerun it, loading the rest of the applications. This also succeeded.
But the problem I still have is this. There is no explanation why the phone corrupts itself every couple of months, or why loading the OS and the applications in one step failed to work _repeatedly_. I believe the device has a bad memory address, and the two step OS load simply danced around it. And it is that which is causing the phone to corrupt its own OS to the point that it cannot boot.
The tech tried to pass of the corruption due to loading third party applications, and while I can accept that a rogue application can corrupt memory locations that it has the ability to write to, I don't know if the BB OS/device uses any form of protected memory, or if apps are essentially unrestrained. The only third party applications I load on this are the Google app, with Gmail, and Opera Mini.
To be honest, if the BB OS is that fragile that I can't even load these two applications on it, I'll be trading it for a different email capable phone.
Anyway, I'm looking to find if anyone else has a phone that repeatedly gets corrupted so it can't boot, and requires a complete reload. Also, is there anyway to test the memory on the phone? I'm going to call T-Mobile back and try to get them to swap my phone, because I can't afford to spend three hours on the phone with tech support every couple of months when my phone dies.
thanks!

Thanks for the reply. Our cases sound a bit different. I seldom use Desktop Manager, as I sync through BES. I do use it for backup though.
But over the time my phone corrupting itself has happened, I've upgraded from BB OS 4.3 to 4.5, which required an update to Desktop Manager, and following that I upgraded to a new computer. So I've changed computers, BB Desktop software, and BB OS software, and the problem has happened across all of those changes.
You should have been able to restore the OS even if it was corrupt. Desktop Manager won't recognize the device if it won't boot, but application loader will still find it. The first two times I did it, I used instructions basically like this: http://crackberry.com/blackberry-101-lecture-12-how-reload-operating-system-nuked-blackberry?page=4
But since then I've found I can just access application loader via BB Desktop Manager and do the same thing. I did notice when my OS reload kept failing this last time, that using application loader directly showed more of the failure message. It still wasn't anything useful, but when I reran the reload via Desktop Manager, I recognized the error was the same, but noted that I didn't see all of the output of the standalone application loader.

[SOLVED] nouveau error while booting arch

Hi!!! I'm newbie to arch, here is an error I can't solve myself. I search in google for solutions but they didn't solved. Please help me to solve this. I dual booted arch linux with window 8.1. After installation, while booting for the first time, this error occurred.
Here is the error I found.
[0.063411] Ignoring BGRT: Invalid status 0 (expected 1)
starting version 218
Arch_Linux: clean, 70622/18677760 files, 1643393/74703025 blocks
[ 15.759913] nouveau E[ PIBUST][0000:01:00.0] HUBO: 0xffffffff (0x1a
[ 15.759952] nouveau E[ PIBUST][0000:01:00.0] GPCO: 0x00000001 (0x1a
[ 15.823494] nouveau E[ PBUS][0000:01:00.0] MMIO: 0x00000000 FAULT a
[ 15.824050] nouveau E[ DRM]Pointer to TMDS table invalid
[ 15.824072] nouveau E[ DRM]Pointer to flat panel table invalid}
Last edited by aaa234 (2015-02-04 04:18:42)

aaa234 wrote:
runical wrote:
That is a different problem to be honest. I assume that you can login using your normal user? If you set up sudo you might be able to get into root by using
sudo su
and change the password like that.
I'm sorry if this is a noob question. Where do I type sudo su because as soon as the OS is booted, the system asks localhost login and password. I haven't installed any desktop environment yet. I only set up a password under arch-chroot but I can't login with and without that password.
I was assuming a normal installed environment with a normal user. Using "sudo su", you can abuse privileges granted by sudo to circumvent the password required by su. A well configured sudo should not allow this, but in this case it seemed likely that the system was not completely set up yet.
problem has been solved with this https://bbs.archlinux.org/viewtopic.php?id=168879
Then, if there are no more problems, please mark the thread as solved.

Kernel Panic / G4 dp500 / Cannot boot currently

Machine Config:
10.4.8
G4 DP500
1.5 gigs ram.
Internal ATA133 PCI controller card (Sonnet)
Four internal hard drives. My current 4-drive configuration:
Three 200 gig drives are connected to the internal ATA133 sonnet card, and out of those three, just one was made to be bootable with 10.4.8.
The fourth drive (160gig) is connected to the on-board ata33 connector, and is bootable with 10.3.9 on it. Presently I cannot boot from either drive
I installed the Sonnet ata133 card three months ago to expand the drive capacity. I wanted to "see" hard drives larger than 127 gigs, which is the limit if using the onboard ata33.
Everything has been working fine for 3 to 4 months after I installed the Sonnet card, and three internal drives. But about three days ago, my computer was hard-frozen when I went to use it. No mouse movement etc. When I rebooted, I received the Kernel panic black screen with its resulting verbosity.
I had a spare internal drive laying around that was preconfigured with an OS on it. So fearing the Kernel panic was from the Sonnet controller card, I installed my spare drive to connect from the mother board ata33 connector. I was then able to boot from my spare. after that I was able to repair my boot drive that was attached to my Sonnet card. The one that was initially corrupted by the Kernel panic.
After rebooting successfully to m, I decided to leave my spare boot drive attached the on-board ata33 connecter (just in case the kernel panic happened again)
Well, it did happen again. And now I can't even boot from my spare now. Its as if the kernel panic is destroying the directories of my boot drives!
Specifically the volume header wraps.
In addition, I can't even boot from Disk Warrior or my OSX install disk. The screen just hangs at grey. So, I have no more spare boot drives available, and I cannot boot from cd/dvd. The cd/dvd drive is attached to the internal on-board ata33 like my spare is.
I know that heat will often cause a hard freeze. But will it also cause kernel panics upon reboot?
As it stands now:
When ever I try to reboot, a black screen will display unix command line text describing kernel panic and the last line is"
"Panic: we are hanging here."
This seems like a hardware issue. But why are my boot directories becoming corrupted? At this point, maybe its over heating. I have four drives now stuffed into the G4 with ribbon cables all over the place and a vent fan installed into one of the unused PCI slots.
I haven't installed any new hardware lately.
I upgraded to 10.4.8 and the panic still happens.
I have 30gigs of itunes, 20gigs of iphotos, 40gigs of imovies, 10 gigs of mail, etc. My back up system was using SuperDuper to copy my USER folder to another internal drive, so I know I have a backup, It's just that I cannot access it. If I can recover my data, I'm going to go out and buy a G5, transfer my data, and be done with it. If I can't recover my data, then I will be forced to live a life of quiet desperation. My wife will leave me if I've lost her itunes collection
BTW, what is a good program to back up to 8.5 gig DVD's? Can I make large 20gig .DMG files and segment then into 8.5 gig portions? I no longer want to rely on internal backup. I would feel better knowing that my back were on dvd's locked in my fire safe. When did I become so dependant on computers?!
Losing sleep.
Haifarmer

It may not help, but it's worth a try to reset the PMU. See Mac PRAM, NVRAM, CUDA/PMU & Battery Tutorial
When trying to troubleshoot problems, disconnect all external devices except your monitor, kbd & mouse. Do you experience the same problems?
May be a solution on one of these links.
Troubleshooting
The X Lab (Troubleshooting & Maintenance of OS X)
OS X Routine Maintenance & Generic Troubleshooting
Prevent Mac Disasters
Kernel Panic
Mac OS X Kernel Panic FAQ
Mac OS X Kernel Panic FAQ
Resolving Kernel Panics
12-Step Program to Isolate Freezes and/or Kernel Panics
 Cheers, Tom

Cannot boot arch

Similar Messages

Maybe you are looking for