Security updates have fouled it up-AGAIN!!
Once again, installing updates have corrupted the loading of 9.10. Via grub, I have to go back to a previous version. This is not helpful. What is going on with the developers of Ubuntu? Never had this bother with 9.04, for example!!!
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- Ubuntu yelp Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- Sam_
- Solved:
- Last query:
- Last reply:
|
Revision history for this message
|
#1 |
Sorry for the trouble you've experienced.
Which securtiy update?
http://
You may search for the package and go to bug section to see if your issue is already reported.
http://
In case of helping to make Ubuntu better, you may consider to file a bug.
https:/
|
Revision history for this message
|
#2 |
Thanks for this. I have no idea which update caused this. I just accept the
update manager's suggestions for security updates and recommended updates.
Perhaps I should only install them one at a time, and make a note of each
one? This is time consuming!!!
This is the fourth time this has happened since 9.10, and I am not happy
about it. I have to scrap every thing and start again each time.
The message I get is:
[1.104323] Kernel Panic - not syncing: VFS: Unable to mount root fs on
unknown - block (8.17)
I have used WUBI to install Ubuntu, and it all worked much better when GRUB
was not involved.
Richard
-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Sam
Sent: 31 January 2010 22:24
To: <email address hidden>
Subject: Re: [Question #99346]: Security updates have fouled it up-AGAIN!!
Your question #99346 on yelp in ubuntu changed:
https:/
Status: Open => Answered
Sam proposed the following answer:
Sorry for the trouble you've experienced.
Which securtiy update?
http://
You may search for the package and go to bug section to see if your issue is
already reported.
http://
In case of helping to make Ubuntu better, you may consider to file a bug.
https:/
--
If this answers your question, please go to the following page to let us
know that it is solved:
https:/
nswer_id=0
If you still need help, you can reply to this email or go to the
following page to enter your feedback:
https:/
You received this question notification because you are a direct
subscriber of the question.
|
Revision history for this message
|
#3 |
> Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown - block
Virtual Filesystem: unable to mount root filesystem on unknown block ...
means Grub can't mount /
Anyway there should appear more messages which may advise, to view them turn off 'quiet splash'.
After editing the file update Grub and reboot.
Depending on which Grub is installed.
Grub_legacy:
/boot/grub/menu.lst
# defoptions=quiet splash
Grub_2:
/etc/default/grub
GRUB_CMDLINE_
> Via grub, I have to go back to a previous version
Previous version of what? Ubuntu version, Grub version?
How are you running Ubuntu at the moment, via Wubi, dualboot, multiboot?
Did you change anything about partitions?
Did you choose a former kernel image in boot menu and could boot with it?
Did you check with MemTest (also available from boot menu)?
Did you make a filesystem check via 'fsck'?
CLI:
sudo touch /forcefsck
## after next boot filesystem will be checked.
https:/
> which update caused this
Verify the day of the update. Synaptic has an option to search the history, which is stored for xxx days, depending on your preferences.
Open Synaptic -> file -> history
btw. in case you have proposed repository enabled, you'll get packages for testing purpose and you may disable it.
https:/
Which version of Grub are you using, Grub_legacy or Grub_2, may depend if you upgrade from 9.04 to 9.10 or made fresh installation of 9.10.
https:/
CLI:
sudo grub-install -v
https:/
For further investigations, verify the output of:
sudo fdisk -l
cat /etc/fstab
sudo blkid
mount
|
Revision history for this message
|
#4 |
|
Revision history for this message
|
#5 |
Thanks for the replies.
To answer your questions, but not necessarily in the order you asked:
I dual boot, having used WUBI to install, GRUB was not involved until 9.10
Ubuntu. The version is 1.97, beta 4.
The GRUB menu screen (after boot.ini gives me the choice for Windows or
Ubuntu) gives me 5 choices:
Ubuntu, Linux 2.6.31-17-generic
Ubuntu, Linux 2.6.31-17-generic (recovery mode)
Ubuntu, Linux 2.6.31-14-generic
Ubuntu, Linux 2.6.31-14-generic (recovery mode)
Microsoft Windows XP Pro (on /dev/sda1)
Windows does not boot from this point, though. WUBI first gave me Linux
image 2.6.31-14, which quickly updated to 2.6.13-17 without problems. This
has worked OK for the last few weeks, since the last corrupting update!
Selecting 2.6.31-14 will load Ubuntu OK.
This version of GRUB is at /etc/default/grub, but I am not sure how to "turn
off" quiet splash.
I have not changed any partition information. (Since 9.10, my partitions
have not been recognised in the same way as with 9.04, and previous
versions. I have 2 hard drives, partitioned into 3 each, labelled Local Disk
1A, 1B, 1C, and 2A, 2B, and 2C. Windows boots from 1A, and Ubuntu is on 2A.
1B and 2B are not recognised as such, Ubuntu sees them as extended partions
with unallocated space, but with ntfs-config, they can be accessed.
I have run fsck, this showed no problems.
The updates which caused the problem were loaded on 31 Jan and were the
following:
Upgraded the following packages:
dhcp3-client (3.1.2-1ubuntu7) to 3.1.2-1ubuntu7.1
dhcp3-common (3.1.2-1ubuntu7) to 3.1.2-1ubuntu7.1
fuse-utils (2.7.4-
libcairo2 (1.8.8-2ubuntu1) to 1.8.8-2ubuntu1.1
libfuse2 (2.7.4-
libpulse-browse0 (1:0.9.19-0ubuntu4) to 1:0.9.19-0ubuntu4.1
libpulse-
libpulse0 (1:0.9.19-0ubuntu4) to 1:0.9.19-0ubuntu4.1
libsmbclient (2:3.4.
libwbclient0 (2:3.4.
pulseaudio (1:0.9.19-0ubuntu4) to 1:0.9.19-0ubuntu4.1
pulseaudio-
pulseaudio-
pulseaudio-
pulseaudio-
pulseaudio-
pulseaudio-utils (1:0.9.19-0ubuntu4) to 1:0.9.19-0ubuntu4.1
rhythmbox (0.12.5-0ubuntu5.1) to 0.12.5-0ubuntu5.2
samba (2:3.4.
samba-common (2:3.4.
samba-common-bin (2:3.4.
smbclient (2:3.4.
software-center (1.0.2) to 1.0.3
I do not have the proposed repository selected.
I have not tried to update GRUB.
The outputs you suggested are as follows:
richard@ubuntu:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# -- This file has been automaticly generated by ntfs-config --
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/host/ubuntu/
/host/ubuntu/
/dev/fd0 /media/floppy0 auto rw,user,
/dev/sda5 /media/
/dev/sda6 /media/
/dev/sda1 /media/
/dev/sdb6 /media/
/dev/sdb5 /media/
richard@ubuntu:~$ sudo blkid
/dev/loop0: UUID="cd312c35-
/dev/sda1: UUID="F84CA83B4
/dev/sda5: UUID="B0BCD5D6B
/dev/sda6: UUID="DAC014EAC
/dev/sdb1: UUID="42CC3F0DC
/dev/sdb5: UUID="D0D871D3D
/dev/sdb6: UUID="D82819B62
richard@ubuntu:~$ sudo fdisk -l
omitting empty partition (5)
Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xd205d205
Device Boot Start End Blocks Id System
/dev/sda1 * 1 3265 26226081 7 HPFS/NTFS
/dev/sda2 3266 9729 51922080 f W95 Ext'd (LBA)
/dev/sda5 3266 6121 22940788+ 7 HPFS/NTFS
/dev/sda6 6122 9729 28981228+ 7 HPFS/NTFS
omitting empty partition (5)
Disk /dev/sdb: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xd25bd25b
Device Boot Start End Blocks Id System
/dev/sdb1 1 2802 22507033+ 7 HPFS/NTFS
/dev/sdb2 2803 9730 55643679 f W95 Ext'd (LBA)
Partition 2 does not end on cylinder boundary.
/dev/sdb5 2803 6247 27671931 7 HPFS/NTFS
/dev/sdb6 6248 9730 27971685 7 HPFS/NTFS
The grub.cfg file looks like this (the main parts, perhaps):
menuentry "Ubuntu, Linux 2.6.31-17-generic" {
insmod ntfs
set root=(hd1,1)
search --no-floppy --fs-uuid --set 42cc3f0dcc3efb2d
loopback loop0 /ubuntu/
set root=(loop0)
linux /boot/vmlinuz-
loop=/ubuntu/
initrd /boot/initrd.
}
menuentry "Ubuntu, Linux 2.6.31-17-generic (recovery mode)" {
insmod ntfs
set root=(hd1,1)
search --no-floppy --fs-uuid --set 42cc3f0dcc3efb2d
loopback loop0 /ubuntu/
set root=(loop0)
linux /boot/vmlinuz-
loop=/ubuntu/
initrd /boot/initrd.
}
menuentry "Ubuntu, Linux 2.6.31-14-generic" {
insmod ntfs
set root=(hd1,1)
search --no-floppy --fs-uuid --set 42cc3f0dcc3efb2d
loopback loop0 /ubuntu/
set root=(loop0)
linux /boot/vmlinuz-
loop=/ubuntu/
initrd /boot/initrd.
}
menuentry "Ubuntu, Linux 2.6.31-14-generic (recovery mode)" {
insmod ntfs
set root=(hd1,1)
search --no-floppy --fs-uuid --set 42cc3f0dcc3efb2d
loopback loop0 /ubuntu/
set root=(loop0)
linux /boot/vmlinuz-
loop=/ubuntu/
initrd /boot/initrd.
}
I hope that this will help to sort it out. Thanks in anticipation.
-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Sam
Sent: 01 February 2010 21:17
To: <email address hidden>
Subject: RE: [Question #99346]: Security updates have fouled it up-AGAIN!!
Your question #99346 on yelp in ubuntu changed:
https:/
Status: Open => Needs information
Sam requested for more information:
> Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown -
block
Virtual Filesystem: unable to mount root filesystem on unknown block ...
means Grub can't mount /
Anyway there should appear more messages which may advise, to view them turn
off 'quiet splash'.
After editing the file update Grub and reboot.
Depending on which Grub is installed.
Grub_legacy:
/boot/grub/menu.lst
# defoptions=quiet splash
Grub_2:
/etc/default/grub
GRUB_CMDLINE_
> Via grub, I have to go back to a previous version
Previous version of what? Ubuntu version, Grub version?
How are you running Ubuntu at the moment, via Wubi, dualboot, multiboot?
Did you change anything about partitions?
Did you choose a former kernel image in boot menu and could boot with it?
Did you check with MemTest (also available from boot menu)?
Did you make a filesystem check via 'fsck'?
CLI:
sudo touch /forcefsck
## after next boot filesystem will be checked.
https:/
> which update caused this
Verify the day of the update. Synaptic has an option to search the history,
which is stored for xxx days, depending on your preferences.
Open Synaptic -> file -> history
btw. in case you have proposed repository enabled, you'll get packages for
testing purpose and you may disable it.
https:/
Which version of Grub are you using, Grub_legacy or Grub_2, may depend if
you upgrade from 9.04 to 9.10 or made fresh installation of 9.10.
https:/
CLI:
sudo grub-install -v
https:/
For further investigations, verify the output of:
sudo fdisk -l
cat /etc/fstab
sudo blkid
mount
--
To answer this request for more information, you can either reply to
this email or enter your reply at the following page:
https:/
You received this question notification because you are a direct
subscriber of the question.
|
Revision history for this message
|
#6 |
Thanks very much for info.
> version is 1.97, beta 4.
> This version of GRUB is at /etc/default/grub, but I am not sure how to "turn
> off" quiet splash.
It's Grub_2
First backup the file:
sudo cp /etc/default/grub /etc/default/
Open the file:
gksudo gedit /etc/default/grub
edit this line:
GRUB_CMDLINE_
change it to:
GRUB_CMDLINE_
save the file.
Update Grub:
sudo update-grub
Wubi and Grub_2 have issues:
https:/
http://
> corrupting update
Sorry, not sure which of posted packages could be the cause, rather was assuming grub-pc or kernel update, since you can't boot with 2.6.13-17 anymore.
## btw. where are kernel -15 and -16??
> grub.cfg file looks like this (the main parts, perhaps)
?? Where is WinXP?
Example grub.cfg:
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.
if [ -s /boot/grub/grubenv ]; then
have_grubenv=true
load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
saved_
save_env saved_entry
prev_saved_entry=
save_env prev_saved_entry
fi
if [ ${recordfail} = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.
### BEGIN /etc/grub.
set menu_color_
set menu_color_
### END /etc/grub.
### BEGIN /etc/grub.
### END /etc/grub.
### BEGIN /etc/grub.
menuentry "Ubuntu, Linux 2.6.31-15-generic" {
insmod ntfs
set root=(hd0,2)
search --no-floppy --fs-uuid --set 125c7c4e5c7c2f1b
loopback loop0 /ubuntu/
set root=(loop0)
linux /boot/vmlinuz-
initrd /boot/initrd.
}
menuentry "Ubuntu, Linux 2.6.31-15-generic (recovery mode)" {
insmod ntfs
set root=(hd0,2)
search --no-floppy --fs-uuid --set 125c7c4e5c7c2f1b
loopback loop0 /ubuntu/
set root=(loop0)
linux /boot/vmlinuz-
initrd /boot/initrd.
}
menuentry "Ubuntu, Linux 2.6.31-14-generic" {
insmod ntfs
set root=(hd0,2)
search --no-floppy --fs-uuid --set 125c7c4e5c7c2f1b
loopback loop0 /ubuntu/
set root=(loop0)
linux /boot/vmlinuz-
initrd /boot/initrd.
}
menuentry "Ubuntu, Linux 2.6.31-14-generic (recovery mode)" {
insmod ntfs
set root=(hd0,2)
search --no-floppy --fs-uuid --set 125c7c4e5c7c2f1b
loopback loop0 /ubuntu/
set root=(loop0)
linux /boot/vmlinuz-
initrd /boot/initrd.
}
### END /etc/grub.
### BEGIN /etc/grub.
### END /etc/grub.
### BEGIN /etc/grub.
menuentry "Microsoft Windows XP Home Edition (on /dev/sda2)" {
insmod ntfs
set root=(hd0,2)
search --no-floppy --fs-uuid --set 125c7c4e5c7c2f1b
drivemap -s (hd0) ${root}
chainloader +1
}
### END /etc/grub.
### BEGIN /etc/grub.
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.
Hence, please take a look in tutorials already mentioned and verify that XP is added in some of the scripts in
/etc/grub.d/
https:/
About 'Disk /dev/sdb' (output of fdisk -l)
#says
9729 cylinders
# but this line shows
/dev/sdb2 2803 9730 55643679 f W95 Ext'd (LBA)
Partition 2 does not end on cylinder boundary
# that it goes to 9730
# same here
/dev/sdb6 6248 9730 27971685 7 HPFS/NTFS
Honest, I'd leave Wubi since it's suboptimal and make it a real dualboot, e.g.
/
/home
swap
# with a separate /home partition you wont have any hassle with upgrades in the future.
https:/
|
Revision history for this message
|
#7 |
Thanks Sam, that solved my question.
|
Revision history for this message
|
#8 |
Thanks for the reply.
I take your final point about not using WUBI, but having had a previous bad
experience with the "usual" dual boot arrangement using GRUB (had to reload
Windows as well as Ubuntu), I will stick to Wubi. I have had a look at the
various tutorials and other info you have indicated, and have now got the
system back to a satisfactory situation.
Thanks again for your help.
R.
-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Sam
Sent: 02 February 2010 21:51
To: <email address hidden>
Subject: RE: [Question #99346]: Security updates have fouled it up-AGAIN!!
Your question #99346 on yelp in ubuntu changed:
https:/
Status: Open => Answered
Sam proposed the following answer:
Thanks very much for info.
> version is 1.97, beta 4.
> This version of GRUB is at /etc/default/grub, but I am not sure how to
"turn
> off" quiet splash.
It's Grub_2
First backup the file:
sudo cp /etc/default/grub /etc/default/
Open the file:
gksudo gedit /etc/default/grub
edit this line:
GRUB_CMDLINE_
change it to:
GRUB_CMDLINE_
save the file.
Update Grub:
sudo update-grub
Wubi and Grub_2 have issues:
https:/
http://
> corrupting update
Sorry, not sure which of posted packages could be the cause, rather was
assuming grub-pc or kernel update, since you can't boot with 2.6.13-17
anymore.
## btw. where are kernel -15 and -16??
> grub.cfg file looks like this (the main parts, perhaps)
?? Where is WinXP?
Example grub.cfg:
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.
if [ -s /boot/grub/grubenv ]; then
have_grubenv=true
load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
saved_
save_env saved_entry
prev_saved_entry=
save_env prev_saved_entry
fi
if [ ${recordfail} = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.
### BEGIN /etc/grub.
set menu_color_
set menu_color_
### END /etc/grub.
### BEGIN /etc/grub.
### END /etc/grub.
### BEGIN /etc/grub.
menuentry "Ubuntu, Linux 2.6.31-15-generic" {
insmod ntfs
set root=(hd0,2)
search --no-floppy --fs-uuid --set 125c7c4e5c7c2f1b
loopback loop0 /ubuntu/
set root=(loop0)
linux /boot/vmlinuz-
loop=/ubuntu/
initrd /boot/initrd.
}
menuentry "Ubuntu, Linux 2.6.31-15-generic (recovery mode)" {
insmod ntfs
set root=(hd0,2)
search --no-floppy --fs-uuid --set 125c7c4e5c7c2f1b
loopback loop0 /ubuntu/
set root=(loop0)
linux /boot/vmlinuz-
loop=/ubuntu/
initrd /boot/initrd.
}
menuentry "Ubuntu, Linux 2.6.31-14-generic" {
insmod ntfs
set root=(hd0,2)
search --no-floppy --fs-uuid --set 125c7c4e5c7c2f1b
loopback loop0 /ubuntu/
set root=(loop0)
linux /boot/vmlinuz-
loop=/ubuntu/
initrd /boot/initrd.
}
menuentry "Ubuntu, Linux 2.6.31-14-generic (recovery mode)" {
insmod ntfs
set root=(hd0,2)
search --no-floppy --fs-uuid --set 125c7c4e5c7c2f1b
loopback loop0 /ubuntu/
set root=(loop0)
linux /boot/vmlinuz-
loop=/ubuntu/
initrd /boot/initrd.
}
### END /etc/grub.
### BEGIN /etc/grub.
### END /etc/grub.
### BEGIN /etc/grub.
menuentry "Microsoft Windows XP Home Edition (on /dev/sda2)" {
insmod ntfs
set root=(hd0,2)
search --no-floppy --fs-uuid --set 125c7c4e5c7c2f1b
drivemap -s (hd0) ${root}
chainloader +1
}
### END /etc/grub.
### BEGIN /etc/grub.
# This file provides an easy way to add custom menu entries. Simply type
the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.
Hence, please take a look in tutorials already mentioned and verify that XP
is added in some of the scripts in
/etc/grub.d/
https:/
About 'Disk /dev/sdb' (output of fdisk -l)
#says
9729 cylinders
# but this line shows
/dev/sdb2 2803 9730 55643679 f W95 Ext'd (LBA)
Partition 2 does not end on cylinder boundary
# that it goes to 9730
# same here
/dev/sdb6 6248 9730 27971685 7 HPFS/NTFS
Honest, I'd leave Wubi since it's suboptimal and make it a real dualboot,
e.g.
/
/home
swap
# with a separate /home partition you wont have any hassle with upgrades in
the future.
https:/
--
If this answers your question, please go to the following page to let us
know that it is solved:
https:/
nswer_id=5
If you still need help, you can reply to this email or go to the
following page to enter your feedback:
https:/
You received this question notification because you are a direct
subscriber of the question.
