Joined: 6-May-2007 Posts: 8963
From: Greensborough, Australia
The only thing I wonder a little bit is what causes this "unknown partition table" message.
I wonder if this is similar to the unknown partition label error in the installer. That is there is an RDSK on there. But it doesn't know what RDSK is. It may expect an APM.
Yeah, it's better to disable the cdrom entries after the installation, if an internet connection is available anyway.
I thought I had but it just wouldn't let it go. I must have apt-get updated four times as well as in the package manager. It also complains about the SF A1 entries but not all the time. It should be logged here somewhere. Something about a size mismatch.
Did you hardcode all this libata.force kernel parameters?
I did! I can remove them. It must have come out from some discussion we had. I ended up with a list. Some ended up on the boot args from the default slb config. Others for module settings.