Getting antiX 13 working

Slaizer · posted: 2013-06-27 18:14

Hi,

I downloaded the distro: antix-13_x64-full.iso image. When I am during the install process it works just fine. When I am booting it up it reads: Target filesystem doesn't have requested /sbin/init. No init found. Try passing init=bootarg; and: /bin/sh:can't access tty; job control turned off.

Anyone here who might help a fellow out?

Thanks all

BitJam · posted: 2013-06-27 18:40

It seems the Grub entry is pointing to the wrong root filesystem. This would explain the errors you got. You need to boot with the LiveCD/USB in order to diagnose and fix this problem. If there are not a lot of partitions on this machine I suggest you use the"F4 Options" menu -->"mount all" option in the bootloader to mount all partitions under /media.

You need to do two things: (1) find out which partition antiX was installed to, and (2) fix the /boot/grub/menu.lst file on that partition.

If you used the"mount all" option then you should be able to find the menu.lst file with this command:

Code: Select all

$ ls /media/*/boot/grub/menu.lst

If you can find menu.lst then please post the contents here (or on pastebin) along with the output of the command above and the output of:

Code: Select all

$ sudo blkid

This should be enough for someone to tell you how to edit menu.lst to get antiX to boot.

It is possible that something went horribly wrong with the install and you will have to do it again.

rokytnji · posted: 2013-06-27 22:41

Also, to make sure all dogs and cats are in a row.

Make sure bios is telling the right drive to boot first. Believe it or not. That screwed with my head till I checked and fixed that.

Slaizer · posted: 2013-06-28 12:20

My installation process is like this: installing media-->chose wheezy--->install on sdd (my 80Gb hard drive which don't have anything installed on it)---> Chose not to install GRUB for antiX and Windows (should I choose this option?).

Well that is about it, and it doesn't work. Should I install the Grub for antiX and which system boot disk in that case, sda is the first one.

I understand kind of how to change in the boot/grub/menu.lst, but I want to know if to install this GRUB and where first.

I have another operating system on my 120GB drive, that one is my dev/sdc. My first drive is /dev/sda, if this helps.

Thanks for answering, and hope my reply can make you guys understand my situation better.

rokytnji · posted: 2013-06-28 12:41

>install on sdd (my 80Gb hard drive which don't have anything installed on it)

Without the info bitjam asked for. It is still hard to advise you.

My question is is the 80 gig drive the first in bios boot order and was grub installed to mbr of the 80 gig drive with the defaults used in the installer"use initrd, it is recommended" box checked?

It sounds like you have dual ide hard drives and are trying to dual boot Windows on one hard drive and AntiX on another hard drive. I hope I got that right.
I do this also, (quad boot on 2 drives but no Windows on any drive) but without the info Bitjam requested. It is hard to advise you like I said.

Slaizer · posted: 2013-06-28 14:16

bitjam,

the first (1), the OS is installed on the sdd disk, and (2), the GRUB, I did not install it. I have since before Opensuse 12.3 KDE installed on my sdc disk, and GRUB has been working just fine. I don't know the boot-order on these disks. This is the output from blkid: Didn't get any answer from the ls /media/*/boot/grub/menu.lst command.

Best regards

dolphin_oracle · posted: 2013-06-28 14:43

I'm confused. So you booted the live media and installed to /dev/sdd correct? Your blkid shows /dev/sdd1 as an ntfs drive with a label of"Stockholm". Is that the drive you installed to?

Slaizer · posted: 2013-06-28 14:52

I am also kind of confused. I use Gparted when I looked at the drives on antiX, and it showed the 80GB drive as sdd, the drive also has antiX files installed on this drive. When I am using Fedora 18 operating system it shows /dev/sdb/, that the 80GB is located at. (Sorry, I am using Fedora as the other OS, not opensuse KDE 12.3). It is showing the 120GB as the disk containing Fedora, as dev/sda. Well this is the output from my disks when I took a look with the Fedora disk analyser. And exactly like you said, dolphin, my sdd is my STOCKHOLM 1TB disk.

Hope this helps.

dolphin_oracle · posted: 2013-06-28 15:03

Sometimes things get screwy with that many drives and operating systems.

hmm...so you are using the fedora bootloader, which I assume is grub2. You'll need to configure the grub2 line to point to the partition that fedora thinks its located. so if /dev/sdb1 is the 80gb antix partition, point the grub2 entry that way.

this is the grub-legacy entry that would match sdb1 being the antix partition. I don't know how it translates to grub2.

if you were using grub-legacy and the 64bit version of antix:

Code: Select all

title  antiX at sdb1, kernel 3.7.10-antix.4-amd64-smp
root   (hd1,0)
kernel /boot/vmlinuz-3.7.10-antix.4-amd64-smp root=/dev/sdb1  quiet 
initrd /boot/initrd.img-3.7.10-antix.4-amd64-smp
boot

Slaizer · posted: 2013-06-28 15:12

Ok. I have some progress here. I can see Debian/GNU (antiX) in the boot menu, that I always have been seeing. But now it doesn't return any error message, it is just blank. And the disks are in the right boot order, first 120GB IDE drive (Fedora), then 80GB IDE drive (antiX9), after that the two sata drives.

That one didn't work, dolphin. Is my problem here that GRUB2 doesn't point the disks right?

Appreciate your time.

dolphin_oracle · posted: 2013-06-28 15:36

that is my guess. either that or it can't find the boot images for some reason. I honestly don't know much about grub2.

you could try reinstalling antix on the drive, this time selecting install grub to root partition. then you could change your fedora boot manager to simply chainload to the antix grub, which would then finish booting antix.

i'm setting up a similar scenario right now to test.

Alanarchy · posted: 2013-06-28 15:48

man grub is very helpful.

dolphin_oracle · posted: 2013-06-28 16:28

Ok, I just setup a scenario whereby I installed antix to a second parition and chainloaded the bootloader (grub). worked fine, although there are a couple of caveats.

when you install antix and it asks to install grub, unmark the dot that says"mbr". it will then install to the root drive for the current installation. so if you install to sdb1, then the grub system will be on sdb1. unfortuantely on my test system menu.lst was not generated. you will need to modify this on your own, this as plain/jane starter

assuming 64bit

Code: Select all

timeout 5
color cyan/blue white/blue
foreground ffffff
background 0639a1

title  antiX at sdb1, kernel 3.7.10-antix.4-amd64-smp
kernel /boot/vmlinuz-3.7.10-antix.4-amd64-smp root=/dev/sdb1  quiet
initrd /boot/initrd.img-3.7.10-antix.4-amd64-smp
boot
[/boot]

then you can set grub2 to chain load to sdb1 however one does that.

Slaizer · posted: 2013-06-30 15:58

I have actually got antiX working through using Super Grub2 Disk. But I could just install Grub2 with the MBR on my sdd disk. My fedora install which is on my sdc disk, I could not find to install Grub2 and the MBR.

On my antiX my disks sorts my disk as follows
sdc, Fedora
sdd, antiX

And on Fedora OS
sda, Fedora
sdb, antiX

This is kind of confusing, why do they mix the disk order?

This is my antiX menu.lst, Can i write a entry on this script to my Fedora 18 OS?

fatmac · posted: 2013-07-07 19:08

Basically in Linux :-
First HDD First partition = /dev/sda1 Second partition = /dev/sda2
Second HDD First partition = /dev/sdb1 Second partition = /dev/sdb2
Third HDD First partition = /dev/sdc1 Second partition = /dev/sdc2
Fourth HDD First partition = /dev/sdd1 Second partition = /dev/sdd2

Then for Grub (legacy):-
First HDD First partition = hd0,0 Second partition = hd0,1
Second HDD First partition = hd1,0 Second partition = hd1,1
Third HDD First partition = hd2,0 Second partition = hd2,1
Fourth HDD First partition = hd3,0 Second partition = hd3,1

Hope this helps.