Sabayon 3.4 loop2b install: cannot initialise swap

[brodders]

Hi,

Adding Sabayon as a 2nd OS on a box with Vector and Sidux.

The HD (80g Seagate) was partitioned by Sidux using gparted and seems happy - ext3 in use everywhere (each distro has it's own partition, common swap and a data store area).

Attempted Sab 3.4 32bit loop2b install x5 now. Consistently cashes once setup info taken and installer starts it's main work.

Thows an error swaping it cannot initialise swap.

Tried hard reboots (so partition table current), erase and re-buld swap partition by Sabayon, error report persists.

There is a second HD with a swap partition. Would that interfere with the swap initialisation?

That drive is not mentioned in the manual partitoner.... so I assume it does NOT figure with this problem.

Sidux did not mind the swap neither did Vector. Hm.

[WarraWarra]

Not sure but there is the "update installer" icon on the desktop if doing it with "no music" boot menu option .
Should not make a difference though. I had it also somehow losing access to the disk and after restart it works but using installer and it' s partition option instead of the partition on the desktop.
Then it worked for me.
Swap is a general space so 1 should be enough as long as it is cleared every time but this should not be serious problem even if not cleared. Swap is same as windows pagefile.sys scratch pad.

Someone else here had to manually change the partitions using the desktop partitio manager then reboot and run install . This seemed to work.

If you try this again and it gives a errors go to terminal / console and as root "dmesg" and copy the last part that looks like it can have the bug listed, possibly last 4 to 10 lines.

Also if you can make sure the torrent file is propper , run md5sum on the iso file and or use the "force-re-check" option in the torrent program to verify if the iso is good.
Hope this helps.

[WarraWarra]

Hi,

There is a second HD with a swap partition. Would that interfere with the swap initialisation?

That drive is not mentioned in the manual partitoner.... so I assume it does NOT figure with this problem.

Sidux did not mind the swap neither did Vector. Hm.

Might also try and unplug the 2nd hd if it does not list it .

You never know , might want to try some MBR master boot record repair on 2nd hd as it should list it if the MBR is good / stable , unless it is the new solaris disk system the 128bit one not sure but all else is supported even OSX disk's.

[nemesis]

I've noticed I get this problem when I save something in the live environment such as a downloaded file. I think it's cause it's saving it to swap if you aren't using existence.

[totedati]

Hi,
That drive is not mentioned in the manual partitoner.... so I assume it does NOT figure with this problem.

i do not understand ... you can boot in livedvd ? Here what tell to you a command like:

Code: Select all

cat /proc/partitions
major minor  #blocks  name

   8     0  117220824 sda
   8     1   10265503 sda1
   8     2   20531070 sda2
   8     3   63962797 sda3
   8     5    5245191 sda5
   8     6    2096451 sda6
   8     7    2096451 sda7
   8     8    4192933 sda8
   8     9    4192933 sda9
   8    10    2096451 sda10
   8    11    2538238 sda11
   8    16  117220824 sdb
   8    17   10265503 sdb1
   8    18   20531070 sdb2
   8    19   52645005 sdb3
   8    21    5245191 sdb5
   8    22    3148708 sdb6
   8    23    3148708 sdb7
   8    24    5245191 sdb8
   8    25    5245191 sdb9
   8    26   10265503 sdb10
   8    27    1477948 sdb11
   8    32  390711384 sdc
   8    33  185197288 sdc1
   8    34  205511512 sdc2

you can see all hdd devices? if is true then you problem is in other part of install process ...

if you can work in livedvd sabayon, and have a internet acces you first move should be to update the anaconda installer, select "update installer" icon and run it ... then you always run gparted first to see how you drives and partitions are layed-out and recognised. Then you can 'manual partition' first, and set a diferent name for every partition to not confuse where you will put the new sistem. Here you need to check if all disk can be see also. Finally check all you settings again, apply the changes, maybe make a partition table backup so that you can revert what you are doing, you should remember now that all you setting still can be reverted back if you make a mistake partitions can be restored, you are in livedvd and no hdd partition is mounted. Here a command like:

Code: Select all

sfdisk -d /dev/sda > sda_backup
sfdisk -d /dev/sdb > sdb_backup
sfdisk -d /dev/sdc > sdc_backup

is a good move for me also . if something go wrong in my endless cycle of sabayon fresh updates, i just do a

Code: Select all

sfdisk /dev/sda < sda_backup
sfdisk /dev/sdb < sdb_backup
sfdisk /dev/sdc < sdc_backup

and all my pain are gone ... When all is done quit from parted and run the installer, in partition phase just set the path's and check again you setup.

For the swap problem ... when you begin the instalation be sure that swap partition is unmounted. If is already one and in livedvd phase is detected and mounted you need to unmount it. I suspect that this is the problem with

Code: Select all

swaping it cannot initialise swap

error message. For example just do a

Code: Select all

swapon -s
Filename                                Type            Size    Used    Priority
/dev/sda7                               partition       2096440 77304   -1

command to see if is some swap partition mounted, and then an

Code: Select all

swapoff -v /dev/sda7

.
This is working for my system )

[WarraWarra]

I have also seen that when adding files to the live dvd envrm. say for ndiswrapper win drivers + doing a few updates and merging some extra driver related stuff the memory becomes full and then it locks up.

I have 2gb ram so this is a bit hard to swallow.

Might be the same for the partition problem too many stuff done and memory fills up ?

Try to make the partitons the way you want them , then reboot and start installer + manual partition options and just set root swap etc + format and install or 2nd time if this fails "no format" just install after setting root swap options in partition part of installer.

Had to do it once like this.

[totedati]

I have also seen that when adding files to the live dvd envrm. say for ndiswrapper win drivers + doing a few updates and merging some extra driver related stuff the memory becomes full and then it locks up.

I have 2gb ram so this is a bit hard to swallow

with 2 GiB of ram !? And i supose no swap ...

Always help to use your spare swap's partitions in a sabayon livedvd environment, if you know you have it. Just 'activate' it with a

Code: Select all

swapon -v /dev/xxx

command if is not already used ... From my experience in Sabayon LiveDVD v3.2 and v3.3 was detected and mounted. And i stomp over it cannot initialise swap error after partition step of instalation ... This is more true when you try to emerge something in it. Even if software package has only some MiB, if sourcecode is something picky can eat a lot of memory ....