[solved] "No boot signature in partition"

"No boot signature in partition" is the message i get when my computer boots.
I always had an ata disk it booted from, sda. the OS was on sdb. I got rid of the ata disk and wanted my pc to boot from the disc which contains the OS. So hdb became sda. I installed lilo to the mbr and lilo reported it to be succesful. The partition on which the os resides is flagged bootable.
This is in my lilo.conf:
boot=/dev/sda
default=arch
timeout=50
lba32
prompt
image=/boot/vmlinuz26
label=arch
root=/dev/sda1
initrd=/boot/kernel26.img
read-only
image=/boot/vmlinuz26
label=arch-fallback
root=/dev/sda1
initrd=/boot/kernel26-fallback.img
read-only
btw: I installed lilo with "lilo -M /dev/sdb" while the ata-disk was still plugged in. I then removed the disk.
I dont know what to do. Anyone knows a solution?
Last edited by build (2009-07-31 21:04:59)

hello djszapi!
At first I had problems with grub too. But I always had used lilo, so after the diskswitch I decided to go back to lilo bc grub wasnt doing what i wanted it to do.
Eitherway, it is solved now. Grub did the trick and shone light on my darkest hour. Grub dissolved the dark enigma of boot signature problems and made them part of the past.
Thanks
Last edited by build (2009-07-31 21:03:24)

Similar Messages

  • [SOLVED] Cloning boot and var partitions to a new drive for booting

    Ok first of all here's my setup:
    fakeraid (dmraid) / and home on an OCZ Revodrive
    boot with GRUB on a flash drive (since fakeraid doesn't support grub)
    var and downloads/media folder on a 500GB WD Caviar drive
    When I originally installed Arch I had the Caviar drive in my home server in a RAID5 array, so that's why I opted to install boot and grub on a flash drive simply for booting.  Now that I have the drive in my desktop I've cloned the flash drive's partitions and MBR using dd:
    #dd if=/dev/sde of=~/MBR.img bs=512 count=1
    #dd if=/dev/sde1 of=~/boot.img
    #dd if=/dev/sdc1 of=~/var.img
    I then backed up my downloads/media partition, then removed the partition table, then used dd to put the img files on the Caviar drive.
    #dd if=~/MBR.img of=/dev/sdc bs=512 count=1
    #dd of=~/boot.img of=/dev/sdc1
    #dd of=~/var.img of=/dev/sdc2
    I also created labels for the filesystems and put those in fstab.
    I'm able to mount both partitions, however I can't boot from the drive.  I get a 'grub hard disk error' (no error number) when I put it as my first drive in the BIOS. 
    I can still use the flash drive as the first hard drive in the BIOS and boot from it, then it mounts the dmraid root partition and boots successfully.  It is also able to mount the var and boot partitions in fstab. 
    Basically the only problem is that the MBR is somehow wrong.  I then tried booting back into an Arch live USB and installing GRUB from the prompt:
    grub
    grub>setup (hd4,0) (in this case the Caviar drive's boot partition was /dev/sde1
    So essentially what I'm asking is how GRUB handles the MBR.  Is it specific to the partition table of the drive in which it resides when it's originally installed?  For instance, since I had an 8GB flash drive with 2 partitions when I installed GRUB, is the backed up MBR no good for a 500GB drive with 3 partitions?
    I have everything backed up so I can start with a fresh /boot and /var if need be....I'm just not sure where to start. 
    Thanks in advance.
    Last edited by DarksideEE7 (2011-02-13 23:25:31)

    Sorry, I forgot to mention that I tried to install GRUB from the GRUB shell in a live Arch USB.  It failed on a few non-critical parts, and succeeded on the last part. I'm going to try again shortly, possibly I did something wrong.  GRUB is able to find the stage files using:
    #grub
    grub>find /grub/stage1
    grub> find /grub/stage1
    (hd0,0)
    (hd5,0)
    grub>
    (hd0,0) is the desired boot drive, while (hd5,0) is the current bootable flash drive with /boot and GRUB installed.
    Here is the output of fdisk -l:
    WARNING: GPT (GUID Partition Table) detected on '/dev/sde'! The util fdisk doesn't support GPT. Use GNU Parted.
    Disk /dev/sde: 2000.4 GB, 2000398934016 bytes
    256 heads, 63 sectors/track, 242251 cylinders, total 3907029168 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: 0x00000000
    Device Boot Start End Blocks Id System
    /dev/sde1 1 3907029167 1953514583+ ee GPT
    Disk /dev/sdb: 60.0 GB, 60022480896 bytes
    255 heads, 63 sectors/track, 7297 cylinders, total 117231408 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: 0xedb72db9
    Device Boot Start End Blocks Id System
    /dev/sdb1 * 2048 206847 102400 7 HPFS/NTFS
    /dev/sdb2 206848 117227519 58510336 7 HPFS/NTFS
    Disk /dev/sdd: 40.0 GB, 40018599936 bytes
    255 heads, 63 sectors/track, 4865 cylinders, total 78161328 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: 0x00000000
    Disk /dev/sdd doesn't contain a valid partition table
    Disk /dev/sdc: 40.0 GB, 40018599936 bytes
    32 heads, 32 sectors/track, 76329 cylinders, total 78161328 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: 0xb8372fcd
    Device Boot Start End Blocks Id System
    /dev/sdc1 32 21484543 10742256 83 Linux
    /dev/sdc2 21484544 156317695 67416576 83 Linux
    Disk /dev/sda: 500.1 GB, 500107862016 bytes
    255 heads, 63 sectors/track, 60801 cylinders, total 976773168 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: 0x8497e059
    Device Boot Start End Blocks Id System
    /dev/sda1 * 2048 206847 102400 83 Linux
    /dev/sda2 206848 42149887 20971520 83 Linux
    /dev/sda3 42149888 976773167 467311640 83 Linux
    Disk /dev/dm-0: 80.0 GB, 80035053568 bytes
    32 heads, 32 sectors/track, 152654 cylinders, total 156318464 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 65536 bytes / 131072 bytes
    Disk identifier: 0xb8372fcd
    Device Boot Start End Blocks Id System
    /dev/dm-0p1 32 21484543 10742256 83 Linux
    Partition 1 does not start on physical sector boundary.
    /dev/dm-0p2 21484544 156317695 67416576 83 Linux
    Disk /dev/dm-1: 11.0 GB, 11000070144 bytes
    255 heads, 63 sectors/track, 1337 cylinders, total 21484512 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 65536 bytes / 131072 bytes
    Alignment offset: 49152 bytes
    Disk identifier: 0x00000000
    Disk /dev/dm-1 doesn't contain a valid partition table
    Disk /dev/dm-2: 69.0 GB, 69034573824 bytes
    255 heads, 63 sectors/track, 8392 cylinders, total 134833152 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 65536 bytes / 131072 bytes
    Disk identifier: 0x00000000
    Disk /dev/dm-2 doesn't contain a valid partition table
    Disk /dev/sdf: 8086 MB, 8086618112 bytes
    249 heads, 62 sectors/track, 1023 cylinders, total 15794176 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: 0x8497e059
    Device Boot Start End Blocks Id System
    /dev/sdf1 * 62 200693 100316 83 Linux
    /dev/sdf2 200694 15794175 7796741 83 Linux
    I'm using dmraid, so just to be clear I've configured the raid using:
    #modprobe dm_mod
    #dmraid -ay
    Then I saw the array stored in /dev/mapper/silXXXXX.  I then created partitions for /boot, /, and home.  At that time I was hoping to get GRUB working with the AUR package grub2-dmraid.  I wasn't able to get it working for some time, so I just went ahead and installed boot and GRUB to a separate USB flash drive.
    Here is the output of df -h:
    Filesystem Size Used Avail Use% Mounted on
    udev 10M 268K 9.8M 3% /dev
    /dev/mapper/sil_bgbgdjaddicbp1
    11G 5.3G 4.3G 56% /
    shm 6.0G 584K 6.0G 1% /dev/shm
    /dev/mapper/sil_bgbgdjaddicbp2
    64G 38G 23G 63% /home
    /dev/sda1 95M 16M 75M 18% /boot
    /dev/sda2 19G 142M 19G 1% /var
    /dev/sda3 439G 148G 269G 36% /home/l33/Torrents
    none 1000M 132K 1000M 1% /tmp
    shm 6.0G 584K 6.0G 1% /dev/shm
    /dev/sde1 1.8T 1.1T 665G 62% /mnt/Green
    and cat /etc/mtab
    proc /proc proc rw,nosuid,nodev,noexec,relatime
    sys /sys sysfs rw,nosuid,nodev,noexec,relatime
    udev /dev devtmpfs rw,nosuid,relatime,size=10240k,nr_inodes=1022975,mode=755
    /dev/mapper/sil_bgbgdjaddicbp1 / ext4 rw,noatime,barrier=1,stripe=32,data=ordered
    devpts /dev/pts devpts rw 0 0
    shm /dev/shm tmpfs rw,nosuid,nodev 0 0
    /dev/mapper/sil_bgbgdjaddicbp2 /home ext4 rw,noatime 0 0
    /dev/sda1 /boot ext2 rw 0 0
    /dev/sda2 /var reiserfs rw,noatime 0 0
    /dev/sda3 /home/l33/Torrents ext4 rw,noatime 0 0
    none /tmp tmpfs rw,nosuid,nodev,noatime,size=1000M,mode=1777 0 0
    shm /dev/shm tmpfs rw,nosuid,nodev,size=6G 0 0
    rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0
    nfsd /proc/fs/nfsd nfsd rw,noexec,nosuid,nodev 0 0
    /dev/sde1 /mnt/Green ext4 rw 0 0
    Also I don't have a /proc/mdstat.  That's only for mdadm RAID setups, right?  It's been quite some time since I've used mdadm so I can't remember.
    EDIT:
    So I booted into a live Arch USB and entered the grub shell.  I ran:
    #grub
    grub> root (hd3,0)
    Filesystem type is ext2fs, partition type 0x83
    grub> setup (hd3)
    Checking if "/boot/grub/stage1" exists.....no
    Checking if "/grub/stage1 exists.......yes
    Checking if "/grub/stage2 exists.......yes
    Checking if "/grub/e2fs_stage1_5 exists....yes
    Running "embed /grub/e2fs_stage1_5 (hd3)".....25 sectors are embedded.
    succeeded
    Running "install /grub/stage1 (hd3) (hd3))1+25 p (hd3,0)/grub/stage2 /grub/menu.lst".......succeeded
    Done.
    Last time I recall more errors than this, then it reporting that one was a non-critical error, so I think the problem may be solved.  More to come.
    Last edited by DarksideEE7 (2011-02-13 23:18:44)

  • [Solved]Grub booting the wrong partition

    Hello everyone and thank you for reading!
    This is my first post on this forum (and my first step into arch) so appologies for any newbie symtoms (and bad language).
    My problem:
    When I start my laptop (press the power button) my system go's into bios and then boots my HDD (that statement is a bit off I know). After that the system stops and grub rescue starts, saying something about a UUID not found (the UUID is nowhere to be found in my system but it could be one from my previous Ubuntu setup).
    My system:
    An Acer Laptop with a Samsung SSD for OS(sda) and Seagate HDD for storage(sdb)
    a 3d gen i5
    glorious Nvidia optimus
    some more stuff I think is not importend
    My attempted solutions:
    >Switch the boot-order and put my SSD on top.
       My bios only lets me say "Boot from a disk (hdd and ssd)", "Boot from CD", "Network" ,etc.
    >Boot-repair
       Didn't work.
    >try setting this right in grub-rescue
       Could work, but I get an error all the time saying "could not find "grub_real_boot_time"" when running "insmod normal".
    >wipe the entire HDD clean.
       even with all the HDD partitions deleted, grub still pops up from out of nowhere.
    >remove the HDD
       Yes this works the system boots in a blink of an eye.
    Last edited by Lacsapix (2014-07-17 10:17:57)

    thank you karol!
    a simple
    sudo dd if=/dev/zero of=/dev/sdb bs=446 count=1
    did the trick!

  • [SOLVED] UEFI system booting from MBR partition table and GRUB legacy

    I'm trying to understand once and for all the process by which Arch can be booted from a system with UEFI firmware and an MBR partition table. Some of the information on the wiki seems conflictual / non-nonsensical at times. Apologies in advance if this has been answered time and time again, but I did search around and all I found was fixes to get Arch to boot rather than comprehensive explanations of the boot process.
    Now, the way I would imagine it works is that it's just completely identical to the way it would work with a BIOS firmware. The UEFI firmware detects an MBR partitioning scheme (or is configured to know it's an MBR partitioning scheme), activates some "legacy" mode and executes the MBR boot code, just like a BIOS firmware would.
    The wiki however, says different. From the Macbook article: "Do not install GRUB onto /dev/sda !!! Doing so is likely to lead to an unstable post-environment."?
    So what is there in the MBR boot sector? Nothing?
    How does the firmware know what to boot if there's no 0xEF BIOS boot partition and no Grub stage 1 in the MBR boot sector?
    Also, how does installing Grub stage 1 to a partition work? Does it have to be at the beginning of the partition? Wouldn't that overwrite some existing data?
    I'm especially puzzled since many guides to installing Vista on a macbook recommend simply formatting as MBR, and installing as normal, which I suppose entails having the Windows installation process write its boot code to the MBR, ie the equivalent of installing grub stage 1 to /dev/sda rather than to the /boot partition, as the Macbook article suggests.
    Any input is appreciated.
    P.S. I realize it's probably simpler, if I just want to dual boot Windows and Arch, to install Windows 7 in UEFI-GPT mode, let it create the EFI System Partition, and then install GRUB 2 to that partition, but I'm still curious about the UEFI-MBR boot process.
    Last edited by padavoine (2012-06-06 09:35:10)

    padavoine wrote:
    CSM in UEFI firmwares do the exact same job as normal BIOS firmware.
    So it's something specific to the Mac that it's able to boot from a partition's VBR while ignoring the MBR?
    The reason that warning is given is because grub-legacy modifies more than just the MBR boot code region.  It can overwrite some parts of GPT header.
    Not true, the instruction is given in the context of an MBR format, not in the context of a GPT format, so there's nothing to overwrite and Stage 1.5 should be safely embeddable in the post-MBR gap.
    In BIOS boot (normal case in non-UEFI firmwares or CSM in UEFI firmwares) does not read the partitition table (atleast it is supposed to be dumb in this regard), it simply launches whatever boot code exists in the 1st 440-byte of the MBR region.
    So again, you're saying it's specific to the Mac UEFI that it lets you choose a partition whose VBR to load, regardless of what's in the MBR?
    I haven't used Macs so I can't comment on Mac firmware behaviour. But normal BIOS firmwares (legacy and CSM) launch only the MBR boot code and not the partition boot code. We need some chainload capable boot manager in the MBR to launch the partition VBR.
    grub-legacy does not know anything about GPT. So when you install grub-legacy to /dev/sda, it install the MBR boot code (stage1) and stage 1.5 code to the (supposed) post MBR gap. Since there is no actual post MBR gap in GPT (which has been taken over by the header and partition table), grub-legacy does not check for GPT and it assumes the post MBR gap actually exists which is invalid in case of GPT. grub-legacy embeds the stage 1.5 code in GPT header and table region (which grub assumes to be unused post MBR gap) and thus corrupts it.
    0xEF is the MBR type code for UEFISYS partition. grub stage 1 (used in grub-legacy, not in grub2) is the 440-byte boot code stored in MBR for use in BIOS boot.
    That's precisely my point: with neither proper executable code in the MBR (since grub was installed to a partition, not to the MBR) nor a UEFI system partition, what does the firmware default to, and how does it know what partition to boot from?
    In that case it might fallback to UEFI Shell (if it exists)  or give an error similar to the case where BIOS does not find any bootable code in 440-byte MBR region.
    So even with bootcamp/CSM, the disk also needs to be MBR partitioned. So Macs use something called "Hybrid GPT/MBR" ( http://rodsbooks.com/gdisk/hybrid.html ) where the MBR table is synced to match the first 3 partitions in the GPT table.
    I know what Bootcamp does, and that's not what I was referring to. I was referring to standalone Vista installs. I wasn't puzzled at the fact that they were using MBR, I was puzzled at the fact that contrary to the recommendations for the standalone Arch install on the wiki (with MBR partitioning, not GPT), they didn't do anything to try and prevent Windows from writing to the MBR.
    You can't prevent Windows from overwriting the MBR region. You have to re-install the bootloader (grub2/syslinux etc.) after installing Windows. That is the reason why it is recommended to install Windows first and linux later.
    Thats not true. I actually find it is much easier to install Windows UEFI-GPT using USB rather than a DVD.
    I haven't done it since the only UEFI system I own has no DVD drive, but I was under the impression that it was simply a matter of choosing DVD UEFI boot in the firmware's boot menu.
    format the USB as FAT32 and extract the iso to it. That it.
    No, thats not it, precisely, it doesn't work out of the box with a standard Windows install USB, you need to fiddle around:
    2.3 Extract bootmgfw.efi from [WINDOWS_x86_64_ISO]/sources/install.wim => [INSTALL.WIM]/1/Windows/Boot/EFI/bootmgfw.efi (using 7-zip aka p7zip for both the files), or copy it from C:\Windows\Boot\EFI\bootmgfw.efi from a working Windows x86_64 installation.
    2.4 Copy the extracted bootmgfw.efi file to [MOUNTPOINT]/efi/microsoft/boot/bootmgfw.efi .
    Most of the Windows isos already have /EFI/BOOT/BOOTX64.EFI file, so no need to extract the bootmgfw.efi file.
    There is no difference between in BIOS booting in UEFI firmwares and BIOS booting with legacy firmware.
    There has to be a difference, at least in the Mac firmware (sorry, I keep switching), since legacy firmware, AFAIK, cannot chainload a bootloader in a partition's VBR without there being some sort of "stage1" code in the MBR.
    No idea about Mac EFI. Apple made a spagetti out of UEFI Spec. To actually understand how Mac firmwares work, read the blog posts by Matthew Garrett of Redhat, about his efforts in getting Fedora to boot in Macs.

  • [SOLVED] /mnt and /mnt/boot on seperate partitions?

    I'd like to keep /mnt/boot on my ssd, and keep /mnt on my hdd. I know it's possible to keep /mnt on one partition, and /mnt/home on another, because I've done it on another computer. When I tried to do this new setup, pacstrap failed to install.
    Here's what I did
    mkdir /mnt/boot
    mount /dev/sda7 /mnt/boot #a logical partition on my ssd
    mount /dev/sdb3 /mnt #a large partition on my hdd
    Any suggestions?
    Last edited by cu3ba11 (2013-11-02 21:03:05)

    The mount point for / during installation is arbitrary. What you need to be asking is "Can / and /boot be on separate partitions?" And the answer is yes.
    However, the real problem is that you created and mounted /mnt/boot before mounting /mnt. This is pretty basic stuff, so I suggest you try to figure out why that can't work.
    Last edited by alphaniner (2013-11-01 21:01:31)

  • Just installed windows 7 Ultimate using Boot Camp. Problem is when I chose to boot the windows partition, I get the windows icon on the sreen showing that it is starting, but few second after I get a black screen

    Just installed windows 7 Ultimate using Boot Camp. Problem is when I choose to boot the windows partition, I get the windows icon on the screen showing that it is starting, but few second after, I get a blank screen. I suspect a driver (screen) issue, since I also installed Parallell using the boot camp partition and that works fine.
    Do anybody out there has an ideal of what to do to solve this issue.
    Thanks
    Pierre317

    Hi Pierre,
    more tips can be found here ...

  • Pavilion Touchsmart won't boot after resizing partition

    I have a Pavilion 14-n228ca on which I will primarily run Linux. So I followed the procedure I have used in the past to create a dual-boot system on XP and Vista systems, viz.
    - resize the NTFS filesystem on the primary Windows partition
    - delete the partition
    - recreate the partition with the exact same start byte but a smaller size matching the resized filesystem
    - create a new partition in the free space
    - install Linux (CentOS 6.5) in the new parition, which also installs GRUB in the MBR and creates a chain record to the original Windows partition. Normally, that lets me choose to boot either a Linux kernel or Windows.
    Linux runs when I boot the disk (notebook hard drive). I can mount all the Windows NTFS partitions and see the data. But I still want to occasionally run Windows. I believe it is version 8.1.
    When I try to boot the Windows partition from GRUB, I get windows boot manager: file \Boot\BCD - missing or contains errors If I try "OS Boot Manager" after pressing F9 at boot, I get a "trying to repair" splash screen which fails then drops to a repair menu.
    If I select command line, I get a working prompt but the normal Windows volume is not mounted.
    If I run "diskpart" I see all the disk partitions but the Windows volume has no drive letter. diskpart says the partition is valid.
    If I assign a drive letter and exit diskpart, I can then see the files in F: and run chkdsk which reports that the filesystem is OK.
    If I run "rstrui" it says "could not find offline boot volume"
    If I run "bootrec /scanos" it finds a valid volume \\?\GLOBALROOT\Device\HardDiskVolume4\Windows
    If I run "bootrec /rebuildbcd" it says "system cannot find the file specified"
    I tried booting before actuially installing Linux, so I presume the problem is to do with the partition name or something, not the MBR.
    How can I recover the BCD, or otherwise boot Windows, preferably without messing up the Linux installation ?

    Hello adaviel,
    I have read your post on how your notebook computer will not boot after resizing the partition in Linux, and I would be happy to guide you towards a resolution!
    For further information regarding the use of Linux on HP systems, please take a look at this document on Frequently Asked Questions About Linux (FAQs).
    I hope this helps!
    Best Regards
    MechPilot
    I work on behalf of HP
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the right to say “Thanks” for helping!

  • [SOLVED] Grub boots to rescue mode err: unknown filesystem every drive

    So I installed Arch and it all seemed to go reasonably well (well, had a little trouble installing GRUB to begin with, but I think that's just because I needed a BIOS boot partition at the start of the drive). I installed it onto a 4TB I have, which due to its size has a GPT partition table even though my mobo (Gigabyte GA-P67A-UD4-B3, don't think it matters though) uses a regular old BIOS. Initially it was two partitions, the Microsoft reserved partition then a big NTFS data partition. I shrunk the NTFS partition and then made (in this order on the disk, starting at third) an ext4 partition for /boot, a swap partition, and a big btrfs partition (in which I created subvolumes for /, /etc, /home and /var). GRUB wouldn't install (I forgot the exact error) but what I could find suggested it was because there needed to be room for it at the start of the disk, so I deleted the Microsoft reserved partition (Windows is installed on an SSD, and its bootloader is on another hard drive entirely, so I didn't think I needed it) and created an empty partition with the right code using gdisk, then I could install GRUB to the 4TB HDD.
    Unfortunately, when I try to boot into GRUB it immediately comes up with error: unknown filesystem and dumps me at the GRUB rescue prompt. Using ls, I can see my HDDs and their partitions, but whenever I try to use (for example) ls (hd0,gpt3)/ - which I think should probably be the ext4 boot partition, but it does this for everything - it just says error: unknown filesystem again.
    This seems pretty close to (if not exactly the same as) my problem, so I tried what he suggested, but when I tried to run the command he says worked, (grub-install --recheck --disk-module=native /dev/sda) - and don't worry, I didn't do that blindly, I know /dev/sda is my 4TB HDD - I just get the error grub-install: --disk-module: (PROGRAM ERROR) Option should have been recognized!?. So I'm all out of ideas and I've been trying for a few hours. Please help me, before I go insane... more insane. I can boot the USB drive I used to install Arch and chroot into my installation, but I haven't found a way to actually boot the installation yet.
    SOLVED: Apparently the partition I was using for /boot was too far back on the drive (past the first 2TB). When I shuffled partitions around so that the /boot partition was near the start of the drive (it starts at sector 2048 now!) that seemed to fix it.
    Last edited by Slashee the Cow (2015-04-12 15:36:51)

    Tried using insmod btrfs in the grub rescue shell last night. Didn't work, can't remember if the insmod command itself gave me an error or whether it still couldn't see any files or anything. Tried it again today, but that was after I converted /dev/sda3 back to ext4 and mounted it at /boot (since it being ext2 wasn't working, and not using it wasn't working, so I figure what's the harm) and I just got error: unknown filesystem.
    Anyway: using grub-install from outside chroot seems to work (still can't use --disk-module), but grub-mkconfig just generates this:
    # DO NOT EDIT THIS FILE
    # It is automatically generated by grub-mkconfig using templates
    # from /etc/grub.d and settings from /etc/default/grub
    ### BEGIN /etc/grub.d/00_header ###
    insmod part_gpt
    insmod part_msdos
    if [ -s $prefix/grubenv ]; then
    load_env
    fi
    if [ "${next_entry}" ] ; then
    set default="${next_entry}"
    set next_entry=
    save_env next_entry
    set boot_once=true
    else
    set default="0"
    fi
    if [ x"${feature_menuentry_id}" = xy ]; then
    menuentry_id_option="--id"
    else
    menuentry_id_option=""
    fi
    export menuentry_id_option
    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 load_video {
    if [ x$feature_all_video_module = xy ]; then
    insmod all_video
    else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
    fi
    if [ x$feature_default_font_path = xy ] ; then
    font=unicode
    else
    insmod ext2
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root ec4cf3cd-d72d-4988-a2ce-421f45d52824
    else
    search --no-floppy --fs-uuid --set=root ec4cf3cd-d72d-4988-a2ce-421f45d52824
    fi
    font="/usr/share/grub/unicode.pf2"
    fi
    if loadfont $font ; then
    set gfxmode=auto
    load_video
    insmod gfxterm
    set locale_dir=$prefix/locale
    set lang=en_US
    insmod gettext
    fi
    terminal_input console
    terminal_output gfxterm
    if [ x$feature_timeout_style = xy ] ; then
    set timeout_style=menu
    set timeout=5
    # Fallback normal timeout code in case the timeout_style feature is
    # unavailable.
    else
    set timeout=5
    fi
    ### END /etc/grub.d/00_header ###
    ### BEGIN /etc/grub.d/10_linux ###
    ### END /etc/grub.d/10_linux ###
    ### BEGIN /etc/grub.d/20_linux_xen ###
    ### END /etc/grub.d/20_linux_xen ###
    ### BEGIN /etc/grub.d/30_os-prober ###
    ### 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.
    ### END /etc/grub.d/40_custom ###
    ### BEGIN /etc/grub.d/41_custom ###
    if [ -f ${config_directory}/custom.cfg ]; then
    source ${config_directory}/custom.cfg
    elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
    source $prefix/custom.cfg;
    fi
    ### END /etc/grub.d/41_custom ###
    ### BEGIN /etc/grub.d/60_memtest86+ ###
    if [ "${grub_platform}" == "pc" ]; then
    menuentry "Memory Tester (memtest86+)" --class memtest86 --class gnu --class tool {
    search --fs-uuid --no-floppy --set=root ec4cf3cd-d72d-4988-a2ce-421f45d52824
    linux16 /boot/memtest86+/memtest.bin
    fi
    ### END /etc/grub.d/60_memtest86+ ###
    I'm not an expert on GRUB configuration files, but I figured that even if that didn't just boot me straight to the rescue shell, it wasn't going to boot anything... other than memtest86+ maybe. So I went back into chroot and run grub-mkconfig and it generated this:
    # DO NOT EDIT THIS FILE
    # It is automatically generated by grub-mkconfig using templates
    # from /etc/grub.d and settings from /etc/default/grub
    ### BEGIN /etc/grub.d/00_header ###
    insmod part_gpt
    insmod part_msdos
    if [ -s $prefix/grubenv ]; then
    load_env
    fi
    if [ "${next_entry}" ] ; then
    set default="${next_entry}"
    set next_entry=
    save_env next_entry
    set boot_once=true
    else
    set default="0"
    fi
    if [ x"${feature_menuentry_id}" = xy ]; then
    menuentry_id_option="--id"
    else
    menuentry_id_option=""
    fi
    export menuentry_id_option
    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 load_video {
    if [ x$feature_all_video_module = xy ]; then
    insmod all_video
    else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
    fi
    if [ x$feature_default_font_path = xy ] ; then
    font=unicode
    else
    insmod part_gpt
    insmod btrfs
    set root='hd0,gpt5'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt5 --hint-efi=hd0,gpt5 --hint-baremetal=ahci0,gpt5 b21e6211-5e7a-4769-9f53-b9b5d554a242
    else
    search --no-floppy --fs-uuid --set=root b21e6211-5e7a-4769-9f53-b9b5d554a242
    fi
    font="/root/usr/share/grub/unicode.pf2"
    fi
    if loadfont $font ; then
    set gfxmode=auto
    load_video
    insmod gfxterm
    set locale_dir=$prefix/locale
    set lang=en_US
    insmod gettext
    fi
    terminal_input console
    terminal_output gfxterm
    if [ x$feature_timeout_style = xy ] ; then
    set timeout_style=menu
    set timeout=5
    # Fallback normal timeout code in case the timeout_style feature is
    # unavailable.
    else
    set timeout=5
    fi
    ### END /etc/grub.d/00_header ###
    ### BEGIN /etc/grub.d/10_linux ###
    menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-b21e6211-5e7a-4769-9f53-b9b5d554a242' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_gpt
    insmod ext2
    set root='hd0,gpt3'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 184916fd-57a7-48cf-858e-93a5d339ade2
    else
    search --no-floppy --fs-uuid --set=root 184916fd-57a7-48cf-858e-93a5d339ade2
    fi
    echo 'Loading Linux linux ...'
    linux /vmlinuz-linux root=UUID=b21e6211-5e7a-4769-9f53-b9b5d554a242 rw rootflags=subvol=root quiet
    echo 'Loading initial ramdisk ...'
    initrd /initramfs-linux.img
    submenu 'Advanced options for Arch Linux' $menuentry_id_option 'gnulinux-advanced-b21e6211-5e7a-4769-9f53-b9b5d554a242' {
    menuentry 'Arch Linux, with Linux linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-b21e6211-5e7a-4769-9f53-b9b5d554a242' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_gpt
    insmod ext2
    set root='hd0,gpt3'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 184916fd-57a7-48cf-858e-93a5d339ade2
    else
    search --no-floppy --fs-uuid --set=root 184916fd-57a7-48cf-858e-93a5d339ade2
    fi
    echo 'Loading Linux linux ...'
    linux /vmlinuz-linux root=UUID=b21e6211-5e7a-4769-9f53-b9b5d554a242 rw rootflags=subvol=root quiet
    echo 'Loading initial ramdisk ...'
    initrd /initramfs-linux.img
    menuentry 'Arch Linux, with Linux linux (fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-fallback-b21e6211-5e7a-4769-9f53-b9b5d554a242' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_gpt
    insmod ext2
    set root='hd0,gpt3'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 184916fd-57a7-48cf-858e-93a5d339ade2
    else
    search --no-floppy --fs-uuid --set=root 184916fd-57a7-48cf-858e-93a5d339ade2
    fi
    echo 'Loading Linux linux ...'
    linux /vmlinuz-linux root=UUID=b21e6211-5e7a-4769-9f53-b9b5d554a242 rw rootflags=subvol=root quiet
    echo 'Loading initial ramdisk ...'
    initrd /initramfs-linux-fallback.img
    ### END /etc/grub.d/10_linux ###
    ### BEGIN /etc/grub.d/20_linux_xen ###
    ### END /etc/grub.d/20_linux_xen ###
    ### BEGIN /etc/grub.d/30_os-prober ###
    menuentry 'Windows Vista (loader) (on /dev/sdb1)' --class windows --class os $menuentry_id_option 'osprober-chain-4E94BAB294BA9C41' {
    insmod part_gpt
    insmod ntfs
    set root='hd1,gpt1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt1 --hint-efi=hd1,gpt1 --hint-baremetal=ahci1,gpt1 4E94BAB294BA9C41
    else
    search --no-floppy --fs-uuid --set=root 4E94BAB294BA9C41
    fi
    chainloader +1
    menuentry 'Windows Vista (loader) (on /dev/sde1)' --class windows --class os $menuentry_id_option 'osprober-chain-CEF01053F010445D' {
    insmod part_msdos
    insmod ntfs
    set root='hd4,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos1 --hint-efi=hd4,msdos1 --hint-baremetal=ahci4,msdos1 CEF01053F010445D
    else
    search --no-floppy --fs-uuid --set=root CEF01053F010445D
    fi
    chainloader +1
    menuentry 'Windows Vista (loader) (on /dev/sde5)' --class windows --class os $menuentry_id_option 'osprober-chain-4E94BAB294BA9C41' {
    insmod part_msdos
    insmod ntfs
    set root='hd4,msdos5'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos5 --hint-efi=hd4,msdos5 --hint-baremetal=ahci4,msdos5 4E94BAB294BA9C41
    else
    search --no-floppy --fs-uuid --set=root 4E94BAB294BA9C41
    fi
    chainloader +1
    ### 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.
    ### END /etc/grub.d/40_custom ###
    ### BEGIN /etc/grub.d/41_custom ###
    if [ -f ${config_directory}/custom.cfg ]; then
    source ${config_directory}/custom.cfg
    elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
    source $prefix/custom.cfg;
    fi
    ### END /etc/grub.d/41_custom ###
    ### BEGIN /etc/grub.d/60_memtest86+ ###
    ### END /etc/grub.d/60_memtest86+ ###
    Still didn't work though.
    I don't know grub config, but is the UUID specified in
    linux /vmlinuz-linux root=UUID=b21e6211-5e7a-4769-9f53-b9b5d554a242 rw rootflags=subvol=root quiet
    supposed to be the UUID for /boot or /? Because the UUID there is for the btrfs partition being mounted at / (which I guess would explain why it has the correct subvol listed, which I'm not sure if it's necessary, given that should be the default subvolume). So... that's probably alright (just something that stood out to me).
    As for installing grub on another disk: I suppose I could try, though I'd rather keep it on one drive if I can (sometimes it gets complicated enough having Windows and my Windows bootloader on different drives... I should probably try moving the Windows bootloader to the SSD where Windows is installed. Would it matter which drive? The options are:
    sda: 4TB, GPT table, the one I'm having problems with now
    sdb: 2TB, MBR table, nothing in boot sector AFAIK
    sdc: 240GB SSD, GPT table, would rather not use it since Windows is installed on there, even if its bootloader isn't
    sdd: 1TB, MBR table, nothing in boot sector AFAIK
    sde: 500GB, MBR table, has the Windows bootloader so I'd rather not mess that up (although given it's the smallest and I have no free SATA ports, it'll be next to go when I need more space, so I might want to move the bootloader)
    (sdf and sdg which appear in lsblk earlier are just USB flash drives, and I'd rather not have to rely on having to use one of them to boot Linux).
    As for repartitioning /dev/sda: as long as I can do it non-destructively, sure. Well I mean non-destructively for the NTFS partition, which is mostly full of Steam games (and I might have enough room on other drives and portable drives to keep the rest safe), but on my crappy Australian internet connection (aren't they all) it'd probably take me a couple of weeks to redownload them. I don't mind if I have to get rid of the Linux partitions, I already tried going through the install again once before to try to get it to work, another time isn't going to matter. So I guess I could try using gparted to delete the Linux partitions, move the NTFS partition to the end of the disk, and recreate the Linux partitions in front of it (although moving that much data might take a while, so I'd probably want to do it overnight). For reference, right now it's:
    128MB of unformatted space (where the Microsoft reserved partition was, but now it's flagged as a BIOS boot partition, even though it's far bigger than it needs to be for that, I didn't feel like moving the other partitions back just to claim less than 128MB)
    ~2.7TB NTFS data partition (important)
    ~1GB ext4 /boot partition
    8GB swap partition
    ~1TB btrfs partition with subvolumes mounted at /, /home, /etc and /var

  • Booting from a partitioned drive

    I have 1,5 TB drive and want to create 2 partitions. One for cloning using Super Duper and second back up by data files. Is this possible? Because I read that Apple doesn't officially support booting from Apple partition map on Intel Macs and doesn't allow to install the OS X.
    Thanks,

    Well, after using disc utility, I had a bad luck... kernel panic during the partition. And the computer panics anytime the drive is plugged in. Firewire and USB. I tried my other computer .... the same thing. That means the drive is dead!
    Oh Well...
    Here is the error:
    Wed May 13 09:40:58 2009
    panic(cpu 2 caller 0x001F9445): "jnl: mod block start: bufsize 512 not a multiple of block size 4096\n"@/SourceCache/xnu/xnu-1228.9.59/bsd/vfs/vfs_journal.c:2282
    Backtrace (CPU 2), Frame : Return Address (4 potential args on stack)
    0x8d8af2a8 : 0x12b4f3 (0x45b13c 0x8d8af2dc 0x1335e4 0x0)
    0x8d8af2f8 : 0x1f9445 (0x46c6e4 0x200 0x1000 0x0)
    0x8d8af348 : 0x332a34 (0x9e55d10 0x7ccc7a80 0x0 0x200)
    0x8d8af3e8 : 0x33be77 (0xc140004 0x1 0x0 0x8d8af778)
    0x8d8af7a8 : 0x33443e (0xc140004 0xa151804 0x0 0x0)
    0x8d8af8b8 : 0x335ea6 (0x0 0xb6b0364 0x0 0x0)
    0x8d8af9a8 : 0x1f5d9f (0xa97a258 0x1049d8c0 0xbffffdc4 0x0)
    0x8d8af9f8 : 0x1df47f (0xa97a258 0x1049d8c0 0xbffffdc4 0x0)
    0x8d8aff28 : 0x1dfb40 (0xadb7ba4 0x8d8aff48 0xb6b02a4 0x1)
    0x8d8aff78 : 0x3df460 (0xadb7ba4 0xb6b0260 0xb6b02a4 0x0)
    0x8d8affc8 : 0x1a0887 (0xb3d97a0 0x0 0x1a30b5 0xa25e640)
    No mapping exists for frame pointer
    Backtrace terminated-invalid frame pointer 0xbffffe18
    BSD process name corresponding to current thread: mount_hfs
    Mac OS version:
    9G55
    Kernel version:
    Darwin Kernel Version 9.6.0: Mon Nov 24 17:37:00 PST 2008; root:xnu-1228.9.59~1/RELEASE_I386
    System model name: MacPro3,1 (Mac-F42C88C8)
    Message was edited by: Girshon Rutstein

  • [SOLVED] Dual Boot Window 7 & Arch on a Uefi system.

    From the Wiki
    Windows 7 x86_64 versions support booting in x86_64 UEFI mode from GPT disk only, OR in BIOS mode from MBR/msdos disk only. They do not support IA32 (x86 32-bit) UEFI boot from GPT/MBR disk, x86_64 UEFI boot from MBR/msdos disk, or BIOS boot from GPT disk.
    I don't understand this. As stated in the title I have a ueif system so that means I have to create a GPT disk ? I already have a gpt disk which I confirmed by running Arch Live USB. Under type it said GPT. I don't understand this at all
    However if Arch is installed in BIOS-GPT in one disk and Windows is installed in BIOS-MBR mode in another disk,  then the BIOS bootloader used by Arch CAN boot the Windows in the other disk, if the bootloader itself has the ability to chainload from another disk.
    Note: If Arch and Windows are dual-booting from same disk, then Arch SHOULD follow the same firmware boot mode and partitioning combination used by the installed Windows in the disk.
    In the Note above it says both Arch and Windows follow the same boot mode if they are dual booting from same disk. I DO NOT want to do this. I have already decided to partition  my drive with 200 Gb going to Windows and 500 Gb going to Arch. Does this mean that I should install both in different modes i.e. Arch in Bios-GPT and Windows in Bios-MBR.
    The recommended way to setup a Linux/Windows dual booting system is to first install Windows, only using part of the disk for its partitions. When you have finished the Windows setup, boot into the Linux install environment where you can create additional partitions for Linux while leaving the existing Windows partitions untouched.
    UEFI systems
    Both Gummiboot and rEFInd autodetect Windows Boot Manager \EFI\Microsoft\Boot\bootmgfw.efi and show it in their boot menu, so there is no manual config required.
    For GRUB(2) follow GRUB#Windows_Installed_in_UEFI-GPT_Mode_menu_entry.
    Syslinux (as of version 6.02 and 6.03-pre9) and ELILO do not support chainloading other EFI applications, so they cannot be used to chainload \EFI\Microsoft\Boot\bootmgfw.efi .
    Computers that come with newer versions of Windows often have secure boot enabled. You will need to take extra steps to either disable secure boot or to make your installation media compatible with secure boot.
    Being a beginner should I go with Gummiboot then. GRUB made a mess last time.
    Also my secure boot is NOT enabled so is that good.
    I have read the FAQs, Beginner's guide, Installation Guide, Dual Boot wiki entry but I just don't understand the above concepts. But it looks this this is the main thing in dual booting. Almost everything else is doable but this I have to get right on account of what happened the last time I installed Arch without getting the above right.
    Last edited by Some Arch Lovin (2014-06-14 08:53:14)

    A few issues with the dual boot setup
    Hello again, I lost my dual factor authentication grid from lastpass. Opensuse was acutally overwriting new pdf files over my old pdf files so now that grid pdf is actually an Arch cheat cheet with the name last_pass_grid.pdf. And the gmail account I used to register to Arch forums is also in last pass.
    This is why I created another account. I am some arch lovin.
    The installation went smoothly but I could not dual boot Windows7 with Arch because my Win7 image is not UEFI bootable so had to dual boot win8(not a fan at all) and arch.
    Almost everything is working correctly. I have a few issues that aren't affecting how the system is working but they still need sorting out.
    I'll do them one at a time but I want to know from the admins if I should start a new thread? Because in a way this thread accomplished it job i.e. win7 and arch dual booting in uefi system.
    If the answer is yes I should create a new thread depending upon the issue then I will do that but in case its a no since I have only 2-3 problems I am going to ask help for the first one.
    My gummiboot is not working on startup. I have to press f12 and use bios booting menu to boot. The problem with that is if I put Windows at the top of the boot priority the bios does not show F12 and F2 at the time of booting up so I can't access the boot menu. I have to boot into Windows and crash it by holding the power button and then the F12 options shows up and I am able to boot into Arch. If I put Arch at the top then Windows keeps restoring back to an earlier version due to start up options.
    NOTE : I can't be sure but one it did work(only once). I checked the images online to compare with what I saw and its very similar. An all black screen with three bootloading options
    Windows
    Arch
    Opensuse(don't know why I created a completely new GPT partition table)
    This is what I did while installing Gummiboot
    # mount -t efivarfs efivarfs /sys/firmware/efi/efivars
    # pacman -S gummiboot
    # gummiboot install
    I tried going through the gummiboot to see if I can do something but it very difficult to comprehend as a beginner. All I get is the characters gummiboot understands but thats all.
    Last edited by Archer61 (2014-06-11 13:48:56)

  • How to separately backup the Boot Camp drivers partition from Leopard DVD?

    I used Disk Utility and my only (and expensive) DVD+R DL disc to make a backup copy of my Leopard DVD, and it worked perfectly to install Leopard on my MacBook Pro.
    However, that was before I learned that the Boot Camp drivers was now on a separate, PC-only partition on the DVD. So while my backup copy works great to install Leopard, I have no backup of the Boot Camp driver CD.
    I tried several tricks, including booting into Windows Vista and using PowerISO to attempt to make an ISO image of the Boot Camp driver partition (shows up as 400 MB or so). However, the ISO image generated is a whopping 7.6 GB, same size as the full Leopard DVD. I then tried to take that back into the Mac OS side, but it was "unmountable". Toast 8 was able to make an image of the full DVD that (I'd presume, as did previous versions of Toast) would contain both partitions of an ISO-9660 volume, but when I mounted that disk image with Toast 8, I didn't get the two-mounted-volume like I'd normally expect to see.
    I'd really like to know how to backup this volume - I demo this system regularly on my MacBook for clients, and I don't want to have to keep using my nice, pristine Leopard DVD when I have to do my weekly re-install. Any thoughts on how to get a simple extraction of the actual volume used for the Boot Camp drivers?
    Thanks much for the time,
    MBJ

    Hi Stefan,
    Thanks for taking the time to reply to my question! Although I think your steps will "work", per se (and I will try them out as soon as I can), I'm something of a purist in regards to my backups and so this method seems a little hackish as opposed to a process that actually images the volume in question (I'm also curious from a technical perspective, as the Boot Camp Assistant Beta used to allow for a dedicated MacintoshDrivers disc to be burned from it—I liked that method better, to be honest).
    Thanks again! I'll keep checking back here for other comments, and will let you know how the method you suggested works out.
    Best wishes,
    MBJ

  • Repartition a Boot Camp Windows partition

    I am trying to restore an Acronis 10 image backup on a Boot Camp Win partition. Acronis does not see the Win partition. I tried Partition Manager 8 to repartition inside the Win partition but PM says it cannot see the drive letters, though its small tools software seem to be ok with that. Has anyone tried to restore an image of another drive on a Boot Camp Win partition ?
    Thanks !
    Andrei

    You may want to post your question in the Boot Camp forums:
    http://discussions.apple.com/category.jspa?categoryID=237

  • Can't boot from Ubuntu partition after upgrading to Yosemite

    When i go to Disk Utility the Ubuntu partition appears as it always have, i had installed since Mavericks refind to boot from any partition. Now refind doesn't work and the alt/option key doesn't work either. Does anyone know a way to fix this?

    A extensive report already written is in the Ubuntu stacks as
    Dual boot Linux and Yosemite
    Basically you need to follow http://www.rodsbooks.com/refind/yosemite.html
    wherein it explains that Yosemite is using a new LVM bootup from within the Recovery Partitions 10.10.
    This messes up REFIT/REFIND tools  which have previously installed Partition 1.S
    See my current Table below , wherein << are my comments
    Current GPT partition table:
    #      Start LBA      End LBA  Type
    1             40       409639  EFI System (FAT)    << old preferred site for REFIT/REFIND tools
    2         409640    154061023  Mac OS X HFS+ << main Mac partition
    3      154061024    155330559  Mac OS X Boot  << Recovery 10.10 , installed by Yosemite update, used to start MAC boot.  BUT is not shown by Disk Utility, to prevent its naive deletion which would kill the MAC boot.
    4      155330560    156598271  Mac OS X HFS+ << old Recovery 10.9, simply retained
    5      157869786    228772129  Unknown << My Ubuntu partition
    6      228772130    236765969  Linux Swap << which was shortened by 200 MB to make room for 7)
    7      236765970    236974814  Mac OS X HFS+ << installation site of REFIND.  Though 4) could have been used, there is a possibility that Apple might have future plans for this small 4) partition.  
    With 7) created (see detail below),  my REFIND install command under MAC, within Downloads/refind-bin-0.8.3/ was:
    sudo ./install.sh  --alldrivers --ownhfs  /dev/disk0s7
    There was still required the edit if refind.conf.sample specified in Yosemite.html, which I named refind.conf.edit1
    This was copied with:
    sudo cp refind.conf.edit1  /Volumes/macefi/System/Library/CoreServices/refind.conf
    macefi  is my name for the MAC  /dev/disk0s7 mount point, equivalent to /dev/sda7 under Linux
    CAREFULLY do read Yosemite.html,  as the instructions here are too terse by themselves!!!!
    There are 2 routes to  boot Ubuntu, and then creat 7) with GPARTED
    a) If you can access the GRUB shell under an old REFIT/REFIND installation, partitions will be shown by:
    grub> ls
    Presence of a Linux file system can be confirmed by a command like:
    grub> ls (hd0,gpt5)/
    Output of
    grub > ls (hd0,gpt5)/boot/grub/
    should include a grub.cfg file.  Then you can boot as usual with
    grub > configfile  (hd0,gpt5)/boot/grub/grub.cfg
    After boot up, start GPARTED
    b) Alternatively boot with the Ubuntu install disk, and choose the Demo option
    Open a text console, and get admin proviledge with:
    $ sudo su
    # gparted
    Using GPARTED, unmount if necessary  any terminal SWAP partition, such as my 6) above
    Then shrink the SWAP partition end by a trivial 200 MB,
    Create a HFS+ partition in like my 7) for a coming REFIND installation
    Note, that a file /etc/fstab contains a SWAP partition specification, which should be edited for automated SWAP start.
    # sudo blkid  /dev/sda7
    will report the SWAP space specs LONG  uuid code.  This can be copied into memory by dragging the mouse over the uuid
    Then SHIFT-CONTROL-C  will copy it into memory.   Start an edit with:
    $ sudo nano /etc/fstab
    delete the old swap uuid, and paste in the replacement with
    SHIFT-CONTROl-V
    and swap should mount upon reboot, or with:
    $ sudo swapon -a
    Check with:
    $ free
    which should report none-zero swap space.

  • [solved] triple boot on mac with ubuntu

    i have a macbook pro 5,5 if that helps, i installed ubuntu on the macbook with refit and i now want to install arch  as well. i discovered that i can not see any partitions after four on my mac and therefore can not have a boot partition for arch and ubuntu has the grub boot on its partition, my questions are should i and how do i add arch to ubuntu's grub and boot from there, or is there a better way that gets around the four partition problem.
    i apologize if this has been asked before but my searches came up with nothing
    thanks
    Last edited by xcabal (2012-07-28 02:01:21)

    You probably need to learn more about partitioning and partition types.  Read everything relevant here:
    http://www.dedoimedo.com/computers/gparted.html
    Pay close attention to partition types and extended partitions.  You likely need to use an extended partition.
    (Not sure why 40 people looked at this before me and nobody bothered to tell you the easy and obvious suggestion...nice.)
    Last edited by andrekp (2012-07-27 12:27:52)

  • Boot from 2nd partition on mini

    I have a new mac mini with os x server on it. It has two partitions and I tried to install mac os x onto the other partition so I could boot from that. I have an apple external dvd drive attached to the mini.
    Everything went well, it allowed me to install to the partition I wanted. Then when it does a reboot it will not boot with the mac os x disk in the dvd drive and if I take it out it boots back to mac os x server partition. If I hold down the Option Key at the start it does not show me the partition with the os x on it.
    Using finder I can see a bunch of pkg files in a folder called Mac OS X install Data on the partition I want to use. Is there a way of getting these to install?
    Sorry if this is a dumb question but I am fairly new to macs.
    Thanks.

    rchealey wrote:
    Curiously when you boot from this partition, you get virtually the exact same experience as you do when booting from the recovery partition except that the recovery partition tends to suggest that it will download and install Lion, whereas booting from the partition containing the install doesn't mention download.
    That's normal behavior. The Recovery HD only has enough code to go to Apple's servers and DL the installer; whereas, the InstallESD contains everything. Do note, however, that running either will check Apple's servers for additional components, whatever those might be. Thus, Internet access is required to do either.

Maybe you are looking for