Can confirm this bug for 10.04 server.
nfs isn't connected in 1/10 cases in the boot proces.
The rest of the times it connects within the boot proces.
But in either case the next error shows during boot:
mount.nfs: DNS resolution failed for 192.168.1.11: name or service unknown
The client is a 10
*** This bug is a duplicate of bug 97179 ***
** This bug has been marked a duplicate of bug 97179
w/ desktop CD, driver not loaded for jmicron jmb363 controller's SATA ability
--
jmicron JMB363 and the SATA disks attached not visible
https://launchpad.net/bugs/98511
--
ubuntu-bugs mailing l
SATA mode in the BIOS is AHCI modefor real. IDE mode is the legacy mode
for the controller. I think ubuntu must detectd both modes to solve the
problems for humen beings. Further I preffer IDE mode for me, because
it's faster then AHCI mode(not for all people) and the POST is going
much faster.
--
I think the solution is in:
Bug report: 83231
https://launchpad.net/ubuntu/+source/initramfs-tools/+bug/83231
the "udevsettle --timeout 10" at the end of /usr/share/initramfs-
tools/scripts/init-premount/udev works too.
--
boot-time race condition initializing md
https://launchpad.net/bugs/75681
Small mistake. The daily alternate build of 26-03, don't use 20.13 but
20.12. It has the 20.13 onboard, but doesn't use it.
But I can start the jmicron with 20.12 with means he has properly the same
problem.
You can't use the updated kernel on a live CD, you must restart it, but then
you use the
I can confirm this bug.
The jmicron driver found only pata disks.
If I use a pata cdrom player with a sata2pata converter, jmicron don't find it.
My sata disks isn't detected to.
If I use my cdrom drive with pata interface connected to the jmicron
then it is found.
--
can't find sata disk kubu
*** This bug is a duplicate of bug 84964 ***
You have got a Jmicron controller. This is a known problem. It's already fixt.
But it was to late for the beta.
See also:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/84964
** This bug has been marked a duplicate of bug 84964
I can confirm this in Herd 4.
The exact error message:
mdadm: No devices listed in conf file were found.
--
linux software RAID not working after herd 3 installation..
https://launchpad.net/bugs/83231
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/li
