ASUS P8P67 Pro Install Problems [Solved]

[Selexo]

I can't get Sabayon to install on this system. The main thing is when I try to boot USB CD-ROM or USB Flash Drive (tried both) the boot drive loads a few modules but then says Scanning for CD-ROM.. then tries to Mount SDA# or SDB#, # being various numbers.. then tries again fails and says must try something else and asks if I want to drop to a shell... "type shell" and etc..

I think this has something to do with the fact its a EFI bios

or certain modules resetting the USB on load....


Anyone with more experience installing Sabayon on this system would like to hear your input..

I thought about installing Sabayon Linux via a virtual machine on the free-space but then wonder how I would go about getting grub installed to dual boot.

BTW I'm set up on RAID0 if that effect anything..

Trying to install the x64_KDE 5.5 DVD... no luck.

[Selexo]

I still can't install Sabayon 5.5 x64.. I was able to boot Other distros off the DVD drive, now connected to a SATA controller..

When I boot into the Sabayon Linux Live it comes up with a bunch of errors. Where it finally hangs when trying to "Play Music" "OK" lots of things before this fail to start with red "!!" IE: Dbus and Daemons...

When I reboot and start straight into Graphical Installations I get a lot farther. Instead it dies on the login screen Saying "FATAL ERROR in KDM check logs.." Even when I try safe-mode it still dies. Going to try vesa install but not sure if that's going to fix anything.

Like I said I can boot other distros.. IE, Linux MINT, Ubuntu, SESU, in live mode.

Just a update because I have yet to get any reply on this.

[Selexo]

Well I got a new problem... I got everything sorted out with booting off the cd and such.. The new problem is I still can't install sabayon because when it comes to partitioning it is messes up.. I have tried the DAILY BUILD and the 5.5.. both fail on "Sabayon Installer"


I find that my raid volume sits on "/DEV/MD127" I also have to go under Advance Disk-> "Firmware RAID" to see the Disk as Basic Disk doesn't show anything in the installer..

When I try to commit the disk changes it errors out with massive errors... Asks me if I want to Save the report or debug.. when I say SAVE it just dissapears with no message..

Basicly Sabayon can see /DEV/SDA & /DEV/SDB my two drives when I first boot up thats are suppose to be part of my RAID0 array. Its not till after I get into the installer and select Advance Disk that the RAID Array shows up..but under /DEV/MD127 (aka Multi Disk Device)

I was under the impression that with hardware RAID the OS shouldn't be able to see the individual disks.. (update, firmware raid is Fake Raid, or CPU Raid aka, software raid *sigh*...)


Anyways any help on this would be appreaciated..

screenshot
http://img593.imageshack.us/img593/9276/snapshot1k.png

During my troubleshooting I think the installer can't see the partitions correctly... First of all the Disk Utility doesn't see it any partitions at all on the RAID Array once its mounted by the installer... Second the installer itself sees my Windows 7 partitons as Unknow Edtended partitions. I was under the impression that sabayon installer knew more file system types... At least in the Terminal I can see the partition properly in "parted"

[micia]

Hi,
usually the issues that you report in the boot are caused by bad burns, however, since now you sorted them out, let's forget about them.

Did you use the installer to edit the partitions?
If you are using the Gnome daily build, I suggest you to use GParted to handle partitioning rather than the installer partitioner, to launch gparted run in a console:

Code: Select all

gksu gparted


I had always bad experiences with the installer partitioning program, I usually use another program and use the created partitions during the install process.

[Selexo]

I have been trying to install the KDE version.. I have nothing against gnome so I will install off that one instead and install KDE after the fact...

The problem I was having earlier was first because USB was getting reset on the load of the linux modules.. so the USB drive would get bumped off the system.. Didn't matter if I was trying to boot direct off a USB Thumb drive or a USB CD-ROM.. anything on the USB would just blank out and come back (even my usb keyboard lights would refresh).. Sad thing is I installed Windows 7 off USB Thumb drive and didn't experience this issue.. So I was sorely confused by the issue with installing linux off my USB devices on this system.. This doesn't happen on my laptop or older system.. What I think is happening is there are USB 3.0 ports on this board, but linux doesn't see them till it loads more modules.. when this happens its basically shuffles the USB 2.0 and 3.0 and well I loose flash-drive boot somewhere during this and the flashdrive gets remapped somewhere else.

Second problem was because my sata cdrom drive was sitting on the marvel 6gb controller so it was having random read errors on boot.. Wasn't till I moved the drive to another port was things acting better.. I verified the burn and MD5 in windows 7 which passed but out of windows it didn't want to read with 5.5 burn but did with the daily.

As for partitioning I will look into doing so manually.. I just don't have much faith in the installer to be able to properly install if it doesn't know how to manage/execute partitions in the first place.. especially if its somehow suppose to get Grub in order at the end of the install but isn't reading my partitions correctly in the first place. After all the installer doesn't even see my Windows 7 NTFS partitions (listed unknown extended) so I can't expect it to properly execute grub on it for a multi-boot setup. Not sure If I want to risk the aftermath of that without having my Boot Clusters backup in-case it epic fails.

Anyways long reply I know, but just have to express my perspective & concerns on the whole issue; and now current expectations of Sabayon Installer on this system.

[Fitzcarraldo]

After all the installer doesn't even see my Windows 7 NTFS partitions (listed unknown extended) so I can't expect it to properly execute grub on it for a multi-boot setup.

Even if the built-in partition editor in the Installer does not recognise your NTFS partitions, that does not mean you will have a problem. I had no trouble installing SL on my main laptop with two NTFS partitions. I used GParted to create the Linux partitions, and then I ran the SL Installer. As GParted is not on the SL KDE LiveDVD, I used the SL GNOME LiveDVD just to run GParted. A long-winded process just to create and format Linux partitions. Then I booted the SL KDE LiveDVD and ran the Installer. When you get to the Installer page 'Which type of installation would you like?', select 'Create Custom Layout' and tick 'Review and modify partitioning layout'. You then specify, name and reformat the Linux partitions. When the Installer runs gub-mkconfig to create grub.cfg, it runs /etc/grub.d/30_os-prober, which does find the NTFS partitions.

[Selexo]

Oh wow.. I will need to study Sabayon some more before installing.. Turns out this board does have BIOS raid but its not true Hardware raid as it is loaded through firmware.. So that is why on boot Sabayon sees SDA & SDB under /DEV.. The device mapper doesn't see the raid volume till its mapped by the Installer...

This could pose a problem for grub later because of this

http://en.gentoo-wiki.com/wiki/RAID/NVRAID_with_dmraid#Building_the_Kernel

Do not run grub-install! It will not work properly, and will probably detect the sda1, etc. instead of your actual raid. Make also sure not to start grub inside of an chroot enviroment like you propably do if you install from the Gentoo LiveCD and do it like described in the installation manual of gentoo.org. It doesn't know about /dev/mapper so you would get some errors with grub. In this case just jump into another terminal with ALT+F2. Start grub and make sure that it's pointing to /dev/null as a device map.

I am not sure if Sabayon installer will properly execute grub on the right device ie: /DEV/SDA1 where it should be /DEV/MD127

I'm going to simulate this In a VM and see if this boots software raid before installing, as that's how Sabayon is treating my system now; and to see if the installer is going to attempt to install grub on SDA1 or MD127..

Had I know before hand what I had, I would of probably avoided a RAID setup. Learn something new everyday I suppose, I'm not afraid of something new, just wish I was better prepared for this.

I just hope Sabayon is loading raid via Kernal instead of modules as this could make this easier.
http://en.gentoo-wiki.com/wiki/RAID/Onboard#Configure_kernel

I am only using Gentoo information as a primer for Sabayon install.. I know things are not done the same 100% between Sabayon and Gentoo.. but because Sabayon may inherited some of the hiccups of gentoo I would rather be prepared for this situation. Not sure how much has changed with Grub2 so this may be outdated..

[greendave8]

Hi,

Just yesterday I installed Sabayon 5.5 on the same Motherboard with i7 2600k and 4gb of ram. I installed from a USB stick, with no hitches whatsoever. I then did the updates...

Therefore I think your problem maybe a faulty piece of hardware or bad download. The system is compatible and does work...

gd8

[Selexo]

Ok well I have Sabayon installed.. The latest 7 is able to boot even off my USB cdrom with no issue thanks to the 3.0 kernel? Anyways I can install it now but I can't get grub to stick to the MBR nor the Boot partition itself.

RAID0: md127
MD127p1 100MB - Boot Partition belongs to windows 7
MD127p2 900GB - Windows 7
MD127p3 500MB - Linux Boot
MD127p4 20GB - Sabayon Install In a LVM volume.

Grub doesn't seem to stick or write to any MBR because once I reboot I am presented with the windows Boot Loader.. So I thought I could just have windows boot loader boot my grub partition directly so on the second install I told it to place grub on MD127p3, and then copied the boot record with DD, so the MBR could be setup under windows boot manager to do its magic.. Well it didn't work. I found that when I DD the boot partition then preceded to view it in a HEX it was just all "00" If I DD the MBR I would see the windows boot loader info.. Anyone experience this?

[Selexo]

Well after many installs of different version of Sabayon (never giving up hope that it would be fixed someday); downloading daily's snapshots of Sabayon installing Linux to this system periodicity.. Version 10 was finally able boot, and Grub was successfully installed on the partition. No other linux distro, (ubuntu, mint) was able to ever boot off my firmware RAID0 with windows 7 already on it, and properly boot or much less set up grub on my MBR. It was like when it came time for grub to install on the MBR it never produced a error saying Grub failed.. but then on reboot the windows boot loader would be present. (it was like my MBR was write protected or something) I even tried to get the Windows Boot loader to chain-load the grub boot partition but that even failed, because grub never got flagged on the any partition.

But with Sabayon 10 (( *hallelujah* )) on reboot I was presented with the grub boot loader with Windows 7 sitting on MD127p1 and Grub properly installed on the boot partition of the drive! =) yes thank you.. It only took a couple years (almost) but wow.. I'm glad to be typing from linux again and get to dabble and play in this environment again.

I'm not all sure what has changed in the installer but the installer was able to detect my raid volumes under basic install (didn't have to go under advance). Another noticeable change during the installer was that all my volumes seems to require reinitialized and re-scanned because of mount point changes.

Thanks for whatever fixes were done to manage this install on this EFI, GPT, RAID0 system environment. I can finally marked is solved!..