Can't boot os x after bootcamp

Hello.
The problem:
Yesterday I installed windows 7 on my early 2009 (mavericks) mac pro via boot camp.
I have three HD in my mac. One for os x, one for documents, and one for the windows. Before I start bootcamp I formatted my HD into NTFS for Win.
I run the bootcamp and everything went well, until the standard windows partition screen show up. I select the "bootcamp" HD, but i only can continue the installing if I format the hard drive.
The Win7 run well, but now I can't boot into os x.
When I hold down "options", only the windows appear as a selectable option.
I installed bootcamp on windows manually (4.0.4033 according to Boot Camp: System requirements for Microsoft Windows operating systems)
when I try to restart to osx the bootcamp say "there is no bootable volume".
i only see the "bootcamp" HD, and I can't treat the other two.
What I tried
Resetting NVRAM and PRAM
Holding down various key combinations (Options, Command + R, Options + R)
When I take out the "Machintos hd" a flashing folder pic appears.
I don't have the installation disk for os x, and I don't want to uninstall the os x..
There is any solution for my problem?

1. How many physical drives do you have in the MacPro?
2. Was Windows and OS X installed on the same physical drive?
3. In the case of the Tower MacPro with more than one drive, all drives that are not intended for Windows use must be physically removed from drive bays, before Windows is installed.
4. If you cannot see OS X, use an external disk (Firewire or USB with 16GB or more) and install a fresh copy of OS X and both you MacPro and the the disk with Windows can be corrected, if possible.
5. OSX re-installation leaves you files intact, unless you tell the OS X Installer to erase the designated drive.
6. Step 4 can also uses a USB flash drive, if necessary.
The error message is because a drive which was present when Windows was installed (it is stored in the BCD for W7/W8 or boot manager/loader)is no longer available. It is complaining about it.
If you put this drive back, can you boot into Windows successfully? If yes, can you post a screen shot of Control Panel -> System -> Administrative Tools -> Computer Management -> Disk Management.

Similar Messages

IMac won't boot OsX Partition after Bootcamp install/uninstall.

Hello,
I have bought 2 late 2012 21.5 iMacs last year and have used both the same way. Here is what happened with one of them recently.
Fisrt af all I've installed bootcamp 1 year ago in both iMacs without issues and was ok so far, and was using exclusively Windows 7 partition. The trouble iMac started with some startup issues during boot/reboot (screen was frozen with green/grey horizontal lines), but worked fine after following manual start up.
Lately I've been trying to boot from OsX partition and it freezes in the apple logo every time.
I have already done the SMC / PRAM procedures, without success.
I have tried to download and do a fresh OsX install (Mountain Lion, Mavericks and Yosemite). Can't boot from Mavericks / Yosemite flash drive install (both freeze at apple logo - horizontal lines), and only had partial success with one Mountain Lion 10.8.5 flash drive install that booted all right and the first part of the installation process was ok, but after the initial reboot, it happened to freeze the same way before.
The iMac failed to boot in safe mode (stops booting at 25% and then freezes on apple logo), and show no issues with AHT tests.
I can boot in single user mode, but it reboots after a few seconds. I noticed some errors messages during this boot.
It fails to boot in verbose mode, showing a few lines of errors (images attached), and then freezes in a green horizontal line screen.
I can still boot from Bootcamp flash drive and Ubuntu Flash drive, and install both OS. The only issue is with OsX itself. I have used Gparted in Ubuntu to Format the hole partition to HFS+, and can't find any errors in hard drive tests.
I thought about buying a thunderbolt cable and try to do a Clone of my other iMac, but don't know if it will work.
Any other tests/suggestions about this issue?
Regards,

Fixed the problem with this setup
Of course this means i just lost 4GB.
Let me tell the full story.
In the beginning, long ago, once upon a time. My iMac had 2x2GB ram sticks which were in the two DIMM1 Banks. I then told myself "I WANT MORE RAM BECAUSE LOLZ". So i bought 2x4GB ram sticks. The two empty slots were Bank 0/DIMM0 and Bank 1/DIMM 0. and I added them in there. having done that, I booted OS X up, worked great, had 12GB, everything was shiny and beautiful. Soon after I wanted to try it out on windows. I restarted my computer and BAM the blinking cursor just sits there, being stubborn and all. I then told myself "holy balls, this new ram i got is bonkers" (them words, I blame the language filter). Then after giving it a little thought, i just asked myself if it was because I had ram from two different manufacturers. I removed my old ram, which has nice Samsung stickers on them, and booted it up on windows. Still had the same problem, I then decided that maybe this is all really mentally challenged so to win I had to think like a retard. I took my new ram and inserted it in the same slots where my old ram sticks were (DIMM1 Banks), booted windows up and IT WORKED.
I still hold all of my WHYs on this subject but I will keep messing around to see if I find a better solution than just leaving both DIMM0 banks empty

Can't Boot OS X after Win7 Install

I was running Leopard and partitioned my hard drive using boot camp. I read that you have to be running Snow Leopard to install Windows 7 with bootcamp, so that's probably the problem.
I installed windows 7 just fine but can't boot to OS X. I can't figure out how to boot from a CD either because the option key doesn't bring up anything after a restart. I wouldn't mind just installing Snow Leopard (which I have now) and starting all over again. I've tried running EasyBCD but it can't boot to OS X. Any ideas on what I can do?

You don't need to be running 10.6, but you need Boot Camp 3.0 drivers off that DVD.
Wireless keyboard? a wired keyboard is preferable and needed sometimes.
X on startup will try to boot Mac OS
Try holding C and booting from Windows 7 DVD again; or from SL DVD - and from there you can access Utility menu and Disk Utility
Step one: backup, read the pdf from Boot Camp Aasistant
I prefer cloned backups that can then boot OS X off an external drive

Can't connect to wifi after bootcamp

ICan't connect to wifi after bootcamp.
I install windows 7 on my MacBook Pro retina 15.
Windows is staring up but I can't connect to network.
It says I need a driver (network driver) how do I get it?
But when I run the Mac with Macintosh HD all work normal.

Did you follow the Bootcamp instructions and download and install the Windows Support software?

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!

How can i boot my iphone after erasing using findmyiphone

I accidentally erased my iphone using find my iphone and removed it also. now it says sim pin locked. how can i boot it again normally?

Hello Mr.MacMac,
It sounds like you are trying to restore your device but you are seeing a message about the Sim Pin being locked. I recommend the information in the following article:
iOS: Understanding the SIM PIN
http://support.apple.com/kb/ht1316
You can enable, disable, or change your SIM PIN in the following locations:
iPhone: Settings > Phone > SIM PIN
iPad (Wi-Fi + Cellular models): Settings > Cellular Data > SIM PIN
Note: Some carriers provide SIM cards with a default SIM PIN already enabled. Contact your carrier to find out what your default SIM PIN code is.
Restoring
When restoring the device, you will need to unlock the SIM card to complete the restore process. The device and iTunes display the following prompts to notify you:
To complete the restore process:
Disconnect the device from your computer.
Tap Unlock on the device.
Enter the SIM PIN to unlock the SIM card.
Reconnect the device to your computer.
Thank you for using Apple Support Communities.
All the very best,
Sterling

Can no longer boot to MacOSX after bootcamp install

Hello all, I have an issue to where I can no longer boot into the Mac OSX partition after what appears to be a failed Windows bootcamp install. As I was running the bootcamp assistant process, a reboot occurred and I was greeted with the "No bootable device -- insert boot disk and press any key". I have no idea how to get past this and boot back to OSX.
Things I have tried:
Holding down the "option" key does nothing, even using a USB keyboard
Resetting PRAM (CMD + OPT + P + R) does nothing, even with USB keyboard
I have put in a MAC OSX 10.7 Disk and cannot boot to disk using CMD + C on startup
I also pulled the hard drive out and connected it to another PC and wiped the drive completely. I put it back in the macbook and I am still presented with this error. It seems, even though I get the Mac startup tone, that it is stuck in which ever OS it tried to run previously, that being Windows. Not sure why I am still receiving this error even after wiping the drive completely clean.
As far as hardware goes, I am pretty sure its a late 2010 Alumn. Macbook Pro. I cant get the current model number since I cant boot the OS. Any help is appreciated.

Please reset SMC as well.
You can get the serial number from the back cover and use https://selfsolve.apple.com/agreementWarrantyDynamic.do to find the model.

Can't boot into Windows after splitting Mac partition with Disk Utility

Hi everyone,
I installed Windows 8 with BOOTCAMP, creating a large 871 GB partition with a smaller 127 GB partition for Windows. After installing Windows, I then went back to Disk Utility to shrink the Mac partition and add two new partitions, one for storage and another blank, hoping to use it to install Linux into one day.
I did that, and now Windows doesn't boot. A Windows blue screen tells me I need to use the Windows DVD to repair it.
I tried to use Disk Utility to delete the two new partitions I made and grow the Mac partition back to the max size of 871 GB. But it doesn't let me do this. The Disk Utility log doesn't report an error and thinks it worked but the partition stays the same size. However if I make the partition a little smaller, like 870 GB then it works. I'm wondering if the Recovery partition is hiding there and preventing me from fully expanding the Mac partition.
What can I do?
Here's what I get if I type in sudo gpt -r -vv show disk0:
Code:
gpt show: disk0: mediasize=1000204886016; sectorsize=512; blocks=1953525168 gpt show: disk0: Suspicious MBR at sector 0 gpt show: disk0: Pri GPT at sector 1 gpt show: disk0: Sec GPT at sector 1953525167 start        size index contents 0           1         MBR 1           1         Pri GPT header 2          32         Pri GPT table 34           6 40      409600      1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B 409640 1701278816      2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC 1701688456     1269536      3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC 1702957992     1846360 1704804352   248002560      4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 1952806912      718223 1953525135          32         Sec GPT table 1953525167           1         Sec GPT header
Here's what I get if I type sudo fdisk /dev/rdisk0:
Code:
Disk: /dev/rdisk0     geometry: 121601/255/63 [1953525168 sectors] Signature: 0xAA55 Starting       Ending #: id cyl hd sec - cyl hd sec [     start -       size] ------------------------------------------------------------------------ 1: EE 1023 254 63 - 1023 254 63 [         1 -     409639] <Unknown ID> 2: AF 1023 254 63 - 1023 254 63 [    409640 - 1701278816] HFS+ 3: AB 1023 254 63 - 1023 254 63 [1701688456 -    1269536] Darwin Boot *4: 07 1023 254 63 - 1023 254 63 [1704804352 - 248002560] HPFS/QNX/AUX
Here's what I get with gdisk:
Code:
Disk /dev/rdisk0: 1953525168 sectors, 931.5 GiB Logical sector size: 512 bytes Disk identifier (GUID): 6075110F-7CEF-4604-85EE-6231B850E2AE Partition table holds up to 128 entries First usable sector is 34, last usable sector is 1953525134 Partitions will be aligned on 8-sector boundaries Total free space is 2564589 sectors (1.2 GiB) Number Start (sector)    End (sector) Size       Code Name 1              40          409639   200.0 MiB   EF00 EFI System Partition 2          409640      1701688455   811.2 GiB   AF00 1 TB APPLE HDD HTS54101 3      1701688456      1702957991   619.9 MiB   AB00 Recovery HD 4      1704804352      1952806911   118.3 GiB   0700 BOOTCAMP

Okay, the code I typed didn't display properly in the forum. Let me try again.
Here's what I get when I type
sudo gpt -r -vv show disk0:
gpt show: disk0: mediasize=1000204886016; sectorsize=512; blocks=1953525168
gpt show: disk0: Suspicious MBR at sector 0
gpt show: disk0: Pri GPT at sector 1
gpt show: disk0: Sec GPT at sector 1953525167
       start        size index contents
           0           1         MBR
           1           1         Pri GPT header
           2          32         Pri GPT table
          34           6
          40      409600      1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
      409640 1701278816      2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
1701688456     1269536      3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
1702957992     1846360
1704804352   248002560      4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
1952806912      718223
1953525135          32         Sec GPT table
1953525167           1         Sec GPT header
And when I type fdisk /dev/rdisk0 I get:
Disk: /dev/rdisk0          geometry: 121601/255/63 [1953525168 sectors]
Signature: 0xAA55
         Starting       Ending
#: id cyl hd sec - cyl hd sec [     start -       size]
1: EE 1023 254 63 - 1023 254 63 [         1 -     409639] <Unknown ID>
2: AF 1023 254 63 - 1023 254 63 [    409640 - 1701278816] HFS+
3: AB 1023 254 63 - 1023 254 63 [1701688456 -    1269536] Darwin Boot
*4: 07 1023 254 63 - 1023 254 63 [1704804352 - 248002560] HPFS/QNX/AUX
Kappy,
I can boot into OS X just fine so if possible, I'd like to avoid reformatting everything. If you know of a way I can add more than 2 partitions with OS X and Boot Camp, please let me know. As far as I know, rEFInd can recognize more than two partitions, but I don't think it can edit partitions on a GPT / hybrid MBR system. Or am I wrong?

Can not boot into OSX after boot camp installation and resizing of Macintosh HD

So from the beginning what I was trying to do was set up my iMac (27-inch, Late 2013) with boot camp so that I could play some old windows based games that can not be played in Parallels.
I went through the Boot camp process and everything set up just fine.
I had both OS X Yosemite 10.10.2 and Windows 8 Professional running but as I was installing games on to boot camp I discovered I did not allocate enough space and needed to extend the Boot Camp partition.
I used boot camp utility to set OS X as the default start up disk and had it restart
I launched into OS X and used Disk Utility to shrink Macintosh HD another 120GB
Restarted again holding option and launched into Windows
Used the disk management in windows to try and extend the boot camp partition into the unallocated space.
It was not an option to extend it so I tried to create a new simple volume from the unallocated space then delete it and try to extend it again.
It still was not an option.
From there I went to restart again while holding option and the only options I had were 10.10 Recovery and Windows
I tried using disk utility in recovery and Macintosh hd now only showed disk0s2
I tried to verify and it could not verify
I tried to repair and it could not repair.
I put the iMac in target disk mode and using a thunderbolt cable I tried using disk utility from my MacBook Pro (13-inch Mid 2012)
Verifying volume “disk2s2”Verifying file system.** /dev/rdisk2s2
Invalid BS_jmpBoot in boot block: 000000
File system check exit code is 8.Error: This disk needs to be repaired. Click Repair Disk.
Verify and Repair volume “disk2s2”Repairing file system.** /dev/rdisk2s2
Invalid BS_jmpBoot in boot block: 000000
File system check exit code is 8.Updating boot support partitions for the volume as required.Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
This is the same error I got on my iMac
I used terminal diskutil list and got:
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:       Microsoft Basic Data                         799.3 GB   disk2s2
   3:                  Apple_HFS Recovery HD             650.0 MB   disk2s3
   4:       Microsoft Basic Data BOOTCAMP                70.3 GB    disk2s4
I can see that Macintosh HD was disk2s2 but it now shows its Microsoft Basic Data.
I did not format this partition and it was working fine till I restarted the computer after resizing Macintosh HD.
I am not sure what I can do to fix this.
I've found multiple articles about similar issues, but the issue thet they have was that they could not boot to Windows instead of my issue not booting to OS X

****************    Update    *****************
From the Windows Partition using Disk Management I can see that the drive is still labeled Macintosh HD and that all of my data is there.
I have a complete backup so i'm not worried so much about the data.
What I'm most interested in is trying to solve this issue because I'd like to continue using boot camp and I actually work with mac computers and would like to be able to help others if this issue arrises again.

Windows XP on MacBook Pro - Can't connect to wireless after bootcamp, why?

1)I just bought MacBook Pro, just did a boot camp with windows xp. With Windows xp installed, it can't detect wireless network. What went wrong?
2)When setting the boot camp, do i need to have the boot camp driver? Why?
3)Can Windows xp on Macbook pro use the same built-in modem, or do i need to get a modem/ adaptor for windows on mac, so the wireless (on window xp on mac) would be able to work.

hannah llc wrote:
1) I just bought MacBook Pro, just did a boot camp with windows xp. With Windows xp installed, it can't detect wireless network. What went wrong?
2) When setting the boot camp, do i need to have the boot camp driver? Why?
Did you install Apple's bootcamp drivers after you installed Windows? You should be able to accomplish that by booting into Windows and then inserting the installation disc that came with your MacBook Pro. Without Apple's drivers, Windows may not know how to use the wireless circuitry on your Mac.
3) Can Windows xp on Macbook pro use the same built-in modem, or do i need to get a modem/ adaptor for windows on mac, so the wireless (on window xp on mac) would be able to work.
With the proper drivers Windows should be able to use the wireless equipment that came with your Mac.

I can't boot to Windows after resizing my Mac partition.

So, I recently decided to resize my bootcamp Win7 partition. This is something I have done successfully before, by:
1) Booting into Macintosh
2) Using Disk Utility to decrease the size of the Mac partition (20GB the first time)
3) Booting into Windows
4) Using Mini-Tool Partition Wizard (third-party) to allocate the free space to the Bootcamp partition.
There were a couple issues caused by this the first time around, mainly the fact that Macintosh didn’t recognize the fact that the free space had been taken, and had trouble reading from the Windows partition. However, I could live with that. I have since rebooted to both Mac and Windows several times without problem.
Recently, I decided I needed a bit more space, and so started to follow the above steps, shrinking the Mac partition an additional 15GB. Only when I went to reboot to reallocate the space, the Windows partition didn’t show up as a bootable option. Confused, I booted back to Mac, and the Bootcamp partition was still there, but renamed “disk0s4”, and unmounted. Reparing the disk failed (“Invalid BS_jmpBoot in boot block: 15921e”). The disk wouldn’t mount (not even sure if it was supposed to be mounted earlier, but that’s what it looks like). It also appears grayed-out in the list of drives to the left. It looks like I can create a dmg from the windows drive, although I haven’t done that yet (I will soon).
Any solutions for this? Although I will erase the drive if absolutely necessary, it would be preferred if that wasn’t the first option to try. I had no problems like this the first time I resized the disk.
(My mac partition is running Mavericks, if that is of any relevance)

These steps correct the Partition ID, and the boot ability of the MBR partition that has Windows on it.You can type '?' for help in the following steps where you set the fdisk prompt.
To fix the MBR, in OSX Terminal
sudo fdisk -e /dev/disk0
setpid 4
07
flag 4
p
w
y
q
Please ignore the i386 message that you see in the following. Here is the set of commands in the utility. The utility starts at partition id 1. If you see any other messages, please post back.
sudo fdisk -e /dev/disk0
fdisk: could not open MBR file /usr/standalone/i386/boot0: No such file or directory
Enter 'help' for information
fdisk: 1> ?
help Command help list
manual Show entire man page for fdisk
reinit Re-initialize loaded MBR (to defaults)
auto Auto-partition the disk with a partition style
setpid Set the identifier of a given table entry
disk Edit current drive stats
edit Edit given table entry
erase Erase current MBR
flag Flag given table entry as bootable
update Update machine code in loaded MBR
select Select extended partition table entry MBR
print Print loaded MBR partition table
write Write loaded MBR to disk
exit Exit edit of current MBR, without saving changes
quit Quit edit of current MBR, saving current changes
abort Abort program without saving current changes
fdisk: 1>

[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)

MSI GE620 can't boot to windows after installing CoreCenter 2.0.6.8

I have made a very huge mistake by installing an overclocking software without knowing anything about overclocking :(
Here is what I have done
- I installed CoreCenter version 2.0.6.8, after the installation finished it ask me to reboot the system, so I reboot.
- First my system won't shutdown it tell be that S-Bar (an toolbar that come with my GE 620 laptop) prevent me from shutdown, so I hit force shutdown. Then the system started to shutdown but it stuck at windows logo (Shutting down screen) so I hold down the power button to force turn off
- Windows gives me an option to boot into safe mode (because I hold down the power button and it is unexpected shutdown), I hit start Windows normally
- It goes into a Windows logo screen like normal, but it won't boot. It's just stuck at the Windows logo screen. At this time I tell myself "OMG what I have done!???"
- I try most option in a boot option (not sure what it called, it's a menu brings up when you press F8). I tried boot into safe mode, safe mode with cmd (both stuck at loading disk.sys), repair system, enable low res (640x480), last known good config, Directory service restore mode and debugging mode. None of them are able to boot.
- I grab a Windows 7 Ultimate repair disc that I have created long time ago. And.... "Oh no! It even cannot boot into a repair disc!"
- I give a Hiren's BootCD 15.2 a try. I boot Mini XP from that disc and..... It can't even boot XP from the CD.
- Ok Ok, maybe it mess something with BIOS setting, I press DEL into a BIOS setting (I believed) and hit restore all setting to default. Unfortunately, my system still won't boot.
Any idea of how I can uninstall this CoreCenter or any clues that what it have done to my system?
The only thing I know for now is just re-installing Windows, but I need to backup some data in C:/ first. I think I can install windows without formatting and backup some data and re-install it with format.
My system information
MSI GE620 laptop (All of hardware is stock, I didn't change anything. Just install extra 4 GB of RAM)
CPU: Core i7 2630QM
GPU: nVidia GeForce GT 540M / 1 GB DDR3
RAM: 8 GB
OS: Windows 7 Ultimate x64
Update: I can't even boot from a Windows 7 installation disc!! *cry*

Having not yet installed Developer 6 on my own system, (still running most recent 200 version), I can't be exactly sure. However your problem sounds a lot like the problem I encountered in trying to get my Dev 2000 install to connect.
Here are some things to check:
Is your listener running?
Is your listener properly configured to look for your host machine?
Look in the Oracle Net 8 Assitant utility and see how many listeners have been established. This is where my problem existed. I had 2 listeners. One was trying to connect to my loop back address (127.0.0.1) and could not. The other was properly configured for my host address but would not run because of the failure of the other. Once I removed the listener the was using the loop back address things began to work.
Make sure you have the appropriate alias set up through SQL Net Easy Config and/or Net8 Config.
Thats all I can think of for now.
Hope something I said will help.

[SOLVED]Can't boot into OS after installation

Hello all,
I've ran into a few problems already all of which I could solve with somme googling etc.
Until now the installation of arch Linux went pretty smoothly until I rebooted to get into the OS via grub (version 2), once I select Arch Linux in the menu the os starts booting but it stops at this: "a start job is running for dhcpcd on enp7s0 (x s/1m31s)" this always fails. After that 3 extra lines appear starting with a green OK all saying reached target ..........
This is where no more progress is made, the only keys that generate a response are Ctrl+alt+Del then the system reboots.
Here is a clear image of the status of the machine
https://i.imgur.com/queQkEOh.jpg
EDIT: If you guys need any extra information please ask, but I can't access the systems config files or anything due to this problem so suggestions on how to pull that data are welcome
-- mod edit: converted img tags to url - Trilby --
Last edited by Covati (2014-10-06 13:04:05)

Trilby wrote:
Welcome to the forums - please see the forum guidelines on how to post including image size restrictions.
As for the issue - can you Alt-F2 or Alt-F3 to get to another tty?
It worked, wow I feel dumb now.
Anyways thank you for helping me out, I will look into the guidelines.
Can mark this thread as solved!

Can't re-install system after bootcamp

now i cant even install the system 10.4.9 on my near new MBpro
after doing a bootcamp install and restore,
cant use any disk utilities except erase,
which i did,
before that idefrag, ipartition, wouldnt work coz the drive was stuffed up.
now its really stuffed.
thanks apple...
erased hard drive
10.4.9 install says ''this software cannot be installed on this computer''
the original discs
what the f***

Hi Mark,
sorry to hear of such bad luck.
Check with Disk Utility (Top Menu - Utilities) while booted from the OSX DVD if your HD is set to the GUID partition table.
If not change it to that for OSX installation.
Good Luck
Stefan

Can't boot os x after bootcamp

Similar Messages

Maybe you are looking for