We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
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
I also have this problem. After upgrading to Fesity my second hard
drive seems to be nowhere
#
$ sudo fdisk -l
Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
I installed Fesity everything went well, however on reboot
well during the installation Fesity finds hdb1 hdb2, on reboot this
not changed to sdb1 sdb2 shown by fdisk -l
#
[EMAIL PROTECTED]:~# fdisk -l
Disk /dev/sda: 80.0 GB, 80060424192 bytes
255
** Changed in: linux-source-2.6.20 (Ubuntu)
Sourcepackagename: None = linux-source-2.6.20
--
Kernel 2.6.20-15 loses two partitions/disks
https://bugs.launchpad.net/bugs/106408
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
This is NOT fixed by the latest kernel. In fact the kernel fails to even
boot fully (X does not come up).
--
Kernel 2.6.20-15 loses two partitions/disks
https://bugs.launchpad.net/bugs/106408
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Renamed the bug - this is a kernel issue. If I boot with kernel
2.6.20-12, it names the hard disks in the same way as edgy did (i.e.
hd*...), and /mm1 and /mm2 are detected (and show up in both /dev/disk
/by-uuid and /dev/disk/by-path). If I booth with kernel 2.6.20-15, the
hard disks are given
