I found other people with similar problems:

https://answers.launchpad.net/ubuntu/+question/4147

http://ubuntuforums.org/showthread.php?t=414903&highlight=ALERT%21+%2Fdev%2Fdisk%2Fby-uuid%2F
( have an workaround )

This weekend I've trieed again to boot Ubuntu Feisty. The results:

1) My first installation was on the partition /dev/hda8 (logical partition), 
and on this weekend i've tried on /dev/hda1 (primary partition) with GRUB 
loaded on the MBR.
- Results: the same errors as registered above.  
(https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/107976/comments/3)


2) Second attempt: I've installed again in /dev/hda1, but GRUB was entirely 
loaded in the boot sector of /dev/hda1 (hd0,0). In MBR was installed an boot 
selector (XOSL).  I would test the workaround described in 
http://ubuntuforums.org/showthread.php?t=414903&highlight=ALERT%21+%2Fdev%2Fdisk%2Fby-uuid%2F
  

- Results: My computer booted with Feisty Fawn. I've seen some error messages, 
the boot process was too long, but finally i could see Feisty running on my 
computer.
I don't undestand why they have booted. i don't have made the workaround from 
the Ubuntu forum. The only fifferent thing was GRUB entirely loaded in boot 
sector.

All the partitions of my 2 disks was corrected and named hda (some people 
report that Feisty names all partitions with "sda")
The sound is ok.  Video with resolution 1280x1280. I've changed to 1024x768 and 
then the image occupied only part of the screen. Then i've runned 
"dpkg-reconfigure xserver-xorg" and choosed SIS drive. Now the video is also ok.

I hope that Ubuntu developers pay some attention for these problems
(bugs?) with SIS chipset. At the moment I can't trust the system (firs
successful boot after 10 days, long boot time and and some error
messages -> my nest job).

I hope the information above can help others, despite my bad english.
Please excuse me for that.

-- 
feisty crashes on boot, "/" system disk does not exist
https://bugs.launchpad.net/bugs/107976
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to