Hi,

Yesterday I finally succeeded installing M12 in Virtualbox, so today I tried installing the Antix Core M12 and failed three times. Then I had a look at what was mounted (because there were hundreds lines saying"can't copy blablabla") and the device sda1 was not mounted. I mounted it on /mnt and restarted the cli-installer script, then it installed successfully.

I am about to reboot to the new install to discover it.

Have other people met with a similar issue with the core version, be it in a real or a virtual machine ? Is it possible that something has been forgotten in the install script ?

PS: It does not reboot, but stalls with two lines saying:
/usr/local/lib/antiX/antiX-get-param.sh: line 17: /usr/bin/gettext: Input/output error

This happens just after deactivating swap and umounting local file systems.

I have to force the shutdown and try to reboot anyhow. (typing"q" in front of a ':' which was at the bottom left, and hit Enter did the trick).

PS-2 : there is a full tree directory in /root which is almost the same as in / : there might be a mistake somewhere ? I have done a few diff on several directories : diff /root/bin /bin and same with /usr and others, there are definitely differences, but : what are these directories doing there ?

PS-3 : here is a screenshot :

If I were you I would install again (It only takes a few minutes).
If you have your partition(s) set up already in VB, then all you have to do is correctly point the installer to the partition you want to install to. If you get this wrong, then the installer will stil try to install, but will not be able to.

eg type sda1.

When the script finishes, it promts to use

reboot.sh

(This will shut it down cleanly, reboot will not).

Also do not save the contents of home. Best to add them later. And the answer to the Is this a remastered version is the default N (unless of course it is a snapshot).

I just ran it in VB with no issues. My guess is that the partitions have not been set properly.

Yes I have had the problem of cannot copy before...
On a actual install I think it is from the cdrom drive not reading the cd correctly. As soon as I seen those messages run across the screen I hit control + C and reboot. The reboot always fixes the issue and installation will work fine.

I have had it on a Vbox install, again reboot and it fixed itself.

Hi,

I suppressed the install and I am now reinstalling.

I use the puel extensions, therefor is is as if I had the Vbox non free edition (in Archlinux it is the latest). I have booted from the ISO (as I do usually). I have booted to the first entry, cli install, therefore the new"hard drive" file has not been partitioned yet, and as before I will let it create a partition table, and a ext3 partition using the whole space. Then I will tell it to use sda1 : which is what I have done before.

This is where up to now it has blocked.

I am sure the iso is good, I had downloaded it with wget, and I just checked the md5sum additionnally.

Do I have to worry about having the sda1 mounted, or not ?

I seems that after partitioning with cfdisk the installer formats again : should I skip the formatting step in cfdisk therefore ?

Ok, here is what the slaughter looks like here:



If you don't know why the partition (just created, with the integrated cfdisk) is not mounted before the installar starts to copy, I don't know either.

Would you have any other clues about your setup in vbox ?

Shouldn't matter. However IMO it is best to set up the vb pertition(s) before running antiX-core eg by using antiX-base or full (live) and via gparted.

come to think of it, the only times i had the failed to copy problem was after partitioning the drive with cfdisk. after a reboot might have solved it because i did not repartition. maybe the script is to ambitious and cfdisk has not yet finished writing the changes to the drive?

maybe i will take a look while writing the antix gui cli installer.

Dave wrote:come to think of it, the only times i had the failed to copy problem was after partitioning the drive with cfdisk. after a reboot might have solved it because i did not repartition. maybe the script is to ambitious and cfdisk has not yet finished writing the changes to the drive?

If you are right perhaps after the partioning the script should rather as for a reboot prior to continuing ?

maybe i will take a look while writing the antix gui cli installer.

Thank you.

Hi,

The try before last I have used cfdisk, then tried to use cli-installer, then again a row of errors can't copy, then I tried to mount the partition freshly created by what looks like a cfdisk tool.

Here is what I got:




Ok, fun I thought !

I redid a new one. Then paritionned with cfdisk then rebooted. Then I tried to mount it got the same result as above : I did a"mkfs.ext4" on the partition and then I mounted it to /media. Then I launched the installer. Then install went well.

So it seems as if cfdisk does not build a valid partition.

If you do the same as above, (run cfdisk then cli-installer) so that it fails again, at that point reboot with a live copy of antiX full, and run gparted, what does it show the partitions as being?
if it is valid was it the format you were looking for?
if it was not valid what format were you attempting to make i assume ext.4 from your previous post)?

Yes, you assumed right. I found the idea of booting another antix to look at the partition too complicated for what I needed. I can confirm cfdisk created the partition table (msdos), created a partition, but was unable to format it to a partition type.

What is the shell used in antiX core ? Isn't it one of these buggy busybox shells ? I ask because I could not use tab for completion ?

ok, so there was no format, thank you.

It is bash I believe, not sure, and I use core for almost everything and tab completion works fine for me. So I am unsure why it does not for you.

I have the same problem here.
First cfdisk asked for description of the disk type. I didn't choose msdos but gpt (?).
Than I tried to format the disk with ext3 -- didn't work.
Than I tried ext2 -- yes, worked.
Now the copy of the .iso (I used antiX-base) went smoothly through.

I tried both grub in the MBR and in the filesystem. When I did it once, the disk space shown in VB was 1,3 GB. After the second attempt it was 2,3 GB. So, nothing was deleted in contrast to the messages during the installation.

I shut the VM down and restarted it.
Now I always get the message : no bootable media found.
No matter whether I installed grub in MBR or not.

And yes, I flagged the sda1 bootable in cfdisk.

as suggested, I started the antiX-base.iso in VB and searched for the GPArted program in the fluxbox menu . The deletion and creation of the sda1 partition worked smoothly.
Then I stopped the virtual machine, rebooted the .iso and used the cli-installer. I skipped cfdisk and the installation was sucessful -- now AntiX booted from the virtual disk.

btw -- VB runs on a 64-bit machine in a 64-bit version. Maybe this causes the problems of cfdisk (?).

I'm away from the machine I use for VB right now but I run antiX (plus several other distro's) on it without trouble. As I remember it, you open VB, select new and follow the bouncing ball to do a basic setup:: name (say: antiX-test), OS (Linux - Debian, I guess although I just chose the kernel), RAM and the amount of disk space. I always create a new disk, usually allow 10Gb and check the dynamic box.

I always use a live disk. If it is one I have downloaded from a systems website, I have the .iso's to my hard disk (distro's off magazines -LXF- are slightly different). Once you've done this, double click on antiX-test, a Wizard will open up. and suggest that you boot from the CD drive. Click on 'Browse', find the directory holding your .iso & take it from there.

If you are using a live image, you can either run that & take snapshots as you go or you can install it. When the cfdisk screen comes up, I usually choose ext3 which seems to work ok. If anything goes wrong, I close the virtual machine, destroy it and start again.

Hope this helps

dmk