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?

Similar Messages

Can I boot into Windows if it is partitioned on a second hard drive?

I want to put my 2009 MBP hard drive into a 2012 MBP by replacing the optical drive with the 2009 hard drive in a caddy. The 2009 has Windows partitioned on it already through bootcamp.
Will I be able to boot into windows through the second drive or will I have to bootcamp the new 2012 drive with Windows?

OK Cool. I think I will try that. Thanks for the tip. I appreciate it.

Can't get rid of Windows on my Mac even with disk utility

I noticed this disk0r3 or something like that, and I know this is Windows.
I have a bit of a bug issuea nd the windows wasn't done very well. I wanted to erease it with disk utility, but it said it couldn't. What should I do?
I've tried the zero, 15, and 35 or whatever they offered.

Did you use Apple's Boot Camp utility to create a hard drive partition for Windows?
If so, do you want to erase the partition created for Windows or eliminate the 2nd partition and go back to a single hard drive partition?
If the latter, you have no choice but to reformat the hard drive first which erases the hard drive and then re-install OS X and all software.

Can't boot into Windows after installing with Boot Camp

So I installed Windows 7 on a separate 70GB partition using Boot Camp. Everything seems fine, but once installation finished and the computer restarted for the final time, the computer shows the blinking "_" on the black screen and then promptly reboots and this cycle continues without end.

please re-post in the more appropriate Boot Camp forum

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.

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

I deleted my Boot Camp partition with Disk Utility and now I cannot reclaim the freespace?

I deleted my Boot Camp partition with Disk Utility and now I cannot reclaim the freespace?
And when I try to add a partition to the free space, and try to apply I do this:
I press apply and it does its thing for like a second, I switch tabs and I get this:
No matter how many times I reboot it doesn't work. Please help

diskutil list:
diskutil mergePartitions:

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>

Can only boot into Windows 7. Can't even boot from Snow Leopard DVD.

I have no idea what prompted this. I don't recall installing any OS updates recently, other than some Windows Live apps in Windows 7.
I have an early 2009 Mac Mini with Snow Leopard, and have Windows 7 64-bit installed in a Boot Camp partition. When I installed Windows 7, I couldn't get the Boot Camp utility to install within Windows (I guess because it's 64-bit) so to switch back and forth between OSes, I just shut down the Mac and restart it with the Option key pressed, and select Mac OS X when I want to return to Mac. This has worked for about a month and a half now (ever since I got Windows 7). Suddenly I have problems.
I first had problems booting into Windows or Mac. I got to the grey screen with the Apple logo, with that spinning "progress" thing going for a while, then it would freeze up and get stuck on the grey screen with the Apple logo. I zapped the PRAM. No help. Then, after disconnecting all external drives (I have several) and extra USB devices, I was able to boot from the DVD install disk and reinstall Snow Leopard on my internal drive. Joy, or so I thought. Then I booted into Windows 7, and after some weirdness getting it to start, it did successfully start and ran just peachy.
Then I turned off the Mac and held down the option key (as usual) to return to Mac OS. But now all that happens is that I get a grey screen for a few seconds, then the Mac boots back into Windows 7, which seems to work fine. (I'm in Windows 7 right now.) I turned on one my external drives (Snow Leopard installed, connected via Firewire 800) in hopes that the Mac would boot into that, but same thing. Ignored and back to Windows 7.
Then I thought I'd boot from the install DVD again by putting it in the drive and holding down the C key as I restart, but the same thing--a grey screen for a few seconds, and then booting right into Windows 7. I can't seem to escape Windows 7! It's a bit disturbing when it won't even recognize the install DVD.
I tried to call Apple Care since I'm within my 90 day support window, but of course they are closed. I'm figuring that I'm going to have to take this into an Apple Store, but thought I'd see if anyone has any ideas. Any advice will be appreciated. Thanks.

According to Apple, Win 7 64bit is supported with Bootcamp 3.0. If bootcamp 3.0 is available; I could not find it anywhere on Apple's website. It appears the most recent version is 2.2. The only place I could find 3.0 is not on Apples website and it's a questionable source so I won't post it here.
It may just be a matter of time before Apple makes it available. I'm not suggesting you wait, however if the install disk can't be used, I'm not too sure where u could go from there. Calling Applecare might work.
If you do a simple google search using the terms 'download bootcamp drivers windows 7' u will see what I was referring too.
Here's what I found from Apple (It doesn't specifically mention 64bit however just win7): http://support.apple.com/kb/HT3920
This is not from Apple, but specifically addresses whether they support win7 64bit: http://www.macnn.com/articles/09/08/31/boot.camp.win.7.64.support/
Here is more info about bootcamp 3.0 and win7: http://www.apple.com/support/bootcamp/

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

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!

Can't boot into Windows??

Hi!! This is my theory about not being able to boot into windows. If you have made a system repair disc like you should have made on day one; and your PC will not boot with the system repair CD, you probably have some serious hardware problems.
I'm going to steal this reply from cee64 again. A system repair CD can be made from any PC that is running W7 ect.
Hi I'm going to steal this reply from cee64. I'm sure he won't mind!
"It is quite possibly the hard drive is failing or has failed. The reason you can't get into the bios or boot from a CD/DVD is because the bios it hanging trying to recognize the hard drive. Try removing the hard drive and see if it will allow you into the bios or boot to a CD/DVD. If it does, go the hard drive manufacturer's support site, downlod their hard drive diagnostic ISO image, then use the burn from image option to create the self booting cd, then boot to it and run the most exhaustive diagnosis on it if it will boot. If you can't get it to boot to the diagnostic disk while the hard drive is installed you'll more than likely need to replace the hard drive.
If it won't get you into the bios or boot to a CD/DVD with the hard drive out of the system you need to try reseating the ram. If that doesn't help you probably have a bad motherboard. In this case it would more than likely be cheaper to just replace the laptop than fix it."
http://www.dummies.com/how-to/content/how-to-use-a-system-repair-disc-to-restore-windows.html
If Seatools found your HD good, then you have a good chance of using the recovery disks or the recovery partion to restore you back to factory setting. If that fails, you may be down to a bad motherboard. I know of no program to test the MB. You can use memtest 86 to test your Ram. I think it tests some parts of your MB, but can't say that for sure.
I Love my Satellite L775D-S7222 Laptop. Some days you're the windshield, Some days you're the bug. The Computer world is crazy. If you have answers to computer problems, pass them forward.

Hi! I stole this reply from Jerry Edited One link, because it failed to open
Let's start here. The spec above says your machine came with 32-bit Windows Vista. Have you changed it?
We need to reach the recovery environment. Can you do it this way?
http://windows.microsoft.com/en-US/windows-vista/What-happened-to-the-Recovery-Console
If not, burn a system repair disc from this download (assuming 32-bit Windows).
Download Windows Vista Recovery Environment ISO X86 version (32 bit)
-Jerry
I Love my Satellite L775D-S7222 Laptop. Some days you're the windshield, Some days you're the bug. The Computer world is crazy. If you have answers to computer problems, pass them forward.

Can't boot to windows, stuck at black screen (with cursor)

Hi! I'll get straight to my problem: I can't boot to Windows (Windows 10 Technical Preview) anymore after installing VirtualBox (or rather, an Android emulator that installed VirtualBox) on my system. I get stuck, after the loading animation with the blue HP logo, on a black screen (I can move my cursor around) but the login screen never shows up.
The problem.
I'm currently dual-booting linux and windows for several purposes. My laptop came with a Windows 8.1 OS by default. Some time after the Windows 10 Tech Preview came out to public, I upgraded my system to Windows 10 (so my 8.1 is gone now). Everything's going well until I installed this Android emulator (which installed VirtualBox) on Windows 10. Everything seemed fine at first but after rebooting, Windows isn't working anymore. I can still boot to linux, but Windows just won't boot properly.
What I've tried.
I've tried A LOT of things. The problem actually happened twice already (at first I was able to fix it with System Restore but not this time around). I have a Windows 8 USB Recovery Drive at hand, just so I can access a Windows command line. It's not from my system, though. It came with a new windows 8 laptop of a friend so I just borrowed it.
1: System Restore. This worked the first time. But now the restore won't finish and throws an error, telling me that it can't restore my system.
2: Refresh PC. "There was a problem refreshing your PC. No changes were made." or something like that.
3: chkdsk on C:\. It says it changed some files, but it doesn't really fix the problem.
4: sfc /scannow. Again, something happened, but it didn't get fixed.
5: bootrec.exe to fix BCD and MBR. Doesn't work. (as far as I know my sytem is using GPT)
6: Hard reset (remove all power sources then hold power button). Still not working.
7: System Restore again. All the restore points aren't working. It reaches a "Finished" state, but then an error comes up after. It says can't extract a specific file, and the restore point is damaged or might have been deleted during restore.
8: checking and fixing bad sectors (nope, no bad sectors on my hard drive)
9: built-in component tests. It passed all of them, except the battery test (my battery really isn't surviving for any duration longer than 30 minutes, but that shouldn't affect my OS). I didn't try the really long tests since I thought it wouldn't matter as my problem is most probably completely software (since linux is still working).
10: cry. oh please. Windows isn't working. What should I do? (
Things I haven't tried.
1: RAM and CMOS battery reset.
2: Reset PC.
3: Format hard drive.
4: Test hard drive on another laptop's system.
If possible I'd like to avoid getting my hard drive wiped, since I have a lot of stuff to backup (more than 300 GB of files + dozens of linux apps and ppas), and I only have a 32GB USB drive to backup all the files I need).
Thanks for reading.

Sorry for the delay. Wasn't expecting the "road work" signs when attempting to check back with you in the AM here.
As others have already mentioned, the prompt for file systems occurs during text mode setup. Quick or Full? FAT or NTFS? How do you know what to do?
We'll start with file systems, short and sweet. Most any OS can read and write FAT volumes without fail which makes FAT ultra-portable, and the only choice if you want to let Mac OS write documents on your Windows volume. It's also more efficient on drives of 16 GB or less. However, FAT has no folder-level access control, so any file in the system can be manipulated by any user or by any system process. By contrast, NTFS is far more restrictive. It can only be manipulated under Windows, though other systems may be able to read it. Not only do you get the access control that FAT lacks, but you also get superior efficiency on large volumes, plus the power to compress or encrypt folders and files at will (in "business" flavors of Windows only--and yes, Vista Ultimate counts as "business" even though it will be supported much like a "consumer" version).
On format speeds: A quick format is very handy if you have a large partition or a single drive completely dedicated to Windows. Because it completes in 30 seconds or less, it will go a long way toward completing your Windows install. However, in some cases, volumes formatted with a quick format may have reliability issues. They must have fixed this in Vista, because Vista can only format at the "quick" speed.
A full format tests all blocks of a given volume (as opposed to testing an entire disk unless the volume itself is the entire disk) as the file system structure is laid down. Bad blocks are marked as "used" when they are found. This type of format takes much longer as a result of all the testing, but the result is a more stable volume from the start.
Get past the formatting stage, and you'll be right as rain.
Nate

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

Similar Messages

Maybe you are looking for