Can't boot into installation

Tried to boot from USB with:
dd if=archlinux-2009.08-core-x86_64.img of=/dev/sdb
MD5 checksum checks out
USB formated FAT32, then I tried with an ext3 formated USB
I also tried unetbootin (http://unetbootin.sourceforge.net/)
Then I got an external USB cd reader/writer and burnt 2009.02 and 2009.08 (sould I try 2008.X builds?)
Tried to boot on this PC and get (on mine it works fine):
ERROR: boot device didn't show up after 30 seconds...
Falling back to interactive prompt
You can try to fix the problem manually, log out when you are finshed
ramfs$
Sometimes I got erros like:
sda1 (and all others) could not be mounted.
No boot device found.
I googled and I found this:
ramfs$ ln -sf /dev/sdb1 /dev/archiso
ramfs$ exit
Source: http://www.redbluemagenta.com/2009/10/0 … rch-linux/
Tried it, kernel panic after 'exit'...
I'm trying to install arch on an older machine, its not real that old tho.. It's specs (maybe it's relevant): AMD X2 4400+, 1GB DDR2, NVIDIA 7600GT, asus m3a78 motherboard, 450W PSU, HDDs (all SATA): 1=250GB (this is where I want to install arch), 3 and 4=2TB (x2 1TB on raid1, enabled in the BIOS).  It's a machine I aquired from a family member, I want to turn it into a personal webserver, file/media-server, access it via ssh, etc.
I already installed arch on my PC, could I just make an image of my HDD, copy it to the 250GB hdd in the new PC and install grub? (Im not sure how to do this...)
Any help will be appreciated, thank you!
Last edited by Ryuujin (2009-10-18 10:21:41)

I had a similar error message than your first one (... didn't show up after ...). I had to try a different USB slot in order to get it booting from the USB stick. I used the 2009.08 image, so in general, that image should be the right one. Do you have a cd/dvd driver in your machine or is there a chance to connect an external drive?

Similar Messages

  • Replaced dying hard drive, can't boot into installer

    Well, this is always fun.
    My hard drive was dieing in my 12-inch Powerbook (last-model, I believe), so I ordered a bigger one and just finished installing it.
    So, I try to boot to my 10.5 installer disk, and it gets to the Apple logo for about a minute, occasional DVD drive noise, and then freezes. Even the little spinny thing stops spinning. Sometimes there are vertical, dotted lines running through the darker areas, sometimes not.
    It was doing this when my previous hard drive was dieing, and that was on 10.4. I can now and could then log into single-user mode, but no GUI. I've tried everything I can think of, and nothing's worked thus far.
    Any help? My laptop is completely dead without an OS, and I've got school work and a programming internship that largely rely on my laptop.

    sheez
    I'm really ashamed of these forums. Doesn't anyone here even know how to ask intelligent questions?
    I managed to rip apart some of the info from the Single User mode, purchased a new set of OS disks, ran the hardware test, and discovered the video RAM had failed the test.
    ANY of those should have been suggested by someone with some repair knowledge. Non-booting? Did you ask about the hardware test built into the OS disks? Noooo, I had to find that out , and run it, myself. Problem not solved by replacing hard drive? Gee...
    Strange vertical lines on a boot screen where there shouldn't be any? Mayhaps it's video related? Hmmm? Even if you were wrong, it'd have been SOMETHING to try, instead of silence.
    Maybe I should just amble around here and show you people how to help people. I've had almost NO help (often no replies, either) for most of my questions on this forum, despite offering more information than most, and I ultimately have solved most of them myself, when they didn't resolve themselves.

  • Can't boot into Windows 8.1 partition after apple store repair

    Can't boot into Windows 8.1 partition after apple store repair
    I went to the apple store about a week ago to get my screen fixed, and when I get it back I don't have an option to boot into my windows partition. The bootcamp partition is still there, but I can't boot into it. I can still see all of the files on the drive. When I try to boot into windows from the startup disc setting I get "no bootable device — insert boot disk and press any key” on a black screen. I went in for a dead pixel, and the guy at the genius bar ran something on my computer and went into disk utility application. I’m not sure what he was doing, but obviously that’s what messed up my windows partition. How can I be able to boot back into windows? Here's what disk utility looks like on my computer.

    Here's the output
    00000000  eb 52 90 4e 54 46 53 20  20 20 20 00 02 08 00 00  |.R.NTFS    .....|
    00000010  00 00 00 00 00 f8 00 00  3f 00 ff 00 00 b0 0e 2b  |........?......+|
    00000020  00 00 00 00 80 00 80 00  ff bf 2e 0f 00 00 00 00  |................|
    00000030  00 00 0c 00 00 00 00 00  02 00 00 00 00 00 00 00  |................|
    00000040  f6 00 00 00 01 00 00 00  05 92 d3 74 c4 d3 74 aa  |...........t..t.|
    00000050  00 00 00 00 fa 33 c0 8e  d0 bc 00 7c fb 68 c0 07  |.....3.....|.h..|
    00000060  1f 1e 68 66 00 cb 88 16  0e 00 66 81 3e 03 00 4e  |..hf......f.>..N|
    00000070  54 46 53 75 15 b4 41 bb  aa 55 cd 13 72 0c 81 fb  |TFSu..A..U..r...|
    00000080  55 aa 75 06 f7 c1 01 00  75 03 e9 dd 00 1e 83 ec  |U.u.....u.......|
    00000090  18 68 1a 00 b4 48 8a 16  0e 00 8b f4 16 1f cd 13  |.h...H..........|
    000000a0  9f 83 c4 18 9e 58 1f 72  e1 3b 06 0b 00 75 db a3  |.....X.r.;...u..|
    000000b0  0f 00 c1 2e 0f 00 04 1e  5a 33 db b9 00 20 2b c8  |........Z3... +.|
    000000c0  66 ff 06 11 00 03 16 0f  00 8e c2 ff 06 16 00 e8  |f...............|
    000000d0  4b 00 2b c8 77 ef b8 00  bb cd 1a 66 23 c0 75 2d  |K.+.w......f#.u-|
    000000e0  66 81 fb 54 43 50 41 75  24 81 f9 02 01 72 1e 16  |f..TCPAu$....r..|
    000000f0  68 07 bb 16 68 52 11 16  68 09 00 66 53 66 53 66  |h...hR..h..fSfSf|
    00000100  55 16 16 16 68 b8 01 66  61 0e 07 cd 1a 33 c0 bf  |U...h..fa....3..|
    00000110  0a 13 b9 f6 0c fc f3 aa  e9 fe 01 90 90 66 60 1e  |.............f`.|
    00000120  06 66 a1 11 00 66 03 06  1c 00 1e 66 68 00 00 00  |.f...f.....fh...|
    00000130  00 66 50 06 53 68 01 00  68 10 00 b4 42 8a 16 0e  |.fP.Sh..h...B...|
    00000140  00 16 1f 8b f4 cd 13 66  59 5b 5a 66 59 66 59 1f  |.......fY[ZfYfY.|
    00000150  0f 82 16 00 66 ff 06 11  00 03 16 0f 00 8e c2 ff  |....f...........|
    00000160  0e 16 00 75 bc 07 1f 66  61 c3 a1 f6 01 e8 09 00  |...u...fa.......|
    00000170  a1 fa 01 e8 03 00 f4 eb  fd 8b f0 ac 3c 00 74 09  |............<.t.|
    00000180  b4 0e bb 07 00 cd 10 eb  f2 c3 0d 0a 41 20 64 69  |............A di|
    00000190  73 6b 20 72 65 61 64 20  65 72 72 6f 72 20 6f 63  |sk read error oc|
    000001a0  63 75 72 72 65 64 00 0d  0a 42 4f 4f 54 4d 47 52  |curred...BOOTMGR|
    000001b0  20 69 73 20 63 6f 6d 70  72 65 73 73 65 64 00 0d  | is compressed..|
    000001c0  0a 50 72 65 73 73 20 43  74 72 6c 2b 41 6c 74 2b  |.Press Ctrl+Alt+|
    000001d0  44 65 6c 20 74 6f 20 72  65 73 74 61 72 74 0d 0a  |Del to restart..|
    000001e0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
    000001f0  00 00 00 00 00 00 8a 01  a7 01 bf 01 00 00 55 aa  |..............U.|
    00000200
    Here's a better screenshot.

  • Can I boot into a PC laptop on an iMac using Bootcamp through a eSATA to Thunderbolt connection?

    Can I boot into a PC laptop on an iMac using Bootcamp through a eSATA to Thunderbolt connection?  Work forces you to use their computers, but it would be nice to use an iMac and extra displays while at home.

    Set up a VNC connection between the computers.
    (51819)

  • Hi, can anyone help with the problem I am having with pro book 4440s? I can't boot into windows 7.

    Hi, can anyone help with the problem I am having with pro book 4440s?  I can't boot into windows 7, nor can I enter the bios cause i fogot the password. the error I am getting says "windows failed to start. a recenr hardware or software change might be the cause.   it then gives me options to boot from a disc but I can't do that cause I am unable to get into the bios to change it to boot from a disc.
    The error message goes on :
    File: \Boot\BCD
    Status: oxcoooooof
    info: An error occurred while attempting to read the boot configuration.
    the only two options on the screen are enter=continue and ECS=exit
    I just can't get pass this screen.
    Please help.
    Thanks

    Hi,
    If you don't already have one, use another PC to create a Windows 7 Rescue CD.  Download the relevant ISO from the links below.
    Windows 7 32bit
    Windows 7 64bit
    You should use an application such as ImgBurn to burn the ISO to a CD - a guide on using ImgBurn to write an ISO to a disc is Here.  Once created, or if you already have this, tap away at the esc key as you start the notebook to enter the Start-up Menu.  Insert the Rescue CD.  Select Boot options ( usually f9 ), use the arrow keys to select the CD/DVD drive and hit enter.  You may also get a prompt to 'Press any key to continue' - do this if asked.
    When loaded, select Repair Your Computer and choose the Command Prompt.  When this loads, enter the following commands and hit enter after each one - include spaces as shown.
    Bootrec.exe
    bcdedit /export C:\BCD_Backup
    c:
    cd boot
    attrib bcd -s -h -r
    ren c:\boot\bcd bcd.old
    bootrec /RebuildBcd
    bootrec /fixmbr
    bootrec /fixboot
    Remove the Rescue CD and try rebooting the notebook.
    Regards,
    DP-K
    ****Click the White thumb to say thanks****
    ****Please mark Accept As Solution if it solves your problem****
    ****I don't work for HP****
    Microsoft MVP - Windows Experience

  • Can't boot into windows 7 anymore......

    Hi all, I have a Mac mini late 2012 with windows7 installed through bootcamp5. It has worked flawless until recently, now I can't boot into windows anymore. I've checked in finder and the bootcamp partition is present and also all the files. Before that, I did have some trouble with my LaCie 2big thunderbolt hdd, it kept on saying I had to reformat one of the discs in the drive, but only when used in windows, in OSX there was/are no problems reading the hdd .......
    Any idea of how I can make windows bootable again?, do I really have to make a fresh install of windows to make it work??
    Any help is very much appreciated
    Kindly
    Jan

    You might want to visit the Boot Camp forum where the Boot Camp gurus hang out. https://discussions.apple.com/community/windows_software/boot_camp

  • Can't boot into anything after EasyBCD's "Write MBR"

    After upgrading my windows 8.1 install to windows 10 about a week ago (week ago), I decided that I no longer wanted the Windows/Ubuntu dual boot I had setup. So, in an attempt to delete GRUB and set the bootloader back to the windows bootloader, I downloaded EasyBCD and fiddled with it a bit before finding the "Write MBR" option. I figured that would allow me to boot directly into windows, or at least delete Ubuntu's GRUB Bootloader, so I could use one of my many windows install DVD's to set the bootloader to a windows one. Unfortunately, I'm an idiot, and after doing that, I can't boot into anything. I've tried everything I could think of or find on Google to get it to boot into absolutely ANYTHING. I've tried boot into every one of the boot options, including the main boot menu, but none of them load. instead, it shows me a loading screen that displays some mobo info as if it were loading a boot option I selected, but it hangs there. Maybe it was just taking its sweet little time right? Wrong! I let it sit for hours, still nothin'. HP has a "solution" where you hold the windows key + B for one second as you start up the pc, and it should start a bios recovery. Feeling hopeless, I tried it, hoping that it would do SOMETHING. Of course, it didn't boot into that either. Just a black screen. Finally, I learned that sometimes problems like this could be cause by hardware issues, and a lot of the times its the hard drive. I highly doubted that it was a hardware issue seeing as I bought this PC late last year (around November or December of 2014) but I removed the hard drive just in case and started my computer. Same result. FML. Can someone, anyone, help this poor idiot get his baby up and running again? I don't have the money or the confidence in their abilities to give it to Geek Squad or anyone else for that matter and let them have a go at it, so i'm depending on the internet ((

    but if my PC's bootloader or something related is messed up, can the neosmart forums actually help?not trying to be rude or anything, i'm genuinely curious. you see, i cant really load anything, including any recovery disks or USB's, which is why i was hoping that there would be some sort of HP utility that could help me restore my PC back to its previous state. i'll still ask the neosmart forums though. i'm pretty desperate to fix my PC at this point!

  • Can I boot into Windows XP from a firewire enclosed Hard Drive? Boot Camp

    I understand you can install XP (as long as it has service pack 2 or 3) on an Intel Mac using Boot Camp, but I was wondering if it would be possible to take a HD from a PC computer which already has XP installed, and, using an firewire HD enclosure, boot the Mac into XP from that. Would this be feasible?

    Yes, but not exactly. The page says:
    "Can I install Windows on an external drive?
    No. Installing Boot Camp on an external hard drive is not supported."
    But I don't want to install Windows, I want to boot my computer into it.
    It also says:
    "External FireWire disks are not recognized by the Startup Disk control panel in Microsoft Windows. To start up from a bootable external drive, press and hold the Option (Alt) key while the computer starts up, then select the external disk."
    I don't mind if external disks won't appear under Windows, as long as I can still boot into it.
    I found another helpful post:bootcamp windows 7 Firewire external drive NTFS?
    Here someone writes:
    "I still use Windows XP with my Mac but still never had such a problem with my two Firewire external HDs (one FW400 and one FW800).
    And I did a lot of things with these
    Partioned one for use with OSX and Windows (one HFS+ partition; one NTFS partition); copied my complete MP3-collection (180GB) from one external HD to the other; etc.
    All without any kind of glitch or slowdown."
    So it seems this person was successful in booting XP from an external drive. Windows 7 or Vista on the other hand will encounter problems booting, which that tread explains.
    In another thread (Boot camp on an external hard drive) someone wrote:
    "I believe there might be a way, I just haven't gotten around to trying this out.
    1) use disk utility to partition the external drive to ntfs (i think)
    2) attach this disk to a pc and install the OS
    3) install refit onto your mac
    4) attach the drive via fw800, or even better yet esata, to you mac.
    5) Start up your mac
    6) choose the win xp option from the boot menu
    7) install bootcamp drivers
    this seems, in theory, that it should work."
    So from what I gather, I think this method would probably work, I just want to know if anyone had any specific knowledge regarding this subject.
    From here I only have two questions:
    Is it possible to take a working drive from a PC which already has XP installed, and change the format to ntfs under OSX without damaging the drive or OS?
    And, would I need a version of XP with service pack 2 or 3, or will anything do, since we are not installing it with Bootcamp, we are only running it under Bootcamp at this point.
    Thanks for any help!

  • [Solved] Can't boot into Arch after deleting some partitons

    About 6 months ago I installed Arch on a machine that used to run Ubuntu. Had some trouble at the time getting to boot into Arch but somehow managed. Now eventually decided to delete the old Ubuntu partitons to free up some space using gparted. Arch partition number changed from sda12 to sda6.
    On rebooting after deleting ubuntu partitions with gparted, I got an ubuntu splash screen and a whole lot of ubuntu boot options. Somehow these were all contained in my Arch's /boot/grub/menu.lst. Arch is all on one partition and no separate boot partition (which I had with Ubuntu - maybe I haven't deleted that and this is the problem?). Will need to check that out.
    I can chroot into Arch and did the following -
    grub> find /boot/grub/stage1
    (hd0,5)
    grub> root (hd0,5)
    Filesystem type is ext2fs, partition type 0x83
    grub> setup (hd0)
    Checking if "/boot/grub/stage1" exists... yes
    Checking if "/boot/grub/stage2" exists... yes
    Checking if "/boot/grub/e2fs_stage1_5" exists... yes
    Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 16 sectors are embedded.
    succeeded
    Running "install /boot/grub/stage1 (hd0) (hd0)1+16 p (hd0,5)/boot/grub/stage2 /boot/grub/menu.lst"... succeed
    ed
    Done.
    grub>
    The Arch /boot/grub/menu.lst had a whole lot of ubuntu stuff in it but I edited to the following -
    # menu.lst - See: grub(8), info grub, update-grub(8)
    # grub-install(8), grub-floppy(8),
    # grub-md5-crypt, /usr/share/doc/grub
    # and /usr/share/doc/grub-doc/.
    ## default num
    # Set the default entry to the entry number NUM. Numbering starts from 0, and
    # the entry number 0 is the default if the command is not used.
    # You can specify 'saved' instead of a number. In this case, the default entry
    # is the entry saved with the command 'savedefault'.
    # WARNING: If you are using dmraid do not use 'savedefault' or your
    # array will desync and will not let you boot your system.
    default 0
    ## timeout sec
    # Set a timeout, in SEC seconds, before automatically booting the default entry
    # (normally the first entry defined).
    timeout 3
    ## hiddenmenu
    # Hides the menu by default (press ESC to see the menu)
    hiddenmenu
    # Pretty colours
    #color cyan/blue white/blue
    ## password ['--md5'] passwd
    # If used in the first section of a menu file, disable all interactive editing
    # control (menu entry editor and command-line) and entries protected by the
    # command 'lock'
    # e.g. password topsecret
    # password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
    # password topsecret
    # examples
    # title Windows 95/98/NT/2000
    # root (hd0,0)
    # makeactive
    # chainloader +1
    # title Linux
    # root (hd0,1)
    # kernel /vmlinuz root=/dev/hda2 ro
    # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
    ## default grub root device
    ## e.g. groot=(hd0,0)
    # groot=(hd0,3)
    title Arch uuid
    #root (hd0,5)
    uuid d15cf4f9-18ca-4ec5-95bc-db0f6f264736
    kernel /boot/vmlinuz26 root=/dev/sda6 ro vga=775
    intrd /boot/kernel26.img
    title Arch hd
    root (hd0,5)
    kernel /boot/vmlinuz26 root=/dev/sda6
    intrd /boot/kernel26.img
    I have a bootinfo script which gives the following (from the chroot environment) -
    Boot Info Script 0.55 dated February 15th, 2010
    ============================= Boot Info Summary: ==============================
    => Grub 0.97 is installed in the MBR of /dev/sda and looks on the same drive
    in partition #6 for /boot/grub/stage2 and /boot/grub/menu.lst.
    => No boot loader is installed in the MBR of /dev/sdb
    sda1: _________________________________________________________________________
    File system: swap
    Boot sector type: -
    Boot sector info:
    sda2: _________________________________________________________________________
    File system: Extended Partition
    Boot sector type: -
    Boot sector info:
    sda5: _________________________________________________________________________
    File system: ext3
    Boot sector type: -
    Boot sector info:
    Mounting failed:
    mount: /dev/sda5 already mounted or sda5 busy
    sda6: _________________________________________________________________________
    File system: ext3
    Boot sector type: -
    Boot sector info:
    Mounting failed:
    mount: /dev/sda5 already mounted or sda5 busy
    mount: /dev/sda6 already mounted or sda6 busy
    sda7: _________________________________________________________________________
    File system: ext3
    Boot sector type: -
    Boot sector info:
    Operating System:
    Boot files/dirs:
    sda3: _________________________________________________________________________
    File system: ext3
    Boot sector type: -
    Boot sector info:
    Operating System: Ubuntu 10.04.1 LTS
    Boot files/dirs: /etc/fstab
    sda4: _________________________________________________________________________
    File system: ext3
    Boot sector type: -
    Boot sector info:
    Operating System:
    Boot files/dirs: /grub/menu.lst /grub/grub.cfg /grub/core.img
    sdb1: _________________________________________________________________________
    File system: xfs
    Boot sector type: -
    Boot sector info:
    Operating System:
    Boot files/dirs:
    =========================== Drive/Partition Info: =============================
    Drive: sda ___________________ _____________________________________________________
    Disk /dev/sda: 750.2 GB, 750155292160 bytes
    255 heads, 63 sectors/track, 91201 cylinders, total 1465147055 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    Partition Boot Start End Size Id System
    /dev/sda1 417,690 6,554,519 6,136,830 82 Linux swap / Solaris
    /dev/sda2 25,414,954 1,465,144,064 1,439,729,111 5 Extended
    /dev/sda5 25,414,956 1,360,287,809 1,334,872,854 83 Linux
    /dev/sda6 1,360,287,873 1,423,198,349 62,910,477 83 Linux
    /dev/sda7 1,423,198,413 1,465,144,064 41,945,652 83 Linux
    /dev/sda3 6,554,520 25,414,829 18,860,310 83 Linux
    /dev/sda4 * 63 417,689 417,627 83 Linux
    Drive: sdb ___________________ _____________________________________________________
    Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
    255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    Partition Boot Start End Size Id System
    /dev/sdb1 2,048 1,953,523,711 1,953,521,664 83 Linux
    blkid -c /dev/null: ____________________________________________________________
    Device UUID TYPE LABEL
    /dev/loop0 squashfs
    /dev/sda1 2a95d85a-45fe-4584-88dd-0ee20e651ec5 swap
    /dev/sda2: PTTYPE="dos" PART_ENTRY_SCHEME="dos" PART_ENTRY_TYPE="0x5" PART_ENTRY_NUMBER="2"
    /dev/sda3 32495e1a-227c-4d23-9f63-b1319def0dd9 ext3
    /dev/sda4 d6dc69b0-967d-4886-b62d-8c0d6be06b41 ext3
    /dev/sda5 37971286-b8d3-4a1b-9f94-4008288fed6d ext3 data
    /dev/sda6 d15cf4f9-18ca-4ec5-95bc-db0f6f264736 ext3 30GB-02
    /dev/sda7 eb736131-b558-4404-9b83-7f1e6d9e76ae ext3 var
    /dev/sda: PTTYPE="dos"
    /dev/sdb1 0e83045d-a0bd-4d36-b61d-bdb905130dc2 xfs 1TB-04
    /dev/sdb: PTTYPE="dos"
    ============================ "mount | grep ^/dev output: ===========================
    Device Mount_Point Type Options
    /dev/sda12 / ext3 (rw,commit=0)
    =============================== sda3/etc/fstab: ===============================
    # /etc/fstab: static file system information.
    # <file system> <mount point> <type> <options> <dump> <pass>
    proc /proc proc defaults 0 0
    # /dev/sda1 = swap
    /dev/sda1 none swap sw 0 0
    # /dev/sda3 = root
    #UUID=32495e1a-227c-4d23-9f63-b1319def0dd9
    /dev/sda3 / ext3 relatime,errors=remount-ro 0 1
    # /dev/sda4 = boot
    # UUID=d6dc69b0-967d-4886-b62d-8c0d6be06b41
    /dev/sda4 /boot ext3 relatime 0 2
    # /dev/sda5 = home
    # UUID=670eee83-0a3e-429c-863f-b9ecced9f97e
    /dev/sda5 /home ext3 relatime 0 2
    #/dev/sda6
    #UUID=37971286-b8d3-4a1b-9f94-4008288fed6d
    /dev/sda6 /home/ben/Data ext3 defaults,relatime 0 0
    # /dev/sda7
    # UUID=fdb14ca4-d71d-489f-a00e-6e608770674c
    /dev/sda7 /var ext3 relatime 0 2
    # /dev/sda8
    /dev/sda8 /opt ext3 relatime 0 2
    # /dev/sda10 - Arch
    /dev/sda10 /mnt/arch ext3 relatime 0 2
    # Not sure what this is doing here
    # Have commented it out - May be the reason why xbmc and mythtv were crashing on dvd insert and play
    # /dev/hda /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
    # /dev/sde1
    # uuid appears to be 644406B3570C1846 -> ../../sde1
    #/dev/sde1 /home/ben/Data/TVRecordings-1TB01 xfs defaults,relatime 0 0
    #1TB-01
    UUID=76f3823a-81dc-45c9-a0b7-2bc6c3beb2f8 /media/1TB-01 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
    d defaults, relatime
    # 1TB-02
    UUID=59cbf7a1-7008-40d0-96ed-c6f231823d4f /media/1TB-02 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
    d defaults, relatime
    # 1TB-03
    UUID=0e936800-3c53-4b87-abc8-19be0ffca7f9 /media/1TB-03 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
    d defaults, relatime
    # 750GB-02 ext3 Partition
    # UUID giving problems, trying with dev
    # UUID=c23b9c9a-66fc-4256-9211-73156c1ac64a /media/750GB-02_ext3 ext3 defaults,relatime 0 0
    /dev/sde2 /media/750GB-02_ext3 ext3 defaults,relatime 0 0
    ============================= sda4/grub/menu.lst: =============================
    # menu.lst - See: grub(8), info grub, update-grub(8)
    # grub-install(8), grub-floppy(8),
    # grub-md5-crypt, /usr/share/doc/grub
    # and /usr/share/doc/grub-doc/.
    ## default num
    # Set the default entry to the entry number NUM. Numbering starts from 0, and
    # the entry number 0 is the default if the command is not used.
    # You can specify 'saved' instead of a number. In this case, the default entry
    # is the entry saved with the command 'savedefault'.
    # WARNING: If you are using dmraid do not use 'savedefault' or your
    # array will desync and will not let you boot your system.
    default 0
    ## timeout sec
    # Set a timeout, in SEC seconds, before automatically booting the default entry
    # (normally the first entry defined).
    timeout 3
    ## hiddenmenu
    # Hides the menu by default (press ESC to see the menu)
    hiddenmenu
    # Pretty colours
    #color cyan/blue white/blue
    ## password ['--md5'] passwd
    # If used in the first section of a menu file, disable all interactive editing
    # control (menu entry editor and command-line) and entries protected by the
    # command 'lock'
    # e.g. password topsecret
    # password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
    # password topsecret
    # examples
    # title Windows 95/98/NT/2000
    # root (hd0,0)
    # makeactive
    # chainloader +1
    # title Linux
    # root (hd0,1)
    # kernel /vmlinuz root=/dev/hda2 ro
    # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
    ### BEGIN AUTOMAGIC KERNELS LIST
    ## lines between the AUTOMAGIC KERNELS LIST markers will be modified
    ## by the debian update-grub script except for the default options below
    ## DO NOT UNCOMMENT THEM, Just edit them to your needs
    ## ## Start Default Options ##
    ## default kernel options
    ## default kernel options for automagic boot options
    ## If you want special options for specific kernels use kopt_x_y_z
    ## where x.y.z is kernel version. Minor versions can be omitted.
    ## e.g. kopt=root=/dev/hda1 ro
    ## kopt_2_6_8=root=/dev/hdc1 ro
    ## kopt_2_6_8_2_686=root=/dev/hdc2 ro
    # kopt=root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro
    ## default grub root device
    ## e.g. groot=(hd0,0)
    # groot=(hd0,3)
    ## should update-grub create alternative automagic boot options
    ## e.g. alternative=true
    ## alternative=false
    # alternative=true
    ## should update-grub lock alternative automagic boot options
    ## e.g. lockalternative=true
    ## lockalternative=false
    # lockalternative=false
    ## additional options to use with the default boot option, but not with the
    ## alternatives
    ## e.g. defoptions=vga=791 resume=/dev/hda5
    # defoptions=quiet splash
    ## should update-grub lock old automagic boot options
    ## e.g. lockold=false
    ## lockold=true
    # lockold=false
    ## Xen hypervisor options to use with the default Xen boot option
    # xenhopt=
    ## Xen Linux kernel options to use with the default Xen boot option
    # xenkopt=console=tty0
    ## altoption boot targets option
    ## multiple altoptions lines are allowed
    ## e.g. altoptions=(extra menu suffix) extra boot options
    ## altoptions=(recovery) single
    # altoptions=(recovery mode) single
    ## controls how many kernels should be put into the menu.lst
    ## only counts the first occurence of a kernel, not the
    ## alternative kernel options
    ## e.g. howmany=all
    ## howmany=7
    # howmany=all
    ## should update-grub create memtest86 boot option
    ## e.g. memtest86=true
    ## memtest86=false
    # memtest86=true
    ## should update-grub adjust the value of the default booted system
    ## can be true or false
    # updatedefaultentry=false
    ## should update-grub add savedefault to the default options
    ## can be true or false
    # savedefault=false
    ## ## End Default Options ##
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-26-generic
    root (hd0,3)
    kernel /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-26-generic
    quiet
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-26-generic (recovery mode)
    root (hd0,3)
    kernel /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    initrd /initrd.img-2.6.32-26-generic
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-24-generic
    root (hd0,3)
    kernel /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-24-generic
    quiet
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-24-generic (recovery mode)
    root (hd0,3)
    kernel /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    initrd /initrd.img-2.6.32-24-generic
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-23-generic
    root (hd0,3)
    kernel /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-23-generic
    quiet
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-23-generic (recovery mode)
    root (hd0,3)
    kernel /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    initrd /initrd.img-2.6.32-23-generic
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-22-generic
    root (hd0,3)
    kernel /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-22-generic
    quiet
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-22-generic (recovery mode)
    root (hd0,3)
    kernel /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    initrd /initrd.img-2.6.32-22-generic
    title Ubuntu 10.04.1 LTS, memtest86+
    root (hd0,3)
    kernel /memtest86+.bin
    quiet
    ### END DEBIAN AUTOMAGIC KERNELS LIST
    ============================= sda4/grub/grub.cfg: =============================
    # DO NOT EDIT THIS FILE
    # It is automatically generated by /usr/sbin/grub-mkconfig using templates
    # from /etc/grub.d and settings from /etc/default/grub
    ### BEGIN /etc/grub.d/00_header ###
    if [ -s $prefix/grubenv ]; then
    load_env
    fi
    set default="0"
    if [ ${prev_saved_entry} ]; then
    set saved_entry=${prev_saved_entry}
    save_env saved_entry
    set prev_saved_entry=
    save_env prev_saved_entry
    set boot_once=true
    fi
    function savedefault {
    if [ -z ${boot_once} ]; then
    saved_entry=${chosen}
    save_env saved_entry
    fi
    function recordfail {
    set recordfail=1
    if [ -n ${have_grubenv} ]; then if [ -z ${boot_once} ]; then save_env recordfail; fi; fi
    insmod ext2
    set root='(hd0,3)'
    search --no-floppy --fs-uuid --set 32495e1a-227c-4d23-9f63-b1319def0dd9
    if loadfont /usr/share/grub/unicode.pf2 ; then
    set gfxmode=640x480
    insmod gfxterm
    insmod vbe
    if terminal_output gfxterm ; then true ; else
    # For backward compatibility with versions of terminal.mod that don't
    # understand terminal_output
    terminal gfxterm
    fi
    fi
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    set locale_dir=($root)/grub/locale
    set lang=en
    insmod gettext
    if [ ${recordfail} = 1 ]; then
    set timeout=-1
    else
    set timeout=10
    fi
    ### END /etc/grub.d/00_header ###
    ### BEGIN /etc/grub.d/05_debian_theme ###
    set menu_color_normal=white/black
    set menu_color_highlight=black/light-gray
    ### END /etc/grub.d/05_debian_theme ###
    ### BEGIN /etc/grub.d/10_linux ###
    menuentry 'Ubuntu, with Linux 2.6.32-26-generic' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-26-generic
    menuentry 'Ubuntu, with Linux 2.6.32-26-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
    -class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    echo 'Loading Linux 2.6.32-26-generic ...'
    linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    echo 'Loading initial ramdisk ...'
    initrd /initrd.img-2.6.32-26-generic
    menuentry 'Ubuntu, with Linux 2.6.32-24-generic' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    linux /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-24-generic
    menuentry 'Ubuntu, with Linux 2.6.32-24-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
    -class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    echo 'Loading Linux 2.6.32-24-generic ...'
    linux /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    echo 'Loading initial ramdisk ...'
    initrd /initrd.img-2.6.32-24-generic
    menuentry 'Ubuntu, with Linux 2.6.32-23-generic' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    linux /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-23-generic
    menuentry 'Ubuntu, with Linux 2.6.32-23-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
    -class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    echo 'Loading Linux 2.6.32-23-generic ...'
    linux /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    echo 'Loading initial ramdisk ...'
    initrd /initrd.img-2.6.32-23-generic
    menuentry 'Ubuntu, with Linux 2.6.32-22-generic' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    linux /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-22-generic
    menuentry 'Ubuntu, with Linux 2.6.32-22-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
    -class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    echo 'Loading Linux 2.6.32-22-generic ...'
    linux /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    echo 'Loading initial ramdisk ...'
    initrd /initrd.img-2.6.32-22-generic
    ### END /etc/grub.d/10_linux ###
    ### BEGIN /etc/grub.d/20_memtest86+ ###
    menuentry "Memory test (memtest86+)" {
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    linux16 /memtest86+.bin
    menuentry "Memory test (memtest86+, serial console 115200)" {
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    linux16 /memtest86+.bin console=ttyS0,115200n8
    ### END /etc/grub.d/20_memtest86+ ###
    ### BEGIN /etc/grub.d/30_os-prober ###
    menuentry "Arch Linux (on /dev/sda10)" {
    insmod ext2
    set root='(hd0,10)'
    search --no-floppy --fs-uuid --set 26851879-58d1-4d65-90b4-e0845fe1176c
    linux /boot/vmlinuz26 root=/dev/sda10 ro
    initrd /boot/kernel26.img
    menuentry "Arch Linux Fallback (on /dev/sda10)" {
    insmod ext2
    set root='(hd0,10)'
    search --no-floppy --fs-uuid --set 26851879-58d1-4d65-90b4-e0845fe1176c
    linux /boot/vmlinuz26 root=/dev/sda10 ro
    initrd /boot/kernel26-fallback.img
    #### END /etc/grub.d/30_os-prober ###
    ### BEGIN /etc/grub.d/40_custom ###
    # This file provides an easy way to add custom menu entries. Simply type the
    # menu entries you want to add after this comment. Be careful not to change
    # the 'exec tail' line above.
    # From Arch grub menu.lst
    # (0) Arch Linux
    #title Arch Linux [/boot/vmlinuz26]
    #root (hd0,0)
    #kernel /vmlinuz26 root=/dev/sda3 ro
    #initrd /kernel26.img
    #Note: With a separate boot partition, omit /boot from the path, (i.e. type set prefix=(hdX,Y)/grub and insmod
    (hdX,Y)/grub/linux.mod).
    #This introduces the "linux" and "initrd" commands, which should be familiar (see #Configuration).
    #An example, booting Arch Linux:
    #set root=(hd0,5)
    #linux /boot/vmlinuz26 root=/dev/sda5
    #initrd /boot/kernel26.img
    #boot
    ###menuentry "Arch1" {
    ###insmod ext2
    ###set root='(hd0,10)'
    #search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
    PARTITION
    #linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
    UBUNTU THIS IS THE ROOT PARTITION
    #initrd /initrd.img-2.6.32-26-generic
    ###search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UU
    ID
    ###linux /boot/vmlinuz-26 root=635d7d02-3f5b-4af6-9c74-16b2af8cc7fd ro quiet splash # ARCH'S ROOT UUID
    ###initrd /boot/kernel26.img
    # /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
    ###menuentry "Arch2" {
    ###insmod ext2
    ###set root='(hd0,4)' #= TRYING UBUNTU'S BOOT
    #search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
    PARTITION
    #linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
    UBUNTU THIS IS THE ROOT PARTITION
    #initrd /initrd.img-2.6.32-26-generic
    #search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UUID
    ###linux /boot/vmlinuz-26 root=/dev/sda10 ro quiet splash # TRYING ARCH'S ROOT DEVICE FORMAT
    ###initrd /boot/kernel26.img
    # /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
    ###menuentry "Arch3" {
    ###insmod ext2
    ###set root='(hd0,10)' #= TRYING UBUNTU'S BOOT IN HD FORMAT
    #search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
    PARTITION
    #linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
    UBUNTU THIS IS THE ROOT PARTITION
    #initrd /initrd.img-2.6.32-26-generic
    #search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UUID
    ###linux /boot/vmlinuz-26 root=/dev/sda10 ro quiet splash # TRYING ARCH'S ROOT DEVICE FORMAT
    ###initrd /boot/kernel26.img
    # /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
    ### END /etc/grub.d/40_custom ###
    =================== sda4: Location of files loaded by Grub: ===================
    .0GB: grub/core.img
    .0GB: grub/grub.cfg
    .0GB: grub/menu.lst
    .0GB: grub/stage2
    .0GB: initrd.img-2.6.32-22-generic
    .0GB: initrd.img-2.6.32-23-generic
    .1GB: initrd.img-2.6.32-24-generic
    .1GB: initrd.img-2.6.32-26-generic
    .0GB: vmlinuz26
    .0GB: vmlinuz-2.6.32-22-generic
    .0GB: vmlinuz-2.6.32-23-generic
    .1GB: vmlinuz-2.6.32-24-generic
    .0GB: vmlinuz-2.6.32-26-generic
    =============================== StdErr Messages: ===============================
    No volume groups found
    mdadm: No arrays found in config file or automatically
    [/quote]
    Output of fdisk -l from chroot is -
    [quote]Disk /dev/sda: 750.2 GB, 750155292160 bytes
    255 heads, 63 sectors/track, 91201 cylinders, total 1465147055 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x0000b084
    Device Boot Start End Blocks Id System
    /dev/sda1 417690 6554519 3068415 82 Linux swap / Solaris
    /dev/sda2 25414954 1465144064 719864555+ 5 Extended
    /dev/sda3 6554520 25414829 9430155 83 Linux
    /dev/sda4 * 63 417689 208813+ 83 Linux
    /dev/sda5 25414956 1360287809 667436427 83 Linux
    /dev/sda6 1360287873 1423198349 31455238+ 83 Linux
    /dev/sda7 1423198413 1465144064 20972826 83 Linux
    Partition table entries are not in disk order
    Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
    255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disk identifier: 0x00025bd3
    Device Boot Start End Blocks Id System
    /dev/sdb1 2048 1953523711 976760832 83 Linux
    I need to post this now and come back from a different machine to note the error messages I am now getting on boot. ...
    Note that when I boot and press esc to get the menu I get the menu.lst I created (in the second quote) above in /dev/sda6, ie the one with the Arch hd and uuid entries - so grub is looking there and finding that menu.lst, but something goes wrong after that.
    OK. Have now booted the machine and after pressing esc and selecting the uuid entry (the same thing happens with the hd entry) I get a whole lot of stuff, but what seems relevant is (typing it out) -
    List of all partitions:
    No filesystem could mount root, tried:
    Kernel panic - not syncing: VS: Unable to mount root fs on unknown-block(0,0)
    Pid: 1, comm: swapper Not tainted 2.6.39-Arch #1
    If anyone can help I'd really appreciate it. This is my MythTV machine so the WAF is about to take a big dive!
    If I could just install grub to the MBR as if this was a new installation of Arch that would be great.
    I am really lost as to what is going on, which I'm sure is evident.
    Thanks a lot
    belbo
    Last edited by belbo (2011-08-12 13:31:23)

    Hi. Unfortunately that didn't help.
    So next, based on this post https://wiki.archlinux.org/index.php/Ke … el_version I chrooted into Arch and (a) rolled back and (b) reinstalled my kernel but that didn't help either. I suspected it wouldn't because the kernel was working fine before I deleted the partitions in question.
    [2011-08-08 23:32] ==> Image generation successful
    [2011-08-08 23:32] upgraded kernel26 (2.6.39.3-1 -> 2.6.39.3-1)
    I then did a pacman -Suy and the linux package has now replaced kernel26. ( See this wiki entry http://www.archlinux.org/news/changes-t … filenames/). I didn't change anything in menu.lst owing to this and it seems there is no need to. Unfortunately this hasn't helped either - still getting the kernel panic. 
    Pacman.log relating to the new kernel package below -
    [2011-08-09 00:22] Running 'pacman -Suy'
    [2011-08-09 00:22] synchronizing package lists
    [2011-08-09 00:23] starting full system upgrade
    [2011-08-09 00:23] Running 'pacman -Suy'
    [2011-08-09 00:23] synchronizing package lists
    [2011-08-09 00:23] starting full system upgrade
    [2011-08-09 00:26] removed python-mygpoclient (1.5-1)
    [2011-08-09 00:26] removed kernel26 (2.6.39.3-1)
    [2011-08-09 00:26] warning: /boot/grub/menu.lst installed as /boot/grub/menu.lst.pacnew
    [2011-08-09 00:26] upgraded grub (0.97-17 -> 0.97-19)
    [2011-08-09 00:26] upgraded icu (4.8-1 -> 4.8.1-1)
    [2011-08-09 00:26] upgraded linux-firmware (20110512-2 -> 20110727-1)
    [2011-08-09 00:26] >>> Updating module dependencies. Please wait ...
    [2011-08-09 00:26] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
    [2011-08-09 00:26] ==> Building image from preset: 'default'
    [2011-08-09 00:26] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
    [2011-08-09 00:26] ==> Starting build: 3.0-ARCH
    [2011-08-09 00:26] -> Parsing hook: [base]
    [2011-08-09 00:26] -> Parsing hook: [udev]
    [2011-08-09 00:26] -> Parsing hook: [autodetect]
    [2011-08-09 00:26] -> Parsing hook: [pata]
    [2011-08-09 00:26] -> Parsing hook: [scsi]
    [2011-08-09 00:26] -> Parsing hook: [sata]
    [2011-08-09 00:26] -> Parsing hook: [filesystems]
    [2011-08-09 00:26] -> Parsing hook: [usbinput]
    [2011-08-09 00:26] ==> Generating module dependencies
    [2011-08-09 00:26] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
    [2011-08-09 00:26] 7079 blocks
    [2011-08-09 00:26] ==> Image generation successful
    [2011-08-09 00:26] ==> Building image from preset: 'fallback'
    [2011-08-09 00:26] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
    [2011-08-09 00:26] ==> Starting build: 3.0-ARCH
    [2011-08-09 00:26] -> Parsing hook: [base]
    [2011-08-09 00:26] -> Parsing hook: [udev]
    [2011-08-09 00:26] -> Parsing hook: [pata]
    [2011-08-09 00:26] -> Parsing hook: [scsi]
    [2011-08-09 00:26] -> Parsing hook: [sata]
    [2011-08-09 00:26] -> Parsing hook: [filesystems]
    [2011-08-09 00:26] -> Parsing hook: [usbinput]
    [2011-08-09 00:26] ==> Generating module dependencies
    [2011-08-09 00:26] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
    [2011-08-09 00:26] 23360 blocks
    [2011-08-09 00:26] ==> Image generation successful
    [2011-08-09 00:26] installed linux (3.0.1-1)
    I don't think I've mentioned that my old menu.lst seems to have disappeared and so must have been on one of the partitions that were deleted. I did have 2 Arch installations when I was setting things up months ago and that menu.lst may have been on the other partition but pointing to this partiton's kernel for booting. Presumably that's possible since this partiton is definitely the one I have been using for the last several months (confirmed by log and other files updated in the last few days etc). Even so, I suppose that probably wouldn't be relevant to this issue, since grub is finding the menu.lst on this partition when it boots so it is looking in the intended place now.
    It seems I'm at a bit of a dead end. It seems these kernel panics are usually because there is something wrong with the kernel - which there wasn't with mine (and presumably the kernel in the new linux package is fine) or there is a typo in menu.lst (I can't see one and nobody has pointed one out yet) or menu.lst is pointing to the wrong partition (mine is pointing to the same partition and /boot directory that is found by grub - which is where my boot image is located - so it seems to be correct). I have nevertheless tried editing the menu.lst entry when booting to boot from different partitions but so far that hasn't worked either.
    If anybody has other ideas I'd really appreciate it.
    If not, some suggestions on re-installing would also be appreciated. I have a recent tar archive of the partition, but presumably reinstalling that wouldn't be of much use since it would just put back what is currently there. I guess that I need to format the partition, create a separate boot partition, do a fresh install of Arch into the formatted partition (and with boot in the new boot partition). And then restore my tar backup (excluding the boot directory) into the formatted partition?
    Any assistance greatly appreciated.
    Thanks
    belbo
    Last edited by belbo (2011-08-08 23:17:49)

  • Kernel Panic, but I can still boot into windows? :(

    Hi folks,
    2007?'ish MBP 2.2
    machine (normally) boots right in to SL (latest rev).
    holding option, I can choose SL or Windows XP.
    I have a firmware password set up (i know the password if i need it)
    the problem: when i turn my mac on, it will not boot into Mac right away. I get an error that it's "unable to find driver for this platform: \ "ACPI\".\n"@/SourceCache/xnu/xnu-1486.2.11/iokit/Kernel/IOPlatformExpert.cpp.:1 389
    there's more, but I won't type it just yet b/c I just thought of a possible reason:
    I was reviewing photos with a client for a slideshow (everything is backed up..no worries) and she had a thumb drive with more photos. I plugged it in the USB, but it wouldn't read or open in finder.
    No worries - I ran downstairs to my mac pro, it worked. Dragged the pics off.
    Shut down my macbook pro b/c I wasn't using it and when I tried to turn it on later, this problem is there.
    What I've tried:
    resetting SMC
    resetting PRAM
    can't do the TDM - read the article about needing to install the software to open passwords, but hard to do if the computer is down (unless they mean installing it on the machine from which I'm trying to access it?)
    i tried holding option to key in my firmware password, but the same thing happens - can't access the Mac side of things. I can access the Windows section and as I'm typing this, it looks like I'm able to access the install disc
    Just thought I would post this for 2 reasons:
    1. to see if there's anything else I can do (I am going to try disk utilities to repair the disc)
    and 2. to help anyone else out in case they have the same issue.
    Cheers,
    Keebler

    Backup what you can, boot from a compatible installer DVD, erase the hard drive, then reinstall OS X.
    Alternatively, you can try the following:
    How to Perform an Archive and Install
    An Archive and Install will NOT erase your hard drive, but you must have sufficient free space for a second OS X installation which could be from 3-9 GBs depending upon the version of OS X and selected installation options. The free space requirement is over and above normal free space requirements which should be at least 6-10 GBs. Read all the linked references carefully before proceeding.
    1. Be sure to use Disk Utility first to repair the disk before performing the Archive and Install.
    Repairing the Hard Drive and Permissions
    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 Installer menu (Utilities menu for Tiger.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported, then quit DU and return to the installer.
    2. Do not proceed with an Archive and Install if DU reports errors it cannot fix. In that case use Disk Warrior and/or TechTool Pro to repair the hard drive. If neither can repair the drive, then you will have to erase the drive and reinstall from scratch.
    3. Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When you reach the screen to select a destination drive click once on the destination drive then click on the Option button. Select the Archive and Install option. You have an option to preserve users and network preferences. Only select this option if you are sure you have no corrupted files in your user accounts. Otherwise leave this option unchecked. Click on the OK button and continue with the OS X Installation.
    4. Upon completion of the Archive and Install you will have a Previous System Folder in the root directory. You should retain the PSF until you are sure you do not need to manually transfer any items from the PSF to your newly installed system.
    5. After moving any items you want to keep from the PSF you should delete it. You can back it up if you prefer, but you must delete it from the hard drive.
    6. You can now download a Combo Updater directly from Apple's download site to update your new system to the desired version as well as install any security or other updates. You can also do this using Software Update.

  • Can't boot into Windows 8 Single Language 64 bit or access the BIOS screen with the F1 key

    I have in my possession right now a Lenovo E49, Model name: 3464
    I am unable to access the BIOS settings at POST by pressing the F1 key.  Neither does it respond to the Enter key when it displays the message "To interrupt normal startup, Press Enter".  I am also unable to boot into the installed OS Windows 8 Single Language 64 bit.
    For your informtion, these are the events that led to this issue.
    I accessed the BIOS settings at startup using the CHANGE PC SETTINGS option in the CHARMS menu in Windows 8 Single Languge 64 bit followed by GENERAL and ADVANCED STARTUP.  Then I chose Restart Now.  Windows restarted to produce the startup screen where I chose Troubleshoot, followed by Advanced Options and UEFI Firmware Settings, followed by Restart.  This took me to the BIOS settings screen. Once there I changed the boot settings in BIOS so that SECURE BOOT was turnned OFF.  It was in ON state prior to that.  I also changed the BOOT MODE to LEGACY ONLY.  I also changed the BOOT ORDER to boot from DVD drive first followed by the Hard Disk and USB Hard Disk.  I saved the changes by pressing F10.
    Now the computer is able to boot from the DVD Drive.  I tested this by inserting a Windows 7 Repair DVD and also a Linux Live DVD.  Mind you, I didn't mke any changes to the Hard Drive.  I'm also able to boot from a USB Hard Disk.  This too was tested by inserting a bootable USB HD that had both Windows 7 and Windows 8 OS installers.  I used only the command prompt feature in the Repair option on the Windows 8 installer to ensure that I could access the partitions on the HD.  I did not in any way install Windows 7 or 8 on the HD.
    If there is no bootable DVD or USB HD inserted, the laptop is involved in a loop that restarts followed by a message that says the following:
    "Intel Undi, PXE-2.1 (build 083)
    Copyright (C) 1997-2000 Intel Corporation
    This product is covered by one or more of the following patents:
    US5, 307, 459,  US5, 434, 872,  US5, 732, 094,  US6, 570, 884,  US6, 115, 776 and US6, 327, 625
    Realtek PCIe GBE Family Controller Series v2.41 (06/08/11)
    PXE-E61: Media test failure, check cable
    PXE-M0F: Exiting PXE ROM."
    I am positive that the current state of the BIOS is such that it does not accept any input keys like F1 and F12 at POST so that the BIOS can only be accessed through Change PC Settings in Windows 8 as I had done prior to the occurence of the issue.  Since I cannot boot up Windows 8 I cannot use this method to access the BIOS.  And since it is not possible at this stage to access the BIOS settings through the F1 key, I believe Lenovo must have surely provided another alternative to enter the BIOS.  Can you kindly tell me what other way is there to do this.  In earlier days, one could reset the BIOS by shorting the BIOS through pins on the motherboard.  Is that possible now?  Or is there some Lenovo BIOS utilily that enables me to change the BIOS setting to boot with Legacy and UEFI?  Or do I have to install Windows 8.1 64 bit in Legacy mode?

    I'll see if another member of the team can jump in here and offer more help...
    What I might imagine is that you can only access BIOS from a cold boot. Windows 8/8.1 have hybrid shutdown and don't completely shut down the machine normally, so even when it powers off, it isn't fully off and the next boot is not really a cold boot.
    Please see this KB.  I realize this assumes you can get into windows.
    As you suggest, it also seems as though you have set legacy vs UEFI and that may be why your drive is not currently booting.   Can you remove the battery on your system?  If not, is there a reset hole on the bottom?  Removing battery and AC and pressing and holding the power button several times, then re-attach AC and Battery and try to restart and press F1 to get into BIOS.  (Not familiar with models that use enter for BIOS).
    Mark
    ThinkPads: S30, T43, X60t, X1, W700ds, IdeaPad Y710, IdeaCentre: A300, IdeaPad K1
    Mark Hopkins
    Program Manager, Lenovo Social Media (Services)
    twitter @lenovoforums
    English Community   Deutsche Community   Comunidad en Español   Русскоязычное Сообщество

  • Can't boot into safe mode or prompt login window, need help.

    Hello all,
    This is cross-posted from the installations and set-up list.
    Can anyone suggest a remedy for what's ailing this powerbook. its a g4 powerbook, i don't have much more info other than that. all indications are that it is running 10.2.6, although i was told that it had been updated to 10.2.8, its possible that it was updated only to 10.2.6. following the update, you get to the apple and spinning pinwheel screen and it will not proceed. literally, the pinwheel will spin for 24 hours+.
    it looks like it gets to the point of the startup(login) items and hangs indefinitely. ie it will
    if i start in verbose mode it will, give some clues:
    truncated or malformed library: /System/Libray/Frameworks/Security.frameworks/Versions/A/Security
    Some starup items failed to launch due to conflicts
    /usr/libexec/crashreporterd: crashdump terminated by signal 5
    init: getty repeating too quickly on port /dev/console, sleeping
    /usr/libexec/crashreporterd: crashdump terminated by signal 5
    last message repeated 10 times
    /usr/libexec/crashreporterd: crashdump terminated by signal 5
    init: getty repeating too quickly on port /dev/console, sleeping
    /usr/libexec/crashreporterd: crashdump terminated by signal 5
    last message repeated 5 times
    this will continue to be repeated and i assume a new core.## file is sent to the /cores folder, until the hard drive is maxed out.
    I can boot in single user mode and everything is fine but i cannot boot into safe mode.
    fsck says the disk is fine, as does disk first aid, i have also corrected permissions, and followed many of the things that have been previously posted.
    It looks like ther are conflicts with some startup items, what can i move from the starup folder and is best not to be touched?
    what about the truncated library message?
    also can i update to 10.2.8 from the single user mode, if i cannot get into safe mode?
    any suggestions?
    thanks in advance-
    todd

    I have solved this problem. I mounted the laptop in target mode and replaced this file:
    /System/Library/Frameworks/Security.framework/Versions/A/Security
    with the equivalent file from a machine running 10.2.8.
    It booted all the way through then i upgraded to 10.2.8.

  • Dual boot 10 & 8.1 Had to reinstall 8.1 now can't boot into 10

    I dual boot win 8.1 and win 10...............I had to reinstall 8.1 and now even though I've added the entry for Win 10 in the boot menu it fails to load with a driver signature verification failure on the windows loader file. I have found out how to disable
    driver signature verification but I have to reboot from INSIDE windows to do it. I can boot into win 8.1 just not win 10
    Mark Carroll

    I got it at Get IntoPC  but if you have fast ring enabled on build 10041 it installs 10049 through windows update
    Mark Carroll
    Microsoft is the ONLLY source for Win 10 TP ISO.
    If MS has not released it, then what you get is an illegal copy and probably not working .
    I know how one can get 10049 installed via Windows Update. That has nothing to do with your case. You were using a 10049 ISO which has yet to be released by Microsoft.

  • Can't boot into desktop

    Hi, I own an iMac 20-in early 2008. I've installed Mavericks (10.9.5) on it and it's been running perfectly being used by our accounting person. One day the computer boot up and the usual chime & apple logo shows up. The loading circle shows up indicating that it's loading all the system files etc, then when it disappears just as it's about to go to the desktop view it's stuck. The Apple logo is still there, but the display slightly dims (kinda like when colorsync/calibration kicks in).
    I tried Verbose Mode (Command + V) and it loads all the kernels without a problem. Once it loaded, back to the same grey screen with Apple logo and it just stuck there.
    I've tried booting into safe mode and it works fine so it's probably not hardware.
    I can't start Diagnostic Test on it since I don't have the CD anymore.
    So since most of the files are store on a server, I did a target disk mode, backed up some small amount of data and reformated the computer using a USB stick loaded with a freshly downloaded Mavericks.
    Installation went on without a problem, but as soon as it restarted, it did the same thing again.
    Here's what I've done so far:
    Reset PRAM (cmd + opt + P + R buttons) 3 consecutive times
    I booted using the USB stick and used disk utility to repair permission as well as repair disk. Not much to repair there since it's a freshly installed system
    I did single user mode and did the /sbin/fsck -fy command twice until it says the HD is ok.
    Took off the power cable to reset SMC (or PMU whatever that thing is called now)
    I'm baffled. Since it's been running since 2008, could it be the PRAM battery? I know in my old powermac the logic board has that... but I'm not sure about the new intel Macs.
    I live in a country where there's no Apple Store so I'd really want to make sure I've tried everything before giving the machine to an authorized service center where it will sit 3 weeks if I can kinda pinpoint what's wrong and bring it to a local shop to change parts real quick if needed.
    It's out of warranty (obviously) without any Applecare.
    Anyone might have a clue to what's wrong with this machine?
    Thanks very much.

    Reinstalling OS X Without Erasing the Drive
    Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
    Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
    When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu.
    Reinstall OS X: Select Reinstall OS X and click on the Continue button.
    Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.
    Also see:
    Reinstall OS X Without Erasing the Drive
    Choose the version you have installed now:
    OS X Mavericks- Reinstall OS X
         Note: You will need an active Internet connection. I suggest using Ethernet
                     if possible because it is three times faster than wireless.

  • Can't boot into OSX from different Hard Drive

    Hi,
    I am having a problem booting into OSX.
    I put my own HDD into my Macbook when I first got it and everything was fine, no problems. But recently I took it out to keep my data safe and put back in the old HDD and reinstall OSX Snow Leopard onto the old HDD. After this completed I put back the one I had purchased myself but upon starting the laptop a bar appeared at the bottom of the Apple startup logo and after disappearing the system did not get any further.
    I put my my Snow Leopard CD after this to repair and check the disk and then came the errors that It was corrupt and could not be repaired and that I should try to back up as much data as possible.
    My question is, is there anyway to boot from this HDD again without reformatting it? and if I do have to reformat it, can I place it into an enclosure to get the data off?
    The HDD was working perfectly with no reported errors until I put in the old HDD and made a new installation on it.
    Thanks for any help,
    Francis

    After looking for answers and phoning Apple I have ended up having to reformat. For those who also have this problem:
    I have heard that running Disk Repair multiple times works, try booting into safe mode and try fsck in single user mode. My solution was just to connect the hard drive via USB so I could at least get all my data off of it.
    Cheers,
    Frank

Maybe you are looking for