| Author |
Message |
|
|
Post subject: Installing 2008.2 to fix bootloader problem
 Posted: Aug 12, 2008 - 03:14 AM
|
|
Joined: Mar 24, 2008
Posts: 143
Location: Oregon
Status: Offline
|
|
I have recently tried installing Sabayon 3.5. I seems like a good distro, but it's boot loader broke the boot menu for opensuse and sidux! So I installed Xubuntu over Sabayon, only because its installer has been more reliable. so after installing Xubuntu. it sees sidux but it doesn't load properly.
what is the best way to fix the grub so sidux is the main bootloader? I have three hdds on this test box and I can install sidux 2008.2 where the 2008.1 is now. The sidux bootloader is one of the best that I've used.
I really don't care for Xubuntu and would rather use sidux or even opensuse instead.
How should I correct this? |
|
|
| |
|
|
|
 |
|
|
|
Post subject:
Posted: Aug 12, 2008 - 03:26 AM
|
|
Joined: Mar 24, 2008
Posts: 143
Location: Oregon
Status: Offline
|
|
| ... rebooted again and this time I was able to get into sidux, but in the details it had trouble checking files and I had to do a CTRL+D to get in. What causes that? How di I correct that? |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Aug 12, 2008 - 06:20 AM
|
|
Joined: Feb 24, 2007
Posts: 675
Location: Berlin, Germany
Status: Offline
|
|
Hi vinoman,
the CTRL+D issue looks suspiously like a broken filesystem check after the freshest of your installs.
The Sabayon-Installer should have altered the UUID of one (or more?) of your partitions, that is in the /etc/fstab file of your sidux-installation. Comment the partition out (#) or change the UUID in the file to the newest id with comparing the output of ls -l /dev/disk/by-uuid and the id in the fstab.
If you successfully booted your sidux run the command grub-install --no-floppy --recheck /dev/sda to have the bootloader install in the mbr on your first hard drive. Check carefully if that is what you need and want.
cheers Micha |
_________________
http://sidux.com/PNphpBB2-viewtopic-t-2403.html
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Aug 12, 2008 - 10:42 AM
|
|
Joined: Aug 24, 2007
Posts: 472
Location: Ljubljana
Status: Offline
|
|
|
|
|
|
|
|
|
Post subject:
Posted: Aug 12, 2008 - 11:33 AM
|
|
Joined: Mar 24, 2008
Posts: 143
Location: Oregon
Status: Offline
|
|
|
michaaa62 wrote:
Hi vinoman,
the CTRL+D issue looks suspiously like a broken filesystem check after the freshest of your installs.
The Sabayon-Installer should have altered the UUID of one (or more?) of your partitions, that is in the /etc/fstab file of your sidux-installation. Comment the partition out (#) or change the UUID in the file to the newest id with comparing the output of ls -l /dev/disk/by-uuid and the id in the fstab.
If you successfully booted your sidux run the command grub-install --no-floppy --recheck /dev/sda to have the bootloader install in the mbr on your first hard drive. Check carefully if that is what you need and want.
cheers Micha
here's my fstab:
# <filesystem> <mountpoint> <type> <options> <dump> <pass>
# automatically added, MAXTOR_STM332062-6QF1BRMG-part1, /dev/sdc1
UUID=8a113203-943b-4df1-9afe-0f18f460ae10 / ext3 defaults,noatime,errors=remount-ro 0 1
# automatically added, ST340014A-5JX2V8ZC-part1, /dev/sda1
UUID=6a237063-a57e-4da9-9015-0ed395a08c18 /media/disk1part1 ext3 auto,users,exec,noatime 0 2
# automatically added, ST340014A-5JX2V8ZC-part5, /dev/sda5
UUID=dd2aa548-1db1-4cd2-9f01-2c5215fd31d5 none swap sw 0 0
# automatically added, HDS728040PLAT20-PFD100S1RU6WPG-part1
#/dev/sdb1 /media/disk2part1 ufs auto,users,exec 0 2
# automatically added, MAXTOR_STM332062-6QF1BRMG-part3, /dev/sdc3, LABEL=swap
UUID=9644b726-00f5-476a-94be-8bf5767440fd none swap sw 0 0
# automatically added, SONY_DVD_RW_AW-Q170A
/dev/cdrom /media/cdrom udf,iso9660 user,noauto 0 0
# automatically added, CDU5211
/dev/cdrom1 /media/cdrom1 udf,iso9660 user,noauto 0 0
# automatically added
/dev/fd0 /media/fd0 auto rw,user,noauto 0 0
# temporary filesystem in virtual memory
#tmpfs /tmp tmpfs defaults 0 0
Should I rem out the first listing? |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Aug 12, 2008 - 11:35 AM
|
|
Joined: Nov 30, 2006
Posts: 1010
Location: Nimritz / Thüringen
Status: Offline
|
|
Only your fstab doesn't help us.
Also you should use the code-tags!
And now we need the output of
ls -al /dev/disk/by-uuid |
_________________
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Aug 12, 2008 - 11:36 AM
|
|
Joined: Dec 02, 2006
Posts: 1703
Location: Germany / NRW
Status: Offline
|
|
now execute:
"blkid -L"
and compare the UUIDs |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Aug 12, 2008 - 12:28 PM
|
|
Joined: Mar 24, 2008
Posts: 143
Location: Oregon
Status: Offline
|
|
|
towo| wrote:
Only your fstab doesn't help us.
Also you should use the code-tags!
And now we need the output of
ls -al /dev/disk/by-uuid
here it is:
davek@siduxbox:~$ ls -al /dev/disk/by-uuid
total 0
drwxr-xr-x 2 root root 160 2008-08-11 21:25 .
drwxr-xr-x 6 root root 120 2008-08-11 21:25 ..
lrwxrwxrwx 1 root root 10 2008-08-11 21:25 8a113203-943b-4df1-9afe-0f18f460ae10 -> ../../sdc1
lrwxrwxrwx 1 root root 10 2008-08-11 21:25 9644b726-00f5-476a-94be-8bf5767440fd -> ../../sdc3
lrwxrwxrwx 1 root root 10 2008-08-11 21:25 b8a6f3a6-fe9c-44b4-b3f3-8121fe445c26 -> ../../sdb2
lrwxrwxrwx 1 root root 10 2008-08-11 21:25 c0f991c9-1a16-4fe2-b824-ecac2448d5f7 -> ../../sdb1
lrwxrwxrwx 1 root root 10 2008-08-11 21:25 c29ba650-3951-4af1-86da-95b0703adb04 -> ../../sda5
lrwxrwxrwx 1 root root 10 2008-08-11 21:25 c87d6332-1942-47ef-94a5-250b602f3b60 -> ../../sda1
davek@siduxbox:~$ |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Aug 12, 2008 - 12:32 PM
|
|
Joined: Nov 30, 2006
Posts: 1010
Location: Nimritz / Thüringen
Status: Offline
|
|
The UUID for
sda1 and sda5
does not match. |
_________________
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Aug 12, 2008 - 12:59 PM
|
|
Joined: Mar 24, 2008
Posts: 143
Location: Oregon
Status: Offline
|
|
|
towo| wrote:
The UUID for
sda1 and sda5
does not match.
how do I correct this? |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Aug 12, 2008 - 01:05 PM
|
|
Joined: Mar 24, 2008
Posts: 143
Location: Oregon
Status: Offline
|
|
|
|
|
|
|
|
|
Post subject:
Posted: Aug 12, 2008 - 01:49 PM
|
|
Joined: Nov 30, 2006
Posts: 1010
Location: Nimritz / Thüringen
Status: Offline
|
|
1st, you have to edit your fstab and correct the wrong uuid there.
Then sidux should boot. |
_________________
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Aug 12, 2008 - 02:05 PM
|
|
Joined: Mar 24, 2008
Posts: 143
Location: Oregon
Status: Offline
|
|
|
towo| wrote:
1st, you have to edit your fstab and correct the wrong uuid there.
Then sidux should boot.
Do I rem out one of the lines? How do I correct this?
What is the wrong uuid? |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Aug 12, 2008 - 02:08 PM
|
|
Joined: Nov 30, 2006
Posts: 1010
Location: Nimritz / Thüringen
Status: Offline
|
|
| Put the correct uuid in place of the wrong for the 2 entrys. |
_________________
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Aug 12, 2008 - 03:28 PM
|
|
Joined: Mar 24, 2008
Posts: 143
Location: Oregon
Status: Offline
|
|
|
towo| wrote:
Put the correct uuid in place of the wrong for the 2 entrys.
What are the correct ones? |
|
|
| |
|
|
|
|
|
|
