btw. The fact that this works on usb key but not on Windows main volume
suggests ntfs-3g is not doing anything wrong as such but that something
in Windows is guarding against external changes to the system volume.
Do you by any chance have an SSD or hybrid drive that Windows might be
using as a
Have you got any 3rd party security related software / antivirus
software installed that might be protecting the volume against
modifications? If yes what happens if you turn it off?
Have you got any of the change tracking features enabled in Windows? If
yes what happens if you turn them off?
This bug report is correct. This happens when the -generic kernel is
installed. XenServer cannot boot this 32-bit kernel.
If the VM is x86_64 and the 64-bit kernel is installed it works fine.
If the VM is x86 and the 32-bit kernel is installed it does not boot
using -generic but works fine
I am using a fresh install of Ubuntu 10.04 LTS Server and have used
virt-manager to set up an NFS storage repository (located on another
machine).
On boot the storage fails to mount.
First it was failing with statd not running and I fixed that by
editing /etc/init/statd.conf making this change:
I am using a fresh install of Ubuntu 10.04 LTS Server and have used
virt-manager to set up an NFS storage repository (located on another
machine).
On boot the storage fails to mount.
First it was failing with statd not running and I fixed that by
editing /etc/init/statd.conf making this change:
I am using a fresh install of Ubuntu 10.04 LTS Server and have used
virt-manager to set up an NFS storage repository (located on another
machine).
On boot the storage fails to mount.
First it was failing with statd not running and I fixed that by
editing /etc/init/statd.conf making this change:
Hi Colin,
Thanks for the quick fix. Can you tell me which build of the package it
is in once it is in the official Ubuntu Lucid tree and I will do another
install (I have a second identical server waiting to be built and I can
wait another day or two before doing it so we can make sure it is
(sorry about the status change - I thought clicking on it might bring up
further details and instead it changed it, oops - I changed it back)
--
preseed with RAID and GPT fails to set bios_grub flag on first disk but does
set it on second so install fails
https://bugs.launchpad.net/bugs/566965
Ok, thanks. I will try an install on Monday, hopefully it will be in by
then.
--
preseed with RAID and GPT fails to set bios_grub flag on first disk but does
set it on second so install fails
https://bugs.launchpad.net/bugs/566965
You received this bug notification because you are a member of
Public bug reported:
Binary package hint: partman-base
Hi,
Note: I am not sure this belongs in partman-base but it definitely is in
one of the partman-*...
Note: This is on latest Ubuntu Lucid 10.04 LTS. The time stamp on the
installer is 20081029ubuntu100.
I am doing automated install
** Attachment added: partman log at point of error message that grub-install
has failed.
http://launchpadlibrarian.net/44859254/partman
--
preseed with RAID and GPT fails to set bios_grub flag on first disk but does
set it on second so install fails
https://bugs.launchpad.net/bugs/566965
** Attachment added: syslog at point at which install failed with grub-install
error message
http://launchpadlibrarian.net/44859280/syslog
--
preseed with RAID and GPT fails to set bios_grub flag on first disk but does
set it on second so install fails
** Attachment added: automated installation config file that causes the error
http://launchpadlibrarian.net/44859385/ks.cfg
--
preseed with RAID and GPT fails to set bios_grub flag on first disk but does
set it on second so install fails
https://bugs.launchpad.net/bugs/566965
You received
Forgot to say that this is on 64-bit Ubuntu (amd64) and that the
installation is started using DHCP+PXE booting and the
pxelinux.cfg/default entry which kicks off the installation is:
LABEL install
kernel ubuntu-installer/amd64/linux
append vga=normal
14 matches
Mail list logo