Arch won't boot after trying ususepnd

I wanted to try suspension to disk so I installed uswsusp and hibernate-script, added the ususpend hook in mkinitcpio.conf just before filesystems, mkinitcpio -p kernel26 and after some configuration issued the command "hibernate" as root.
Thigs seemed to work, but after the screen turned off, it instantly turned on again and I was back in my desktop (I suppose the modules were loading again because my wifi card was reconnecting).
I rebooted, and then the mkinitcpio hook seemed to start working and restored my desktop, just where I was when I tried the "hibernate" command. Tried to reboot again, but the KDE reboot buttons didn't did anything. Seconds later, all the desktop hanged, and I had to force a cold reboot.
After that, every time I try to boot, both with the "Archlinux" and the "Archlinux Fallback" entries in Grub, I get a really nasty kernel panic.
I tried to load a LiveCD, delete ususpend from the hooks array and rebuild the initcpio image, but nothing seems to hange.
My system is updated to the present day, including stable kernel26.
I think I really fucked it up this time. Any idea?

Heh, posting from Archlinux LiveCD.
I was trying to check what happened in a chroot, and I realized that every now and then I couldn't access directories I normally can access even from chroot, like some subdirectories of /var. When I tried to read some files the console threw "Permission denied" and "IO Error" errors. However, the majority of the filesystem seems to be accesible.
I'm performing a reiserfsck on my root partition, and the things seems to be quite screwd up. I'm getting "block ******: The level of the node (******) is not correct, (1) expected the problem in the internal node occurred (******), whole subtree skipped". Does this have fix :\?
What do you think could have caused theese issues? Failed hibernation? Just the cold reboots?

Similar Messages

[SOLVED] Arch won't boot after I created a separate /var parition

Arch won't boot after I created a separate /var parition on an existing installation.And let me confess: it was maybe stupid trying to do it on an existing install.
I edited the fstab correctly, copied the files using rsync preserving permissions. Then I kept a backup of /var using tar. Then went on to delete everything under /var, ie /var/*, the /var folder is still there. All this I did from a live CD. After that I booted into my arch linux. Here I get messages about systemd successfully finishing fsck on each of my partitions, then the screen starts blinking. And there is no more output. Pressing Ctrl+Alt+Delete causes systemd to stop its services and reboot.
Having realized I had borked my system, I removed the /var line from fstab and restored /var from the tar file I made earlier. Again I did this from a live cd. Rebooted into my arch system, and again similar issues, namely that after fsck and messages informing a few services had started, the screen keeps blinking.
The live cd I used for reorganizing my partitions was elementary OS freya. They have GParted in there. I also have an arch install iso lying aroung from May 2013. If necessary, I can download the latest version. I am currently typing from a Windows installation I dual boot from.
I don't know how to extract any boot logs as I am locked out of the system. Here is my fstab in any case:
# Filesystem information
# /dev/sda5 LABEL=fs_root
UUID=b9d739cf-fd8c-46dd-a919-bd827dc47c66 / ext4 rw,noatime,data=ordered 0 1
# /dev/sda9 LABEL=fs_var
UUID=ec0f7a49-dccd-43ab-8651-9aa3fdb41cc7 /var ext4 rw,noatime,data=ordered 0 2
# /dev/sda2 LABEL=fs_boot
UUID=0e8ab31a-3bda-4b85-a901-a36f21b1583d /boot ext2 rw,noatime 0 2
# /dev/sda6 LABEL=fs_home
UUID=d9e63c47-274e-447f-ad01-0d97afe0fd34 /home ext4 rw,noatime,data=ordered 0 2
# /dev/sda7 LABEL=fs_swap
UUID=7301227c-e9f3-41b8-9d0f-4cf3c159491c none swap defaults 0 0
# /dev/sda3 LABEL=fs_win
UUID=12B639D1B639B5D7 /fs_win ntfs uid=1000,gid=1000,dmask=027,fmask=137,showexec,nofail,noauto,x-systemd.automount 0 0
# /dev/sda3 LABEL=fs_share
UUID=D272269772268079 /fs_share ntfs uid=1000,gid=1000,dmask=027,fmask=137,showexec,noauto,nofail,x-systemd.automount 0 0
I would greatly appreciate any help.
Last edited by richcocoa (2015-05-03 18:04:44)

Have you moved everything from /var to /new_var (i named it for learning purpose)? You shoud copy content from /var but not on the fly but booting from arch iso cd, and than you shoud mount your / into arch-chroot environement, mount all of your mount points and than copy content from default /var to new /var. The copying should be done with this
cp -rax
and you can add -v switch to verbose output. I have my own /var moved the same way.
The simples way is:
-boot the arch iso cd
-mount all of your mount point (i created here in this step /new_var to move /var to a new place, and this /new_var i put in /etc/fstab as /var later)
-copy /var to /new_var with -rax or -vrax (recursive, archive, this filesystem or verbose, recursive, archive, this filesystem switches)
-umount all of it
-reboot.
Last edited by firekage (2015-05-02 07:49:20)

MacBook Pro won't boot after trying to install 10.7.3 update. Start up stalls at Apple logo and spinning gear.

MacBook Pro won't boot after trying to install 10.7.3 update. Start up stalls at Apple logo and spinning gear. Computer won't even start in safe mode.

My daughter's MacBook Pro was doing exactly the same thing. I don't know if it had anything to do with the latest update. She called me about a week ago saying that her MacBook began running slower by the day . She then called me Friday and told me that it wouldn't get past the gray screen and the gear just kept on spinning. I did everything I could over the phone including Safe mode which it wouldn't go into and thought maybe it was the hard drive. She took it to the Apple store. Originally, they also thought it was the hard drive. It ended up being a corrupted operating system (Lion). Apple genius simply re-installed Lion and she's back up and running. Good thing she backed up right before it crapped out. She'll be restoring everything tonight. Don't know if re-installing Lion will help your situation, but it did the trick for my daughter.

Arch won't boot after rEFInd update

I've followed https://wiki.archlinux.org/index.php/UEFI_Bootloaders as closely as I can, but still can't get Arch to boot. It doesn't even get to the boot loader.
uname -m
x86_64
Partitions:
Device Type Name
/dev/sda1 Linux filesystem root
/dev/sda2 Linux filesystem boot
/dev/sda3 EFI System efi
/dev/sda4 Linux filesystem var
/dev/sda5 Linux filesystem home
lsblk
Name Type Mountpoint
sda disk
sda1 part /
sda2 part /boot
sda3 part /boot/efi
sda4 part /var
sda5 part /home
Directory tree:
/boot/
efi/
EFI/
arch/
initramfs-arch-fallback.img
initramfs-arch.img
refind_linux.conf
vmlinux-arch.efi
refind/
icons/
refind.conf
refind_x64.efi
initramfs-linux-fallback.img
initramfs-linux.img
vmlinuz-linux
/boot/efi/EFI/arch/refind_linux.conf:
"Default boot" "root=PARTUUID=d368616d-a423-4511-88df-f2f645079bab ro rootfstype=ext4 add_efi_memmap system.unit=graphical.target"
"Boot to terminal" "root=PARTUUID=d368616d-a423-4511-88df-f2f645079bab ro rootfstype=ext4 add_efi_memmap system.unit=multi-user.target"
ls -l /dev/disk/by-partuuid/
lrwxrwx 1 root root Jan 30 1:08 d368616d-a423-4511-88df-f2f645079bab -> ../../sda1
efibootmgr -v
BootOrder: 0018, ...
Boot0018* Arch Linux (rEFInd) HD(3,0,0,74930800)File(EFI\refind\refind_x64.efi)
Anything else I'm missing? By the way, I think this is related to the Jan 27. update to refind. Today was the first time I've rebooted my computer since then.
Also - I tried both commenting and uncommenting scan_all_linux_kernels in refind.conf. No dice.
Thank you very much!
EDIT: Some updates...
I was poking around the UEFI shell. The following commands caused my computer to hang (I had to hard-restart):
Shell> fs0:
FS0> ls
I could ls just fine using shell 1.0, but shell 2.0 caused a hang. Then, after the hard restart, more strange behavior:
Shell> bcfg boot add 0 fs0:\EFI\refind\refind_x64.efi "Test"
Error. The file 'fs0:\EFI\refind\refind_x64.efi' did not open.
Also, I can "bcfg boot dump" just fine, but if I want to scroll through the output, I get an error, and it hangs, so I have to hard restart again.
Shell> bcfg boot dump
// bunch of output
Shell> bcfg boot dump -b
// after printing five boot entries...
Press ENTER to continue or 'Q' to break:
ASSERT_EFI_ERROR (Status = Not Ready)
ASSERT c:\dev\edk2top\ShellPkg\Library\UefiShellLib\UefiShellLib.c(3223) : !EFI_ERROR (Status)
Not sure if any of that last but is relevant. Thanks again.
Tried downgrading kernel to 3.6, still won't boot.
Last edited by MitchellSalad (2013-01-30 20:05:10)

MitchellSalad wrote:
Partitions:
Device Type Name
/dev/sda1 Linux filesystem root
/dev/sda2 Linux filesystem boot
/dev/sda3 EFI System efi
/dev/sda4 Linux filesystem var
/dev/sda5 Linux filesystem home
/boot/efi/EFI/arch/refind_linux.conf:
"Default boot" "root=PARTUUID=d368616d-a423-4511-88df-f2f645079bab ro rootfstype=ext4 add_efi_memmap system.unit=graphical.target"
"Boot to terminal" "root=PARTUUID=d368616d-a423-4511-88df-f2f645079bab ro rootfstype=ext4 add_efi_memmap system.unit=multi-user.target"
ls -l /dev/disk/by-partuuid/
lrwxrwx 1 root root Jan 30 1:08 d368616d-a423-4511-88df-f2f645079bab -> ../../sda3
Shouldn't that be sda1? Your root-partition is /dev/sda1.

IMac won't boot after trying to migrate files to macbook?

While trying to migrate info from my IMAC to my Macbookpro all work froze on both puters. Macbook starts and runs alright. But my IMAC won't boot at all. Tried startup disc and it won't get past picking a destination because it doesn't list one. I made a boo boo hear and need help fixing this.

Drive Preparation
1. Boot from your OS X Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the process has completed.
4. Quit DU and return to the installer. Install OS X.

Arch Won't Boot After Kernel Upgrade

I installed Arch on VirtualBox, but after upgrading the Kernel to 2.6.30 it wouldn't boot. It gets to "Loading udev...." and then VirtualBox crashes.

Hello, I'm having this same problem, except I'm not using VirtualBox or VMWare, I have Arch installed to the hard drive. It worked fine after upgrading to 2.6.30, but after upgrading kernel-headers to 2.6.30.1-1, neither Arch NOR Arch-Fallback will boot! I don't even get to Udev or the part where the two arch logos are on top. It just starts up a little bit, then restarts my computer.
I don't even know if my system has been wiped or something, but I doubt that; I think it's just the booting process. I do have a 2009.2 Live CD, but it's an FTP installation. Is there any way to start up my live CD and do a pacman -U for the old kernel version with the cache on my hard drive? How would I do this?
Last edited by Allamgir (2009-07-07 00:32:12)

[SOLVED] Arch won't boot after install - "GRUB" on black screen

I've installed arch on my 1000H from usb stick using zeneee kernel as described in wiki. Right after install everything was fine - wireless and ethernet were working normally, so i've done reboot.
Now it shows me black screen with "GRUB" text (sic! not "grub>", no error messages) on it. keyboard is not working.
I've tried reinstalling completely again - with full repartitioning of HDD and this time without installing eee kernel - just stock kernel26. Everithing went ok, i've checked grub settings and partitions - ok, but after reboot - again "GRUB" and non-working keyboard.
I'm completely out of ideas.
EDIT: turns out i misplaced GRUB or something. reinstalled placing GRUB on /dev/sda. works fine now.
Last edited by glas01 (2008-11-29 12:46:15)

Have you moved everything from /var to /new_var (i named it for learning purpose)? You shoud copy content from /var but not on the fly but booting from arch iso cd, and than you shoud mount your / into arch-chroot environement, mount all of your mount points and than copy content from default /var to new /var. The copying should be done with this
cp -rax
and you can add -v switch to verbose output. I have my own /var moved the same way.
The simples way is:
-boot the arch iso cd
-mount all of your mount point (i created here in this step /new_var to move /var to a new place, and this /new_var i put in /etc/fstab as /var later)
-copy /var to /new_var with -rax or -vrax (recursive, archive, this filesystem or verbose, recursive, archive, this filesystem switches)
-umount all of it
-reboot.
Last edited by firekage (2015-05-02 07:49:20)

Arch won't boot after -Syu: /etc/rc.sysinit can't execute things

Hello,
I was not getting any updates for about a week or two so I checked my mirrors and added a few more. I ran yaourt -Syu, there were 30 updates.
I shutdown my computer and when booting I got several messages saying "cannot execute binary file" from /etc/rc.sysinit.
Here is the first of such messages:
/etc/rc.sysinit: line 45: /bin/dmesg: cannot execute binary file
rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one month, y3k, 114 bytes nvram
/etc/rc.sysinit: line 84: /sbin/hwclock: cannot execute binary file
Arch Linux Fallback has the same problems. I also tried to get to my files with the Arch livecd but I could not mount them:
mount: can't find /dev/sda3 in /etc/fstab or /etc/mtab
Any help on this would be greatly appreciated. I have some things on there that I don't want to lose.
Thanks,
Andreas

From a knoppix disk I mounted sda3 and other partitions to their respective mount points and used chroot.
I ran pacman -S base but many of packages did not install correctly according to the messages.
The reboot with the hard drive fails and I am dropped to a recovery shell.
I can't chroot in again after this because of "Exec format error" however both the Knoppix disk and the Arch install are both i686. Maybe x86_64 base was being installed by pacman.

Arch won't boot after switching to ext4

Hi,
Yesteday I converted my partition to ext4 sucesfully, and I managed to boot once after that, but when I tried to reboot, GRUB2 would say:
error: invalid magic number
while trying to load the kernel. I already chrooted from my Ubuntu partition and tried to fix by reinstalling kernel and fsck'ing, but no luck. ideas? I can't even boot from fallback :S

Ok, here's my grub.cfg
# Config file for GRUB2 - The GNU GRand Unified Bootloader
# /boot/grub/grub.cfg
# DEVICE NAME CONVERSIONS
# Linux Grub
# /dev/fd0 (fd0)
# /dev/sda (hd0)
# /dev/sdb2 (hd1,2)
# /dev/sda3 (hd0,3)
# Timeout for menu
set timeout=5
# Set default boot entry as Entry 0
set default=0
#Colors
set menu_color_normal=light-blue/black
set menu_color_highlight=light-cyan/blue
#modules insert
insmod linux
# (0) Arch Linux
menuentry "Arch Linux" {
set root=(hd0,5)
linux /boot/vmlinuz26 root=/dev/sda5 rootfstype=ext4 ro quiet
initrd /boot/kernel26.img
# (1) Arch Linux recovery
menuentry "Arch Linux Fallback" {
set root=(hd0,5)
linux /boot/vmlinuz26 root=/dev/sda5 ro quiet
initrd /boot/kernel26-fallback.img
menuentry "Kubuntu 8.10, kernel 2.6.27-7-generic" {
set root=(hd1,5)
linux /boot/vmlinuz-2.6.28-4-generic root=/dev/sdb5 ro quiet splash
initrd /boot/initrd.img-2.6.28-4-generic
menuentry "Kubuntu 8.10, kernel 2.6.27-7-generic (recovery)" {
set root=(hd1,5)
linux /boot/vmlinuz-2.6.28-4-generic root=/dev/hda1 ro single
initrd /boot/initrd.img-2.6.28-4-generic
## (1) Windows
#menuentry "Windows" {
#set root=(hd0,3)
#chainloader +1
BTW, if I change "linux" command for "multiboot", I get this:
alloc magic is broken at 0x19710
Any ideas on what may be causing this? Perhaps changing to GRUB-legacy would help?

Arch Won't boot after lockup: "Failed to read file" [SOLVED]

So like many stories, this one begins with a "Sudo pacman -Syu".
Everything was updating fine, but then my system locked up. I let it set for awhile, but when I couldn't even get a console, I finally rebooted (yes, bad, I know).
I was about half-way through the upgrading process.
Now my system will not boot, and I only get a "Failed to read file" error.
I chrooted into my system through the live disk, and managed to finish the upgrade (I had to fix a few files, and reinstall some manually). I tried a "mkinitcpio -p linux," but no luck.
Is there anything else I could post that might be helpful? This error does not tell me a whole lot.
Thanks!
Last edited by thewooster (2014-06-18 16:11:51)

I did a little more looking around, and found a few more problems.
When I run a "mkinitcpio -p linux" now, I get:
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
It also appears I have a number of "empty" directories "pacman -S linux"
resolving dependencies...
looking for inter-conflicts...
Packages (1): linux-3.14.6-1
Total Installed Size: 70.27 MiB
Net Upgrade Size: 0.00 MiB
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
reinstalling linux...
>>> Updating module dependencies. Please wait ...
depmod: ERROR: failed to load symbols from /lib/modules/3.14.6-1-ARCH/extramodules/fglrx.ko.gz: Invalid argument
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> ERROR: Unable to write to /boot/initramfs-linux.img
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> ERROR: Unable to write to /boot/initramfs-linux-fallback.img
ldconfig: File /usr/lib/libclamunrar_iface.so is empty, not checked.
ldconfig: File /usr/lib/libfontforgeexe.so.2.0.0 is empty, not checked.
ldconfig: File /usr/lib/libfontforgeexe.so.2 is empty, not checked.
ldconfig: File /usr/lib/libgunicode.so.4 is empty, not checked.
ldconfig: File /usr/lib/libfontforgeexe.so is empty, not checked.
ldconfig: File /usr/lib/libcord.so is empty, not checked.
ldconfig: File /usr/lib/libgdraw.so.5 is empty, not checked.
ldconfig: File /usr/lib/libgdk_pixbuf_xlib-2.0.so is empty, not checked.
ldconfig: File /usr/lib/libgnome-menu-3.so is empty, not checked.
ldconfig: File /usr/lib/libgdk_pixbuf-2.0.so is empty, not checked.
ldconfig: File /usr/lib/libgccpp.so is empty, not checked.
ldconfig: File /usr/lib/libhunspell.so is empty, not checked.
ldconfig: File /usr/lib/libgdk_pixbuf-2.0.so.0.3000.8 is empty, not checked.
ldconfig: File /usr/lib/libgccpp.so.1 is empty, not checked.
ldconfig: File /usr/lib/libwbclient.so.0 is empty, not checked.
ldconfig: File /usr/lib/libhunspell-1.3.so is empty, not checked.
ldconfig: File /usr/lib/libgioftp.so is empty, not checked.
ldconfig: File /usr/lib/libgdk_pixbuf-2.0.so.0 is empty, not checked.
ldconfig: File /usr/lib/libgdraw.so is empty, not checked.
ldconfig: File /usr/lib/libX11-xcb.so.1 is empty, not checked.
ldconfig: File /usr/lib/libgioftp.so.2 is empty, not checked.
ldconfig: File /usr/lib/libclamunrar.so.6 is empty, not checked.
ldconfig: File /usr/lib/libfontforge.so is empty, not checked.
ldconfig: File /usr/lib/libX11.so.6 is empty, not checked.
ldconfig: File /usr/lib/libgdk_pixbuf_xlib-2.0.so.0 is empty, not checked.
ldconfig: File /usr/lib/libclamav.so.6 is empty, not checked.
ldconfig: File /usr/lib/libgutils.so.2.0.0 is empty, not checked.
ldconfig: File /usr/lib/libgnome-menu-3.so.0.0.1 is empty, not checked.
ldconfig: File /usr/lib/libgunicode.so is empty, not checked.
ldconfig: File /usr/lib/libtalloc.so.1 is empty, not checked.
ldconfig: File /usr/lib/libclamunrar.so is empty, not checked.
ldconfig: File /usr/lib/libclamunrar_iface.so.6.1.23 is empty, not checked.
ldconfig: File /usr/lib/libpytalloc-util.so.2 is empty, not checked.
ldconfig: File /usr/lib/libcord.so.1 is empty, not checked.
ldconfig: File /usr/lib/libX11-xcb.so is empty, not checked.
ldconfig: File /usr/lib/libgccpp.so.1.0.3 is empty, not checked.
ldconfig: File /usr/lib/libtalloc.so.2 is empty, not checked.
ldconfig: File /usr/lib/libtalloc.so is empty, not checked.
ldconfig: File /usr/lib/libwbclient.so is empty, not checked.
ldconfig: File /usr/lib/libX11.so.6.3.0 is empty, not checked.
ldconfig: File /usr/lib/libfontforge.so.2 is empty, not checked.
ldconfig: File /usr/lib/libgutils.so is empty, not checked.
ldconfig: File /usr/lib/libclamunrar.so.6.1.23 is empty, not checked.
ldconfig: File /usr/lib/libclamunrar_iface.so.6 is empty, not checked.
ldconfig: File /usr/lib/libhunspell-1.3.so.0.0.0 is empty, not checked.
ldconfig: File /usr/lib/libtalloc.so.2.1.1 is empty, not checked.
ldconfig: File /usr/lib/libgutils.so.2 is empty, not checked.
ldconfig: File /usr/lib/libfontforge.so.2.0.0 is empty, not checked.
ldconfig: File /usr/lib/libtalloc-compat1-2.1.1.so is empty, not checked.
ldconfig: File /usr/lib/libgc.so.1 is empty, not checked.
ldconfig: File /usr/lib/libpytalloc-util.so is empty, not checked.
ldconfig: File /usr/lib/libcord.so.1.0.3 is empty, not checked.
ldconfig: File /usr/lib/libgunicode.so.4.0.0 is empty, not checked.
ldconfig: File /usr/lib/libX11.so is empty, not checked.
ldconfig: File /usr/lib/libpytalloc-util.so.2.1.1 is empty, not checked.
ldconfig: File /usr/lib/libgc.so is empty, not checked.
ldconfig: File /usr/lib/libhunspell-1.3.so.0 is empty, not checked.
ldconfig: File /usr/lib/libgdk_pixbuf_xlib-2.0.so.0.3000.8 is empty, not checked.
ldconfig: File /usr/lib/libgdraw.so.5.0.0 is empty, not checked.
ldconfig: File /usr/lib/libX11-xcb.so.1.0.0 is empty, not checked.
ldconfig: File /usr/lib/libwbclient.so.0.11 is empty, not checked.
ldconfig: File /usr/lib/libgioftp.so.2.0.0 is empty, not checked.
ldconfig: File /usr/lib/libgc.so.1.0.3 is empty, not checked.
ldconfig: File /usr/lib/libclamav.so is empty, not checked.
ldconfig: File /usr/lib/libgnome-menu-3.so.0 is empty, not checked.
ldconfig: File /usr/lib/libclamav.so.6.1.23 is empty, not checked.
Gummiboot will not reinstall "gummiboot -path=$esp install":
Failed to check file system type of : no such file or directory
I have considered doing a reinstall, but I have so many customizations that I would prefer not to lose them. I do have an rsync backup, but it is a little old, and do have separate home/root partitions, but wouldn't I still lose a fair amount of customizations?

MacBook won't boot after trying to repair with Disk Utility. Cannot boot in Safe Mode. Just powers down after about 5 minutes. Apple Hardware Test says error 4SNS/1/40000001:IG0C-0.265 But I cannot find anything on the net about it. MacBook 4,1 Intel.

Hello Everyone,
I am in dire need of assistance I am hoping someone could provide. I have a MacBook 4,1 with Intel Core 2 Duo processor 4GB Ram. It is taking over 10 minutes to boot up past the gray apple screen when I turn it on. First I cleared the PRam (?) then I checked the disk using Disk Utility Verify, and it said the disk needed repairs. So I ran the disk repair and it said it was unable to fix the errors on the HD.
I did a little research and tried booting into the Single User mode, then running /sbin/fsck -fy. It said that it found errors but could not fix them. I ran it two more times as suggested and got the same result each time. I then tried rebooting and now instead of taking 10 minutes to boot up, it takes about 5 minutes on the gray apple screen and then just turns off. I started in Verbose mode to try to troubleshoot the error and it appears the last thing to come across the screen before power down is a message "Apple Yukon 2: RxRingSize <= 1024....etc".
I decided next I would run the Apple Hardware Tester. The test came back with an error code "4SNS/1/40000001:IG0C-0.265". I am very good at searching the web but I could not find any errors that had the IG0C or IGOC or any combination at the end, but plenty of 4SNS/1/40000000(1) errors with different endings. From what I can tell people are saying anything with 4SNS/1/4000000 is a logic board failure, but this computer was literally just booting this morning until I did the /sbin/fsck -fy.
Any suggestions are welcome and appreciated.
Thank you for your time.

You've a couple of issues .... when Disk Utility tells you it can't repair a drive, if the error is a soft error, like an invalid tree or node, Disk Warrior (or TechTool Pro) can handle it. However, if Disk Warrior (or TechTool Pro) can't handle it, you can erase and write zero's to the hard drive and restore to it, or you can buy a new hard drive. Sometimes running SMART Utility can provide additional insight into the health of the hard drive.
THe 4SNS error is a sensor error. You could install iStat Pro to see if something is indeed getting too hot or remaining room temp or less. You may need to take it into an Apple shop so they can use their thermal diagnostics to test and isolate it further.

Arch won't boot after update and force shutdown because of freeze

OK, I am typing this message on my tablet because the arch system isn't working. It freezes on systemd-fsck dev/sda3 clean a bunch ofmfile and blocks.

Okay guys so I have done some research and what I think I need to do is get into chroot and from what I have gathered chroot (correct me if i'm wrong) simulates the real computers terminal from a live Arch or other distro's cd with chroot installed on it? So I would do mount /dev/sda3 /mnt, as sda3 is my home folder, wait nope some more research says I need to do mount /dev/sda1 /mnt then /dev/sda3 /mnt/home then do arch-chroot /mnt. Now it shows sh-4.3 and a command blinker thing. I am stuck on what to do now

Mac won't boot after updating to OSX 10.6.4

I am on my 3rd Mac that won't boot after updating to OSX 10.6.4. One MacBook Pro and two iMacs. I fixed one but the last two are getting the better of me. HD is not fried. Have tried every keyboard shortcut on startup, Disk Warrior via. Target Disk, repairing permissions in single user mode. The machines will not boot off of a CD or DVD and it will not boot up in safe mode. Something in the startup files is preventing startup. I am suspecting Sophos antivirus. I tried to uninstall it and trash it but I think it's still blocking something. Any help would be appreciated.

Got it! Not sure if removing Sophos had anything to do with it but here's what I did.
1) boot dead machine in Target Disk Mode (iMac)
2) boot good machine off Snow Leopard disk (MacBook)
3) install OS to dead machine- I found this next part very curious. When the install was complete the MacBook restarted as the iMac.
4) ran software updates
5) shut down MacBook then shut down iMac
6) rebooted iMac- all was good
I actually did this twice because a co-worker had the exact same problem on her MacBook Pro. Got both fixed today.
Thanks everyone for your help!

My MacAir 1st gen. won't boot after latest OS X Lion update.

My MacAir 1st gen. won't boot after latest OS X Lion update. tried safe boot(didn't work) tried disk repair, said it was successful, but my mac won't start up. Just get white screen. Also been having trouble with it overheating. Fan seems to work. But when it get too hot whole interface slows down.

Yikes, I hope you have AppleCare on it still, I think it needs to be taken in, but as a last ditch effort...
Have you done a PRAM reset, CMD+Option+p+r...
http://support.apple.com/kb/HT1379
In fact, do 3 in a row, takes a bit of time.

Mac mini won't boot after RAM upgrade.

Tried installing new RAM in my Mac Mini, 512MB stock to 2GB of Crucial. Followed the directions to a T, grounded myself the whole time.
Things I've tried so far:
1. Resetting the PRAM, no luck.
2. Holding option at start-up, shows no icon.
3. Holding shift, no luck.
4. Holding X, nothing.
How do I get it to accept a CD if it won't boot?

Welcome to Apple Discussions!
You clearly have a problem, but you don't describe exactly what that is other than that your mini won't boot after the upgrade. What happens when it starts up? Does it attempt to start and hang up on the grey or blue screens, or does it start beeping at you almost immediately after you try and start it up, and also flash the power light?
If the former, then you may have dislodged a connector while working inside the system, in which case opening it up and checking that everything is firmly connected would be the first thing to do. If the latter, then the beeping/light flashing is the system telling you it has failed the power-on self test and the pattern of beeps/lights indicates why. In your case likely the system can't find workable memory. In that instance, opening the system and ensuring that the RAM is firmly and fully seated would be a good step, and if the mini continues to fail, then replacing the new RAM with the original to test that the system will then start.
It is not likely that anything had damaged your MacOS install in the process of upgrading, thus normally no reason to need to boot to CD as a result of a RAM issue.

Arch won't boot after trying ususepnd

Similar Messages

Maybe you are looking for