help-grub
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cannot install Grub2


From: Артём А
Subject: Re: Cannot install Grub2
Date: Wed, 7 Mar 2012 19:32:34 +0300

I changed a little my partition layout since your letter, but this didn't

helped.

$ sudo parted -l

Model: ATA ST3400620AS (scsi)

Disk /dev/sda: 400GB

Sector size (logical/physical): 512B/512B

Partition Table: msdos

Disk Flags:


Number Start End Size Type File system Flags

1 475MB 21.5GB 21.1GB primary ext4

2 21.6GB 36.9GB 15.4GB primary ext4 boot

3 37.7GB 367GB 329GB extended lba

5 39.9GB 116GB 76.2GB logical ntfs

6 116GB 119GB 2973MB logical linux-swap(v1)

7 119GB 367GB 247GB logical ext4

4 367GB 400GB 33.3GB primary ntfs



2012/3/6 Jordan Uggla <address@hidden>
On Sun, Mar 4, 2012 at 7:46 AM, Артём Алексюк <address@hidden> wrote:
> Hello.
> I'm using Grub1.99 (pc version, Archlinux) and there are some problems with
> it. I used testdisk some time ago, maybe it's a reason of this problem.
> Grub0.x and Windows's loader are working OK.
>
> $ sudo grub-install /dev/sda
> /usr/sbin/grub-setup: error: hostdisk//dev/sda appears to contain a udf
> filesystem which isn't known to reserve space for DOS-style boot. Installing
> GRUB there could result in FILESYSTEM DESTRUCTION if valuable data is
> overwritten by grub-setup (--skip-fs-probe disables this check, use at your
> own risk).
>
> $ sudo grub-setup --skip-fs-probe /dev/sda
> grub-setup: warn: Attempting to install GRUB to a disk with multiple partition
> labels or both partition label and filesystem. This is not supported yet..
> grub-setup: warn: Embedding is not possible. GRUB can only be installed in
> this setup by using blocklists. However, blocklists are UNRELIABLE and their
> use is discouraged..
> grub-setup: error: will not proceed with blocklists.
>

In both of these cases it's probably that you have left over bits from
previous filesystems/partition tables which make it impossible for
grub to ensure safety. We need to figure out what remnants grub is
seeing, and remove them (this will also likely affect other utilities
and so is a good thing to prevent data corruption in general).

> $ sudo fdisk -l /dev/sda
>
> Disk /dev/sda: 400.1 GB, 400088457216 bytes
> 255 heads, 63 sectors/track, 48641 cylinders, total 781422768 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: 0x05f2265b
>
> Device Boot Start End Blocks Id System
> /dev/sda1 * 2048 42088447 21043200 83 Linux
> /dev/sda2 42090300 72144895 15027298 83 Linux
> /dev/sda3 73593765 716466869 321436552+ f W95 Ext'd (LBA)
> /dev/sda4 716466870 781417654 32475392+ 7 HPFS/NTFS/exFAT
> /dev/sda5 77979573 226821734 74421081 7 HPFS/NTFS/exFAT
> /dev/sda6 226821798 232628223 2903213 82 Linux swap / Solaris
> /dev/sda7 233119278 716466869 241673796 83 Linux

Please provide the output of "sudo parted -l". Parted is familiar with
filesystems and is aware of many more partition labels than fdisk, and
will hopefully give us an error message which is more useful to fixing
the problem.

--
Jordan Uggla (Jordan_U on irc.freenode.net)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]