[Bug 489826] Re: Upgrade to Karmic: can't boot, can't mount. Partitions missing from /dev/.
Buck Golemon
workitharder at gmail.com
Sun Nov 29 20:43:35 UTC 2009
** Description changed:
Binary package hint: devicekit-disks
After upgrade to Karmic, my machine will no longer boot with a "ALERT!
/dev/disk/by-uuid/XXX does not exist." error.
I did search the forums but my situation seems different from all of the
problems I found in that:
- [LIST=1]
- [*]/dev/hda1 is also missing
- [*]/dev/disk/by-uuid is [B]completely[/B] missing
- [/LIST]
+ 1) /dev/hda1 is also missing
+ 2) /dev/disk/by-uuid is [B]completely[/B] missing
Because of #1, the root partition is not mounted, and I can't get to
fdisk or /etc/mtab or any of the usual suggestions.
-
This is what I see at the boot-recovery (busybox) terminal:
[CODE]$ ls /dev/sd*
/dev/sda /dev/sdb
$ ls /dev/disk/* -l
/dev/disk/by-id:
total 0
lrwxrwxrwx 1 root root 9 2009-11-28 20:32 ata-MAXTOR_6L060J3_663210555230 -> ../../sdb
lrwxrwxrwx 1 root root 9 2009-11-28 20:32 ata-MAXTOR_6L060J3_663217454727 -> ../../sda
lrwxrwxrwx 1 root root 26 2009-11-28 20:32 dm-name-pdc_dgecfaiii -> ../../mapper/pdc_dgecfaiii
lrwxrwxrwx 1 root root 26 2009-11-28 20:32 dm-uuid-DMRAID-pdc_dgecfaiii -> ../../mapper/pdc_dgecfaiii
lrwxrwxrwx 1 root root 9 2009-11-28 20:32 scsi-SATA_MAXTOR_6L060J3_663210555230 -> ../../sdb
lrwxrwxrwx 1 root root 9 2009-11-28 20:32 scsi-SATA_MAXTOR_6L060J3_663217454727 -> ../../sda
/dev/disk/by-label:
total 0
lrwxrwxrwx 1 root root 9 2009-11-28 20:33 Ubuntu\x209.10\x20i386 -> ../../sr0
/dev/disk/by-path:
total 0
lrwxrwxrwx 1 root root 9 2009-11-28 20:32 pci-0000:00:0f.1-scsi-0:0:0:0 -> ../../sda
lrwxrwxrwx 1 root root 9 2009-11-28 20:32 pci-0000:00:0f.1-scsi-0:0:1:0 -> ../../sdb
lrwxrwxrwx 1 root root 9 2009-11-28 20:32 pci-0000:00:0f.1-scsi-1:0:0:0 -> ../../sr0[/CODE]
-
- Because of #1, the root partition is not mounted, and my machine is not bootable, so I had to file a ticket using this procedure:
+ Because of #1, the root partition is not mounted, and my machine is not
+ bootable, so I had to file a ticket using this procedure:
(After booting to an Ubuntu Dapper live-CD)
sudo -i
mount /dev/disk/by-uuid/1d79a35a-566c-4083-a75a-bafc8b0bb545 /mnt
mount /dev/disk/by-uuid/17a59b8e-904d-46ed-968c-d8ca2d3c53b7 /mnt/boot/
mount --bind /dev /mnt/dev
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
cp /etc/resolv.conf /mnt/var/run/resolvconf/resolv.conf
chroot /mnt /bin/bash
su - golemon
ubuntu-bug
-
I attempted to resolve my issues on the Ubuntu forums, but my problem doesn't seem to be a conventional one.
The thread is here:
http://ubuntuforums.org/showthread.php?t=1339024
-
------
Problem:
A long time ago I had my disks in a RAID array. The new dmraid package
in Karmic detected this and set up my disks to mount as raid. Note the
'/dev/sr0' partition shown above. Not very helpful...
+ This took me four days of intense debugging to figure out and fix, and
+ I'm not a casual Linux user. If Gramdma or Mom runs into this, they're
+ looking at an effectively bricked computer.
+
------
Solution:
Download and boot to a Karmic Live-CD.
Run the following to remove lingering RAID meta-data:
- [CODE]sudo dmraid -E -r /dev/sda
- sudo dmraid -E -r /dev/sdb[/CODE]
+ sudo dmraid -E -r /dev/sda
+ sudo dmraid -E -r /dev/sdb
+ ------
+ Bugfix:
+
+ dmraid needs to be more careful when installing. It should not changes
+ disks from IDE mode to RAID mode without a clear message and
+ confirmation from the user.
+
+ To automate the detection better, dmraid should check the *content* of
+ the disks, not just the metadata. If putting the disks in raid mode
+ makes all the content unusable, then that's a poor guess for
+ autoconfiguration.
+
+ I note that gparted was able to still detect my partitions correctly
+ even with the disks configured to RAID. There's probably some good code
+ to "share" there.
------
ProblemType: Bug
Architecture: i386
CustomUdevRuleFiles: 85-lvm.rules 45-libmtp7.rules 45-logitechmouse.rules 65-libmtp.rules 50-bluez-pcmcia-support.rules 85-mdadm.rules 85-evms.rules 025_logitechmouse.rules 45-libnjb.rules
Date: Sat Nov 28 19:47:16 2009
DevkitDisksDump:
Error: command ['devkit-disks', '--dump'] failed with exit code 1:
(devkit-disks:9529): devkit-disks-WARNING **: Couldn't connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: ipv6 af_packet rfcomm l2cap bluetooth ppdev lp powernow_k8 cpufreq_userspace cpufreq_stats cpufreq_powersave cpufreq_ondemand freq_table cpufreq_conservative video output sbs sbshc container dock ac iptable_filter ip_tables x_tables snd_via82xx gameport snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc snd_mpu401_uart snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device psmouse snd parport_pc i2c_viapro amd64_agp button serio_raw shpchp parport i2c_core agpgart k8temp evdev pci_hotplug soundcore pcspkr battery squashfs loop unionfs usbhid hid nls_cp437 isofs ext3 jbd mbcache sg sr_mod cdrom sd_mod floppy via_rhine mii ehci_hcd pata_via uhci_hcd sata_via pata_acpi ata_generic usbcore libata scsi_mod thermal processor fan fbcon tileblit font bitblit softcursor fuse
Package: devicekit-disks 007-2ubuntu3
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.gz quiet splash --
ProcEnviron:
LANGUAGE=en
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.24-24.56-generic
SourcePackage: devicekit-disks
Symptom: storage
UdevDb: Error: [Errno 2] No such file or directory
Uname: Linux 2.6.24-24-generic i686
XsessionErrors:
(gnome-settings-daemon:3897): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(gnome-panel:3908): libglade-WARNING **: Unexpected element <requires-version> inside <glade-interface>.
(gnome-terminal:3987): Gtk-WARNING **: PopupLeaveFullscreen: missing action PopupLeaveFullscreen
(gnome-terminal:3987): Gtk-WARNING **: PopupLeaveFullscreen: missing action PopupLeaveFullscreen
dmi.bios.date: 03/31/2005
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: K8M800-M2
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd03/31/2005:svn:pn:pvr:rvn:rnK8M800-M2:rvr:cvn:ct3:cvr:
** Description changed:
Binary package hint: devicekit-disks
After upgrade to Karmic, my machine will no longer boot with a "ALERT!
/dev/disk/by-uuid/XXX does not exist." error.
I did search the forums but my situation seems different from all of the
problems I found in that:
1) /dev/hda1 is also missing
- 2) /dev/disk/by-uuid is [B]completely[/B] missing
+ 2) /dev/disk/by-uuid is *completely* missing
Because of #1, the root partition is not mounted, and I can't get to
fdisk or /etc/mtab or any of the usual suggestions.
This is what I see at the boot-recovery (busybox) terminal:
- [CODE]$ ls /dev/sd*
+ $ ls /dev/sd*
/dev/sda /dev/sdb
$ ls /dev/disk/* -l
/dev/disk/by-id:
total 0
lrwxrwxrwx 1 root root 9 2009-11-28 20:32 ata-MAXTOR_6L060J3_663210555230 -> ../../sdb
lrwxrwxrwx 1 root root 9 2009-11-28 20:32 ata-MAXTOR_6L060J3_663217454727 -> ../../sda
lrwxrwxrwx 1 root root 26 2009-11-28 20:32 dm-name-pdc_dgecfaiii -> ../../mapper/pdc_dgecfaiii
lrwxrwxrwx 1 root root 26 2009-11-28 20:32 dm-uuid-DMRAID-pdc_dgecfaiii -> ../../mapper/pdc_dgecfaiii
lrwxrwxrwx 1 root root 9 2009-11-28 20:32 scsi-SATA_MAXTOR_6L060J3_663210555230 -> ../../sdb
lrwxrwxrwx 1 root root 9 2009-11-28 20:32 scsi-SATA_MAXTOR_6L060J3_663217454727 -> ../../sda
/dev/disk/by-label:
total 0
lrwxrwxrwx 1 root root 9 2009-11-28 20:33 Ubuntu\x209.10\x20i386 -> ../../sr0
/dev/disk/by-path:
total 0
lrwxrwxrwx 1 root root 9 2009-11-28 20:32 pci-0000:00:0f.1-scsi-0:0:0:0 -> ../../sda
lrwxrwxrwx 1 root root 9 2009-11-28 20:32 pci-0000:00:0f.1-scsi-0:0:1:0 -> ../../sdb
- lrwxrwxrwx 1 root root 9 2009-11-28 20:32 pci-0000:00:0f.1-scsi-1:0:0:0 -> ../../sr0[/CODE]
+ lrwxrwxrwx 1 root root 9 2009-11-28 20:32 pci-0000:00:0f.1-scsi-1:0:0:0 -> ../../sr0
Because of #1, the root partition is not mounted, and my machine is not
bootable, so I had to file a ticket using this procedure:
(After booting to an Ubuntu Dapper live-CD)
sudo -i
mount /dev/disk/by-uuid/1d79a35a-566c-4083-a75a-bafc8b0bb545 /mnt
mount /dev/disk/by-uuid/17a59b8e-904d-46ed-968c-d8ca2d3c53b7 /mnt/boot/
mount --bind /dev /mnt/dev
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
cp /etc/resolv.conf /mnt/var/run/resolvconf/resolv.conf
chroot /mnt /bin/bash
su - golemon
ubuntu-bug
I attempted to resolve my issues on the Ubuntu forums, but my problem doesn't seem to be a conventional one.
The thread is here:
http://ubuntuforums.org/showthread.php?t=1339024
------
Problem:
A long time ago I had my disks in a RAID array. The new dmraid package
in Karmic detected this and set up my disks to mount as raid. Note the
'/dev/sr0' partition shown above. Not very helpful...
This took me four days of intense debugging to figure out and fix, and
I'm not a casual Linux user. If Gramdma or Mom runs into this, they're
looking at an effectively bricked computer.
------
Solution:
Download and boot to a Karmic Live-CD.
Run the following to remove lingering RAID meta-data:
sudo dmraid -E -r /dev/sda
sudo dmraid -E -r /dev/sdb
------
Bugfix:
dmraid needs to be more careful when installing. It should not changes
disks from IDE mode to RAID mode without a clear message and
confirmation from the user.
To automate the detection better, dmraid should check the *content* of
the disks, not just the metadata. If putting the disks in raid mode
makes all the content unusable, then that's a poor guess for
autoconfiguration.
I note that gparted was able to still detect my partitions correctly
even with the disks configured to RAID. There's probably some good code
to "share" there.
------
ProblemType: Bug
Architecture: i386
CustomUdevRuleFiles: 85-lvm.rules 45-libmtp7.rules 45-logitechmouse.rules 65-libmtp.rules 50-bluez-pcmcia-support.rules 85-mdadm.rules 85-evms.rules 025_logitechmouse.rules 45-libnjb.rules
Date: Sat Nov 28 19:47:16 2009
DevkitDisksDump:
Error: command ['devkit-disks', '--dump'] failed with exit code 1:
(devkit-disks:9529): devkit-disks-WARNING **: Couldn't connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: ipv6 af_packet rfcomm l2cap bluetooth ppdev lp powernow_k8 cpufreq_userspace cpufreq_stats cpufreq_powersave cpufreq_ondemand freq_table cpufreq_conservative video output sbs sbshc container dock ac iptable_filter ip_tables x_tables snd_via82xx gameport snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc snd_mpu401_uart snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device psmouse snd parport_pc i2c_viapro amd64_agp button serio_raw shpchp parport i2c_core agpgart k8temp evdev pci_hotplug soundcore pcspkr battery squashfs loop unionfs usbhid hid nls_cp437 isofs ext3 jbd mbcache sg sr_mod cdrom sd_mod floppy via_rhine mii ehci_hcd pata_via uhci_hcd sata_via pata_acpi ata_generic usbcore libata scsi_mod thermal processor fan fbcon tileblit font bitblit softcursor fuse
Package: devicekit-disks 007-2ubuntu3
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.gz quiet splash --
ProcEnviron:
LANGUAGE=en
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.24-24.56-generic
SourcePackage: devicekit-disks
Symptom: storage
UdevDb: Error: [Errno 2] No such file or directory
Uname: Linux 2.6.24-24-generic i686
XsessionErrors:
(gnome-settings-daemon:3897): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(gnome-panel:3908): libglade-WARNING **: Unexpected element <requires-version> inside <glade-interface>.
(gnome-terminal:3987): Gtk-WARNING **: PopupLeaveFullscreen: missing action PopupLeaveFullscreen
(gnome-terminal:3987): Gtk-WARNING **: PopupLeaveFullscreen: missing action PopupLeaveFullscreen
dmi.bios.date: 03/31/2005
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: K8M800-M2
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd03/31/2005:svn:pn:pvr:rvn:rnK8M800-M2:rvr:cvn:ct3:cvr:
--
Upgrade to Karmic: can't boot, can't mount. Partitions missing from /dev/.
https://bugs.launchpad.net/bugs/489826
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
More information about the universe-bugs
mailing list