[SOLVED] antiX 13.1 and Blag 140k in dual boot - Page 2

Dave · posted: 2013-09-18 18:45

taigarden wrote:
Dave wrote:Ok then I would suggest to look up how to install grub from blag to another device. That way you can install blag's grub to the root partition of the blag install. If it is not possible you may need to install blag again and choose install to root partition instead of install to mbr.

Another option would be to use super grub disk to install grub to the root partition of blag.

Dave
Since I can not access Blag system, I might opt to use super grub disk to install grub to the root partition of Blag.

There are two versions of super grub disk:

(a) Super GRUB Disk, which uses grub legacy.
(b) Super GRUB2 Disk, which uses grub2.

Which one do you suggest?
Thank you.

Depends which version of grub you would like to use....
I was under the impression you and roky were working on chainloading from grub legacy to grub 2. In this case you would want to use super grub2disk. However if you would like to install grub legacy you could install grub to the root partition using your antiX installation and the terminal.

Here should be enough information to install to a partition using terminal / grub console using the antiX installation.

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://wiki.archlinux.org/index.php/GRUB_Legacy"
linktext was:"https://wiki.archlinux.org/index.php/GRUB_Legacy"
====================================

taigarden · posted: 2013-09-18 18:46

rokytnji wrote:Hmmm. though I know nothing about Blag. 1st I would make sure os-prober is installed in Blag.

I made a post in Blag's Forum asking if os-prober is installed in Blag. Let´s wait for any answer they have.

taigarden · posted: 2013-09-18 18:59

Dave wrote: Depends which version of grub you would like to use....
I was under the impression you and roky were working on chainloading from grub legacy to grub 2. In this case you would want to use super grub2disk. However if you would like to install grub legacy you could install grub to the root partition using your antiX installation and the terminal.

Here should be enough information to install to a partition using terminal / grub console using the antiX installation.

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://wiki.archlinux.org/index.php/GRUB_Legacy"
linktext was:"https://wiki.archlinux.org/index.php/GRUB_Legacy"
====================================

Yes, we were working on chainloading from grub legacy to grub 2. I also tried with boot-repair-disk which uses grub2 but it didn't work because of RAID and lvm format.

Now, I think it will be easier to work with grug legacy. I will review your link to see how can I do it from antiX.

male · posted: 2013-09-18 19:09

The latest stable release, BLAG 140k, is based on Fedora 14, and was released on 4 May 2011.

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://en.wikipedia.org/wiki/BLAG_Linux_and_GNU"
linktext was:"http://en.wikipedia.org/wiki/BLAG_Linux_and_GNU"
====================================

Fedora14 and Grub2 ? __{{emoticon}}__

taigarden · posted: 2013-09-18 20:27

male wrote:
The latest stable release, BLAG 140k, is based on Fedora 14, and was released on 4 May 2011.

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://en.wikipedia.org/wiki/BLAG_Linux_and_GNU"
linktext was:"http://en.wikipedia.org/wiki/BLAG_Linux_and_GNU"
====================================

Fedora14 and Grub2 ? __{{emoticon}}__

Good point. Grub legacy will make things easier, at least for me!

taigarden · posted: 2013-09-19 02:18

male wrote: Please spending of antiX as root
Code: Select all
dpkg --list | grep grub
dpkg --list | grep os-prober
fdisk -lu
parted -l

These are the outputs:

Code: Select all

root@antiX1:/home/hugo# dpkg --list | grep grub
ii  grub-common                          1.99-27+deb7u1                     i386         GRand Unified Bootloader (common files)
ii  grub-gfxboot                         0.97-48                            i386         GRand Unified Bootloader
root@antiX1:/home/hugo# dpkg --list | grep os-prober
ii  os-prober                            1.58                               i386         utility to detect other OSes on a set of drives
root@antiX1:/home/hugo# fdisk -lu

Disk /dev/sda: 40 GB, 40015987200 bytes
255 heads, 63 sectors/track, 4865 cylinders, total 78156225 sectors
Units = sectors of 1 * 512 = 512 bytes

   Device Boot      Start         End      Blocks   Id  System 
/dev/sda1   *        2048    24702975    12353953   83  Linux
Warning: Partition 1 does not end on cylinder boundary.
/dev/sda2        24702976    47157247    11229435   83  Linux
Warning: Partition 2 does not end on cylinder boundary.
/dev/sda3        47157248    78163967    15502725    5  Extended
Warning: Partition 3 does not end on cylinder boundary.
/dev/sda5        47159296    65701887     9269505   83  Linux
Warning: Partition 5 does not end on cylinder boundary.
/dev/sda6        65703936    75075583     4690980   83  Linux
Warning: Partition 6 does not end on cylinder boundary.
/dev/sda7        75077632    78163967     1542240   82  Linux swap
Warning: Partition 7 does not end on cylinder boundary.

Disk /dev/sdb: 100 GB, 100027630080 bytes
255 heads, 63 sectors/track, 12161 cylinders, total 195366465 sectors
Units = sectors of 1 * 512 = 512 bytes

   Device Boot      Start         End      Blocks   Id  System 
/dev/sdb1   *        2048     1026047      514048   83  Linux
Warning: Partition 1 does not end on cylinder boundary.
/dev/sdb2         1026048   195371007    97177185   8e  Linux LVM
Warning: Partition 2 does not end on cylinder boundary.

Disk /dev/sdc: 15 GB, 15998169600 bytes
255 heads, 63 sectors/track, 1945 cylinders, total 31246425 sectors
Units = sectors of 1 * 512 = 512 bytes

   Device Boot      Start         End      Blocks   Id  System 
/dev/sdc1            2048    31260671    15631213    c  FAT32 LBA
Warning: Partition 1 does not end on cylinder boundary.

Disk /dev/mapper/VolGroup-lv_root: 48 GB, 48882839040 bytes
255 heads, 63 sectors/track, 5943 cylinders, total 95474295 sectors
Units = sectors of 1 * 512 = 512 bytes

                       Device Boot      Start         End      Blocks   Id  System 
/dev/mapper/VolGroup-lv_root1               0    95485951    47745148   83  Linux 
Warning: Partition 1 does not end on cylinder boundary.

Disk /dev/mapper/VolGroup-lv_home: 48 GB, 48512701440 bytes
255 heads, 63 sectors/track, 5898 cylinders, total 94751370 sectors
Units = sectors of 1 * 512 = 512 bytes

                       Device Boot      Start         End      Blocks   Id  System 
/dev/mapper/VolGroup-lv_home1               0    94765055    47383686   83  Linux 
Warning: Partition 1 does not end on cylinder boundary.

Disk /dev/mapper/VolGroup-lv_swap: 2 GB, 2072770560 bytes
255 heads, 63 sectors/track, 252 cylinders, total 4048380 sectors
Units = sectors of 1 * 512 = 512 bytes

                       Device Boot      Start         End      Blocks   Id  System 
/dev/mapper/VolGroup-lv_swap1               0     4063231     2032191   82  Linux Swap / Solaris 
Warning: Partition 1 does not end on cylinder boundary.
Warning: Unable to open /dev/fd0 read-write (Sistema de ficheros de sólo lectura).  /dev/fd0 has been opened read-only.
Error: /dev/fd0: unrecognised disk label
root@antiX1:/home/hugo# parted -l
Model: ATA WDC WD400BB-00DE (scsi)
Disk /dev/sda: 40,0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End     Size    Type      File system     Flags
 1      1049kB  12,6GB  12,6GB  primary   ext4            boot
 2      12,6GB  24,1GB  11,5GB  primary   ext4
 3      24,1GB  40,0GB  15,9GB  extended
 5      24,1GB  33,6GB  9494MB  logical   ext4
 6      33,6GB  38,4GB  4798MB  logical   ext4
 7      38,4GB  40,0GB  1580MB  logical   linux-swap(v1)
Model: ATA ST3100011A (scsi)
Disk /dev/sdb: 100GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End    Size    Type     File system  Flags
 1      1049kB  525MB  524MB   primary  ext4         boot
 2      525MB   100GB  99,5GB  primary               lvm
Model: TOSHIBA TransMemory (scsi)
Disk /dev/sdc: 16,0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  16,0GB  16,0GB  primary  fat32        lba
Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/VolGroup-lv_root: 48,9GB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0,00B  48,9GB  48,9GB  ext4
Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/VolGroup-lv_home: 48,5GB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0,00B  48,5GB  48,5GB  ext4
Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/VolGroup-lv_swap: 2080MB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system     Flags
 1      0,00B  2080MB  2080MB  linux-swap(v1)
Warning: Unable to open /dev/fd0 read-write (Sistema de ficheros de sólo  
lectura).  /dev/fd0 has been opened read-only.
Error: /dev/fd0: unrecognised disk label                                  

root@antiX

So, there is a:
(1) 40 GB hard disk (sda) in which is antiX
(2) 100 GB hard disk (sdb) in which is Blag
(3) 16 GB pendrive (sdc)

I note the following errors:
(I) In sdb:

Code: Select all

 Device Boot      Start         End      Blocks   Id  System 
/dev/sdb1   *        2048     1026047      514048   83  Linux
Warning: Partition 1 does not end on cylinder boundary.
/dev/sdb2         1026048   195371007    97177185   8e  Linux LVM
Warning: Partition 2 does not end on cylinder boundary.

(II) In sdc:

Code: Select all

Device Boot      Start         End      Blocks   Id  System 
/dev/sdc1            2048    31260671    15631213    c  FAT32 LBA
Warning: Partition 1 does not end on cylinder boundary.

(III) In VolGroup-lv_root1:

Code: Select all

 Device Boot      Start         End      Blocks   Id  System 
/dev/mapper/VolGroup-lv_root1               0    95485951    47745148   83  Linux 
Warning: Partition 1 does not end on cylinder boundary.

(IV) In VolGroup-lv_home1:

Code: Select all

Device Boot      Start         End      Blocks   Id  System 
/dev/mapper/VolGroup-lv_home1               0    94765055    47383686   83  Linux 
Warning: Partition 1 does not end on cylinder boundary.

(V) In VolGroup-lv_swap1:

Code: Select all

                       Device Boot      Start         End      Blocks   Id  System 
/dev/mapper/VolGroup-lv_swap1               0     4063231     2032191   82  Linux Swap / Solaris 
Warning: Partition 1 does not end on cylinder boundary.

(VI) In fd0:

Warning: Unable to open /dev/fd0 read-write (Sistema de ficheros de sólo lectura). /dev/fd0 has been opened read-only.
Error: /dev/fd0: unrecognised disk label

Given those errors (that I can't really fully assess), and in particular the last one (IV) I am about to give up with this Blag installation. I just wait for any opinion regarding this, to proceed.
P.S.: I don't pay much attention to the warnings in sda, since antiX works perfect.

rokytnji · posted: 2013-09-19 02:26

Install Blag to mbr

Device Boot Start End Blocks Id System
/dev/sdb1 * 2048 1026047 514048 83 Linux

is what is making this thread so long. If blag grub had been installed to root"/" . Chainloading GRUB2 would work in AntiX legacy grub.

taigarden · posted: 2013-09-19 02:39

rokytnji wrote:Install Blag to mbr

Device Boot Start End Blocks Id System
/dev/sdb1 * 2048 1026047 514048 83 Linux
is what is making this thread so long. If blag grub had been installed to root"/" . Chainloading GRUB2 would work in AntiX legacy grub.

rokytnji, thank you for your indication, and thank you to all who participated in this thread. Regards.

male · posted: 2013-09-19 09:32

taigarden wrote:I note the following errors:

It looks good! I would not have thought of.

The error message is irrelevant.
They shall be established by the DOS compatibility mode.

The extension of the command

Code: Select all

fdisk -l -c -u

makes the warning disappear. Explanation here (unfortunately only in German):

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.thomas-krenn.com/de/wiki/Partition_1_does_not_end_on_cylinder_boundary_Warnung_unter_fdisk"
linktext was:"http://www.thomas-krenn.com/de/wiki/Par ... nter_fdisk"
====================================

male · posted: 2013-09-19 10:00

I see three options (although I can only partially explain in english):

1. The GRUB boot files must be copied to sdb1
and the mount point must
/boot
loud.
Within lvm may /boot not Presence!

This applies to Grub Legacy!

2. In antiX remove the Grub Legacy and install GRUB2.
This can avoid using LVM (m.W.)

3. remove the lvm on sdb;
Customize installation of Blag and antiX accordingly
(menu.lst, fstab, device.map)

Please! Beware of my English! __{{emoticon}}__

male · posted: 2013-09-19 10:49

To 1.
found >> /boot

Code: Select all

# blkid -c /dev/null -o list

Perhaps the installer has already created Blag...

To manage the lvm there is a GUI

Code: Select all

male@antiX1:~$ apt-cache policy system-config-lvm
system-config-lvm:
  Installiert:           (keine)
  Installationskandidat: 1.1.18-1
  Versionstabelle:
     1.1.18-1 0
        500 http://ftp.cz.debian.org/debian/ testing/main i386 Packages

Good luck! __{{emoticon}}__

taigarden · posted: 2013-09-19 13:51

male: thank you for your three posts. I will do some research guided by your indications, since I am learning, especially regarding lvm, aside that I haven’t done a grub change so far.
BTW I also have to pay attention to my English writing. It´s a long time from my two years living in USA in order to get my Master’s at Georgia Tech. Actually 33 years!

taigarden · posted: 2013-09-20 14:10

This is to inform that finally I obtained the double boot system with antiX and Aptosid 2013-01 Hesperides kde lite, substituting Blag 140k.

Using Gparted from a Pated Magic CD I deactivated the lvm environment in the second hard disk, format it as ext4 with 4 primary partitions (I used swap from the first hard disk) and then started install trials with several Distros.

Semplice Desktop 5 and Trisquel Mini 6.0 refused to install because of a format issue. Semplice gave no further indication, but Trisquel showed: “No root file system is defined”. I checked with the Parted Magic CD, and everything was O.K. For the doubt I marked with a boot flag the first ext4 partition and tried again with the Triquel Mini CD, but I had the same error again.

Then I decided to try with Aptosid. Its installer directly proposed to use the biggest partition in the second hard disk (sdb4), that I accepted, and suggested to install to the MBR, option that I took.

At the first reboot I had the Grub2 menu, which included the antiX entries. The system entered very fast and everything I tried worked as expected. The system as a whole proved to be very responsive. In the second reboot I chose the antiX entry, and I entered in it as expected.

Thanks’ again to all participants in this thread for all your orientations.