feisty crashes on boot, "/" system disk does not exist

[georgielove]

Binary package hint: linux-source-2.6.20

First of all i will describe my sistem:
Pentium IV 1.5 Mhz on a SiS 645DX/961B (NS70-EL from DFI) chipset board, with two ATA Hard Disk. I am trying to install feisty, and with the feisty livecd, hard disks are partitioned like this:

First Hard Disk 40 gb (Master of IDE1)
hda1-> Windows XP (30 gb). I want to keep it aswell.
hda2-> / (8.5 gb approx)
hda3-> swap (1.5 gb approx)

Second Hard Disk 120 gb (Slave of IDE1)
hdb-> /home (120 gb)

After installing, i reboot and the remove the livecd, and when when grub loads, I select the latest Kernel (2.6.20-15), and then the progressbar does not make any progress. (Same bug in the Kernel (2.6.20-12 to 2.6.20-15 last one). After one or two minutes i can see this:

"Udevd-event [1950]: run-program: '/sbin/modprobe' abnormal exit

BusyBox v.1.1.3 (Debian 1:1.1.3-3ubuntu3) Built-install (ash)

/bin/sh: can access tty; jub control turned off (initramfs)"

and this:

"ALERT! /dev/disk/by-uuid/xxxxxxxxxxx Does not exist, dropping to a shell"

i thinks that "xxxxxxxxxxxx" is the by-uuid identificator for the system disk "/"
The number of Udevd-event [xxxx] can vary from 1950 to 1960 (in other install tryings)
The system works perfectly with Edgy with the same partitioning configuration.

Any solution?

[Olivier (olivier-lacroix)]

Grub now uses UUID to boot. Could it have it wrong ?
be sure that your grub line read root=UUID=XXXXXXXXXXXXXXXXXX, with the correct UUID, which you can get from a the livecd.

good luck

[georgielove (gorkaamor)]

Thanks Olivier,

No, i don't have it wrong, simply i havent it, i have been checking on my system directories (/dev) and none of my partitions seem to appear aswell. /dev/disk doesn't exist in the dev directory, another directories in dev that would have to be there, aren´t aswell. During the installation something is happened, that directories and files haven't be copyed to /dev, and i dont know why.

[Valerio F. Laube (vflaube-gmail)]

First, please excuse my bad english!!!!

I have exactly the same problem described above.

Ubuntu 7.04 (final) installed via "Desktop cd" on /dev/hda8
Also tried with "Alternate cd" but computer won't boot.

My computer don't have a SATA controller.

Procedure for repeating the problem:

1) Power on the computer
2) Supress the option "splash" from grub (for seeing more informations during the boot process)
3) boot
4) after few seconds i can see the following:

[xx.yyyyyy] Call Trace:
[xx.yyyyyy] [<zzzzzzzz>] [sis_init_one+0x0/0x3c0 [pata_sis]
[xx.yyyyyy] [<zzzzzzzz>] pci_device_probe+0x56/0x80
[xx.yyyyyy] [<zzzzzzzz>] really_probe+066/0x190
[xx.yyyyyy] [<zzzzzzzz>] driver_probe_device+0x49/0xc0
[xx.yyyyyy] [<zzzzzzzz>] __driver_attach+0x9e/0xa0
[xx.yyyyyy] [<zzzzzzzz>] bus_for_each_dev+0x3b/060
[xx.yyyyyy] [<zzzzzzzz>] driver_attach+0x24/0x30
[xx.yyyyyy] [<zzzzzzzz>] bus_add_driver+0x7b/0x1a0
[xx.yyyyyy] [<zzzzzzzz>] __pci_register_driver+0x15d/0x1ba0
[xx.yyyyyy] [<zzzzzzzz>] sys_mmap2+0xcd/0xd0 (*1)
[xx.yyyyyy] [<zzzzzzzz>] mii_ethtool_sset+0x0/0x1e0 [mii]
[xx.yyyyyy] [<zzzzzzzz>] syscall_call+0x7/0xb
[xx.yyyyyy] ============================
[xx.yyyyyy] Code: 00 0f b7 d0 31 c9 b8 39 10 00 00 e8 f6 7c 9a e1 85 c0
             89 c0 89 c7 74 dc 66 81 3e 30 06 0f 84 2c 03 00 00 89 f8 e8
             9e 72 9a e1 8b 7e 04 <89> 77 18 8b 46 04 3d 40 6e 85 de 0f
             84 02 00 00 3d 68 70 85
[xx.yyyyyy] EIP:[<de854625>] sis_init_one+0x75/0x3c0 [pata_sis] SS:ESP 0068:ddeb3 e0c
[xx.yyyyyy] udev-event [1900]: run-program: 1/sbin/modprobe' abnormal exit
             <6> usb 1-2: new full speed usb device using ohci-hcd and address 2
[xx.yyyyyy] usb 1-2: configuration #1 chosen from 1 choice
             check root= bootarg cat /proc/cmdline or missing modules,
             devices: cat /proc/modules ls /dev
ALERT! /dev/disk/by-uuid/86fc96dc-0478-4b47-b560-e7d6189a8e22 does not exist.
Dropping to a shell

...... after some time .....

BusyBox v1.1.3 (Debian 1:1.1.3-3ubuntu3) Built-in shell (ash)
ENTER 'help' for a list of built-in commands.
/bin/sh: can't acces tty; job control turned off

....... after ENTER Key pressed ......

(initramfs) [800.087312] input: AT translated set 2 keyboard as /class/input/input1

....... after ENTER Key pressed .......

(initramfs)

---------------------------------------------------------------------------------
xx.yyyyyy -> decimal numbers (different on each boot)
<zzzzzzzz> -> hexadecimal numbers (different on each boot)

(*1) at this position, some times the following line was seen:
       sys_init_module+0x15d/0x1ba0

======================================================================================

Other information:

cat /proc/version_signature: Ubuntu 2.6.20-15.27-generic
 (this information was retrieved from (initramfs) prompt)

sudo /lib/udev/vol_id -u /dev/hda8
  -> 86fc96dc-0478-4b47-b560-e7d6189a8e22
       (command executed from Fedora.
        hda8 is the partition for Ubuntu 7.04)

On the same computer are installed and perfectly working:
- Fedora Core 6 (kernel 2.6.20) (/dev/hda10)
- Xubuntu (Dapper) ...

[Valerio F. Laube (vflaube-gmail)]

No answers ?
No perspective for solutions ?

[Olivier (olivier-lacroix)]

as /dev/ is filled by udev. and as udev apparently fails to load a module, I would bet it is a useful one to access your drives. Failing to load it prevents the boot.

What is your ATA controller ?

[Valerio F. Laube (vflaube-gmail)]

Thanks for answer!

My ATA controller is SIS. Is only ATA, I don't have SATA.

00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0) (prog-if 80 [Master])
        Subsystem: ASUSTeK Computer Inc. Unknown device 807a
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-

The full configuration off my computer is in my first msg on this thread:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/107976/comments/3

Please, do you know if Ubuntu developers are working on on these bugs?
I love Ubuntu since version 5.10, but can't continue if can't boot the new version.
On the same computer (in other partitions) I have Ubuntu 6.10, Fedora 6 and RedHat ES 4.
Fedore 6 also have kernel 2.6.20.

Can you help me, or at least say to forget Ubuntu ? (at least for the current computer).

[aeneas (aeneascarver)]

Hi,

I have the same problem on 3 machines - all have a SIS IDE controller. This worked with Edgy. Booting feisty is impossible.

It seems that there is some race condition with the IDE modules, and they crash when they are loaded.

[Valerio F. Laube (vflaube-gmail)]

And the status of this bug remain "Unconfirmed".

[Valerio F. Laube (vflaube-gmail)]

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.

[georgielove (gorkaamor)]

Hi Valerio,

Have a look at this:

http://ubuntuforums.org/showthread.php?p=2525534#post2525534

Try this from the initframs prompt:

modprobe ide-disk
modprobe ide-generic
mount -t ext3 /dev/hda1 /root
mkdir -p /dev/disk/by-uuid
ln -s /dev/hda1 /dev/disk/by-uuid/xxxxx-xxxxx-xxxx-xxxx (replace with your uuid in /root/etc/fstab)
Control-D

It's a patch that does fix partially. I understand you, i am in the same situation as you, i am thinking in installin the 6.10, and wait till next versions. It doesn't seem that it's gonna be to fix completely soon.

Regards

[Valerio F. Laube (vflaube-gmail)]

Thanks Flexter.

This is the same I have see at: http://ubuntuforums.org/showthread.php?t=414903&highlight=ALERT%21+%2Fdev%2Fdisk%2Fby-uuid%2F

Have you tried this workaround ?

I have reinstalled my system and would try this workaround, but for other reason I could boot Feisty on my computer without this, as described above in https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/107976/comments/9

Flexter, I found same situations in other forums and seems it is related to SIS chipset.
I don't know the exact global marketshare of SIS, but hear in South América they are very common (popular?).

At the moment I also have reinstalled Ubuntu 6.10 for normal use and I'm evaluatinf Fedore (kernel 2.6.20) who installed in another partition.

[georgielove (gorkaamor)]

Yes, i've read it, as i started it logged in as kalimotxo ;). And i've tried and works but it's not a real solution since you have to do that workaround everytime you boot your pc. Have you tried it?

In this report there is more information, the status of the bug is confirmed also, and think that the ubuntu kernel team is working hard in fixing it already.

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/107774

I dont know if that kind of chipset (SIS) is very common here in Spain, anyway i wouldnt like to change to another distro, i loved Ubuntu since the first day i tryed. (sorry about my english too ;))

[Valerio F. Laube (vflaube-gmail)]

> Yes, i've read it, as i started it logged in as kalimotxo ;). And i've tried and works but it's not a real solution since you have to do that > >.workaround everytime you boot your pc. Have you tried it?

Have you tried the hack on page 2 of the thread ?

----------------------------------------------------------------------------------------------------
Code:

apt-get install yaird
sudo cp /boot/initrd.img-2.6.20-15-386 /boot/initrd.img-2.6.20-15-386.bk
sudo yaird -o /boot/initrd.img-2.6.20-15-386

Then reboot!
-------------------------------------------------------------------------------------------------------

I don't have tried the hacks from these guys, because when I reinstalled Feysty on primary partition /dev/hda/ and loaded Grub entirely in the bootsector of this partition, my computer booted succesfuly.

I also loved Ubuntu since 5.04 and would not to leave it.

Thanks for the link of confirmed bug.

English is very hard, really! Portuguese and Spanish were much more easy for our communication. But this is unacceptable by the rules of this forum, i think!

[georgielove (gorkaamor)]

So you installed the grup on that partition and it did work. I haven't tryed yet, but i have some doubts about it. I dont know if i can keep the win xp aswell. Could you?

By the way i tried the hack on page 2 of the other thread and it didnt work. It seemed that i did something wrong.

Regards

[Valerio F. Laube (vflaube-gmail)]

Right flexter. I'm running Ubuntu Feisty Fawn just now.

I don't know if the installation of grub in the bootsector of the partition of Feisty really helped to get the system boot.
I'ii explain what I did, since the firts installation attemp of Feisty:

My fdisk output:

----------
Disco /dev/hda: 60.0 GB, 60022480896 bytes
255 cabeças, 63 setores/trilha, 7297 cilindros
Unidades = cilindros de 16065 * 512 = 8225280 bytes

Dispositivo Boot Início Fim Blocos Id Sistema
/dev/hda1 * 1 383 3076416 83 Linux --> Ubuntu Feisty Fawn
/dev/hda2 384 390 56227+ b W95 FAT32 --> Free Dos
/dev/hda3 391 1029 5132767+ 7 HPFS ou NTFS --> Windows XP
/dev/hda4 1030 7297 50347710 f Win95 (LBA) Partição Extendida
/dev/hda5 1030 2049 8193118+ b W95 FAT32 --> My Documents for XP
/dev/hda6 2050 4535 19968763+ b W95 FAT32 --> only data files
/dev/hda7 4536 4665 1044193+ 82 Linux swap / Solaris
/dev/hda8 4666 5175 4096543+ 83 Linux --> Ubuntu Edgy Eft
/dev/hda9 5176 5685 4096543+ 83 Linux --> Red Hat ES 4
/dev/hda10 5686 6195 4096543+ 83 Linux --> Fedora Core 6
/dev/hda11 6196 6514 2562336 83 Linux --> Xubuntu 6.10
/dev/hda12 6515 7297 6289416 83 Linux --> /home for all ubuntu systems

Disco /dev/hdd: 40.0 GB, 40060403712 bytes
255 cabeças, 63 setores/trilha, 4870 cilindros
Unidades = cilindros de 16065 * 512 = 8225280 bytes

Dispositivo Boot Início Fim Blocos Id Sistema
/dev/hdd1 * 1 1912 15358108+ 83 Linux --> only datafiles
/dev/hdd2 1913 4869 23752102+ f Win95 (LBA) Partição Extendida --> only datafiles
/dev/hdd5 1913 4869 23752071 7 HPFS ou NTFS --> only datafiles

-----------------------
I've XOSL installed as primary boot manager (they use MBR and /dev/hda3 (FAT partition). More about Xosl on http://www.ranish.com/part/xosl.htm. I use XOSL for several years.

Windows 98 was installed on /dev/hda1, before the problems with Feisty.
Windows XP is installed on the 3. partition.

---------------------------------------------------------------------------------------------------------------------
What I did:

1) 20 April -> First attempt to install Feisty
- backup with "partimage" of /dev/hda8
- I tried Ubuntu Feisty Fawn alternate CD - They don't boot my system.
- Then i've downloaded the Ubuntu Feisty fawn desktop cd. My system has booted and the installation was OK, Grub was entirely loaded in the bootsector of /dev/hda8.
By rebooting th...

[georgielove (gorkaamor)]

Hi Valerio, thanks for the comments,

So you typed (/dev/hda1), instead of (hd0) in the advanced options during intall? I dont understand that point.

[georgielove (gorkaamor)]

I think, i am understanding little bit, so i should install feisty on /dev/hda1 not on /dev/hda2 because that causes the problem, but i dont know how to install the grub in a specific partition, because i though that just it could be installed on MBR and not on a partition.

[Valerio F. Laube (vflaube-gmail)]

> So you typed (/dev/hda1), instead of (hd0) in the advanced options during intall? I dont understand that point.
- I have type (hd0,0), but /dev/hda1 also should work. This will install Grub in bootsector of /dev/hda1.
But remember, in this case you must have another boot manager installed. I have Xosl. Or maybe you can make a floppy for booting Ubuntu in /dev/hda1.

> so i should install feisty on /dev/hda1 not on /dev/hda2 because that causes the problem,
> ...
> because i though that just it could be installed on MBR and not on a partition.

The system should work installed in any partition, with Grub in MBR or in bootsector. But I only could boot Ubuntu Feisty when it was installed on /dev/hda as primary partition and Grub installed entirely in bootsector of the same partition.
I don't understand why. This is not the normal behavior.

Seems that have a new kernel in https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/2.6.20-15.27.
Maybe, we can wait for an version 7.04-1 with this new kernel ? There are so many Ubuntu users and others trying Ubuntu who can't install Feisty.

[georgielove (gorkaamor)]

I have got it, feisty fawn is working properly now, finally i installed the grub on (hd0,1), that is on /dev/hda2 (typing (/dev/hda2) on advanced options of install didn't work). So i didnt need to install feisty in the primary partition i did in the second partition of the first hard disk (/dev/hda2). But now i have to boot my computer with supergrub disk.

I have reading about XOSL and looks interesting when you manage many operative systems but looks that you need another partition for installing it and finally i used a supergrub disk. I think that this is a temporarily patch, so we have to wait for that kernel you mention.

[Valerio F. Laube (vflaube-gmail)]

Congratulations!

If you want to try installing Grub in bootsector of /dev/hda2, run grub from a terminal and take a look below:

--------------------------------- typical grub session ---------------------------------------------------------------------------
sudo grub
$ password: (type the password of your account)
grub>
grub> root (hd0,1) (hd0,1 in grub notation is /dev/hda2 in device notation)
 Filesystem type is reiserfs, partition type 0x83 ( in this case my partition was formated as reiserfs)
grub> setup (hd0,1)
 Checking if "/boot/grub/stage1" exists... yes
 Checking if "/boot/grub/stage2" exists... yes
 Checking if "/boot/grub/reiserfs_stage1_5" exists... yes
 Running "embed /boot/grub/reiserfs_stage1_5 (hd0,7)"... 18 sectors are embedded.succeeded
 Running "install /boot/grub/stage1 (hd0,7) (hd0,1)1+18 p (hd0,1)/boot/grub/stage2 /boot/grub/menu.lst"... succeeded
Done.
-----------------------------------------------------------------------------------

You are right about XOSL. They need another partition. Can to be a FAT, FAT32 or an special format for Xosl.
The size required is minimal, less than 1 MB, and if you have a Windows installation in a FAT32 partition, they can share the same partition. But if you choose FAT32, you should create a partition with at least 32 MB. For some reason, seems that FAT32 in lesser partitions have problems.
Usually I create a FAT32 partition and install DOS (FreeDos, DrDos or Ms-Dos) along with some utilities like tools for cloning and reparing disk.
If you don't want to install and boot DOS, you can install Xosl in a logical partition. But I'm not sure if this will work when the partition is located over cilinder 1024. In this situation we need the Int13 extensions.

I agree with you. All this workaround should be only a temporary solution. I'm still waiting for Ubuntu 7.04-1.

[georgielove (gorkaamor)]

Thanks Valerio, i dont know what you mean when you tell me to install grub on (hd0,1) since i have already the grub installed on (hd0,1) i did during the installation, and now when I boot my computer the WinXp runs directly without appearing any menu, unless that i use a supergrub disk and then choose the s.o. which i want to boot. Maybe i'd have to install the XOSL in the MBR for a proper boot.

[Valerio F. Laube (vflaube-gmail)]

> i dont know what you mean when you tell me to install grub on (hd0,1) since i have already the grub installed on (hd0,1) i did
> during the installation

Forget flexter! I should take more attention to your prior message. Excuse, please.
You are right! for more confortable boot, only one boot manager (in grub) are missing. (Xosl, ...).

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Michele Mangili (mangilimic)]

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.