Let me explain my problem with my poor english:

I have an Antix-installation since some month which was working very well.

The root was installed on /dev/sda8
and /home on /dev/sda9
because there are some other distros on the same pc. A sidux-installation on /dev/sda1 controls the bootloader grub in the MBR. From there Antix was called via chainloader, because it has it's own grub in it's root-partition /dev/sda8.

NOW I unfortunately delete /dev/sda6. As a result, all partitions behind /dev/sda6 change their numeration:

/dev/sda7 is now /dev/sda6
/dev/sda8 (AntiX root) is now /dev/sda7
/dev/sda9 (Antix /home) is now /dev/sda8

So I change the"MBR" grub-menu (in sidux) to call the Antix grub via chainloader, but this doesn't work I get an grub error __{{emoticon}}__ !

As my next trial I change the"MBR" grub-menu to start the Antix direct. Antix starts but only till slim tried to make the automatic login. This fails. Also the trial to login interactively via slim with the correct user and pw fails! If I make a console-login via another shell, then it works, but I can't start X because slim is waiting on the"main screen"

I wanna save my antiX-Installation because there are some useful customizations and some important data which I don't wanna loose.

What do I have to do to rescue my complete antiX-Installation???

thanks in advance for every useful hint.

Michael

wingevil,

Could you post your menu.lst from sidux, and while in sidux in the cli post ls-l /dev/disk/by-uuid, as you know sidux uses uuid, when partitions get changed, the uuid will change and these changes need to be reflected in both the menu.lst and /etc/fstab.
I am going out of town today, but I am sure someone else will chime in to help, I will check later tonite to see if you have already found a resolution, if not, I will try to assist you.

cheers,
oldhoghead

@oldhoghead: I will do that...in ca. 7-8 hours. Now I'm at work and the pc is at home...

You should be able to use the sidux live disc and reinstall grub. You may want to use the antix disc first to reinstall it's grub because of the set up your using. The sidux grub should be able to boot antix directly meaning there should be no need to chainload.

Not sure what sidux uses but antix uses msystem-repair boot. Either distro can use the command line with ; grub-install

okay guys I got it! __{{emoticon}}__

what was the reason for my problem and the solution?

the reason was, that my /home on /dev/sda9 now was numbered on /dev/sda8 and I forgot to change the entry in the fstab. so every login via slim must fail

So I edit the entry in /etc/stab and (not necessary but good for clean concept) I repair the system boot, install the AntiX-grub into the mbr and delete sidux __{{emoticon}}__

Now it's all fine. __{{emoticon}}__

Another thing that might be worth thinking about at least, depending upon what stuff you want to save etc.... is to just boot into antix"Live CD" then rar/zip/tar (Whatever is your preference) your /home partition, and copy anything else that you may need from / and the sib-dirs, then just re-install antiX and let grub pick it all up for you. When you have a fresh install then you can replace whatever needs replacing to bring it back to how you want it..... (Does that make sense?... i hope so) __{{emoticon}}__

On a related note, i've had loads of problems like this, especially when there are multiple distros on one drive.... BUT, the biggest culprit for me, has been the introduction of UUID's. Since many debian distros started using UUID's i've had no end of problems when i install different (new) distros. Sometimes it's just the file format change, sometimes it's other things, but UUID's don't like being mucked around with at all it seems. That's why i always use the old method in Grub and get rid of the UUID's altogether..... makes it a lot simpler process.

Good luck anyway, i hope that you get it sorted out with the minimum of hassle.

wingevil,

Glad you got it sorted out, those pesky uuid's are a pita, I avoid the hassle by keeping sidux on it's own usb hd, mixing it with other distro's only brought headache's.

cheers,
oldhoghead

Using by label might be a better idea than by uuids.