On Sat, 31 Jul 2010, Andrei Popescu wrote:
> On Sb, 31 iul 10, 14:46:55, Thomas H. George wrote:
> > It is grub2. I checked and the # kopt is in the new format and the
> > UUID is that of the root partition. I ran update-grub just to be sure
> > and now the system will boot from a MBR written by
On Saturday 31 July 2010 16:15:16 Paul E Condon wrote:
> On 20100731_225121, Andrei Popescu wrote:
> > On Sb, 31 iul 10, 14:46:55, Thomas H. George wrote:
> > > It is grub2. I checked and the # kopt is in the new format and the
> > > UUID is that of the root partition. I ran update-grub just to b
On Saturday 31 July 2010 11:42:35 Thomas H. George wrote:
> as compared to the output of df -h
>
> FilesystemSize Used Avail Use% Mounted on
> /dev/sdc1 71G 39G 29G 58% /
> tmpfs 2.0G 0 2.0G 0% /lib/init/rw
> udev 2.0G 252K 2
On Sb, 31 iul 10, 15:15:16, Paul E Condon wrote:
> On 20100731_225121, Andrei Popescu wrote:
> > On Sb, 31 iul 10, 14:46:55, Thomas H. George wrote:
> > > It is grub2. I checked and the # kopt is in the new format and the
> > > UUID is that of the root partition. I ran update-grub just to be sure
On 20100731_225121, Andrei Popescu wrote:
> On Sb, 31 iul 10, 14:46:55, Thomas H. George wrote:
> > It is grub2. I checked and the # kopt is in the new format and the
> > UUID is that of the root partition. I ran update-grub just to be sure
> > and now the system will boot from a MBR written by g
On Sb, 31 iul 10, 14:46:55, Thomas H. George wrote:
> It is grub2. I checked and the # kopt is in the new format and the
> UUID is that of the root partition. I ran update-grub just to be sure
> and now the system will boot from a MBR written by grub. The output of
> df -h is still the same mixe
On Sat, Jul 31, 2010 at 09:05:45PM +0300, Andrei Popescu wrote:
> On Sb, 31 iul 10, 12:42:35, Thomas H. George wrote:
> >
> > 6. During the installation of the new kernel the fstab was modified to
> > identify the hard drives by their UUID's. The system then could no
> > longer be booted from MBR
On Sb, 31 iul 10, 12:42:35, Thomas H. George wrote:
>
> 6. During the installation of the new kernel the fstab was modified to
> identify the hard drives by their UUID's. The system then could no
> longer be booted from MBR's installed by grub. The boot tried to load
> the new 2.6.32-5 kernel bu
TWIMC: The following is a summary of the problems I encountered when the
kernel image vmlinuz-2.6.32-5-amd64 was released.
1. A dist-upgrade loaded and tried to install linux-base and the
2.6.32-5 kernel image. The install failed with error messages from
dosfslabel.
2. Running dosfslabel on each
9 matches
Mail list logo