[Expired for lilo (Ubuntu) because there has been no activity for 60
days.]
--
failed kernel update followed by boot failure
https://bugs.launchpad.net/bugs/107249
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mai
Problem solved (again)
I used the liveCD from Gutsy to boot, and re-assembled the array using
info from this page:
http://ubuntuforums.org/showthread.php?t=408461
mounted the volume and then ran lilo following some information I found
here:
http://www.syrlug.org/contrib/boot-loaders.html#LI
Over the weekend some process caused me to need to reboot the machine -
which is a problem because the machine "doesn't have a valid boot
signature" as of the last kernel update. This is the third time a
failed semi-automatic kernel update has left the computer unusable (I
typically accept kernel
The latest kernel update has failed. This time the message that I
receive is "Fatal: First sector of /dev/sda1 doesn't have a valid boot
signature". This does not appear to have anything to do with the RAID -
mdstat shows all volumes are up:
Personalities : [raid1] [raid6] [raid5] [raid4]
m
So I added sdc1 back to the md0 array. This was enough to get me past
the errors in the upgrade and everything checks out ok. I guess I'll
really know when I next try to reboot.
It is not clear to me why sdc1 was dropped from the array ... I will
look for a log to see if I can find an explanatio
i think this has something to do with my RAID, for whatever reason.
"cat /proc/mdstat" produces the following output, suggesting md0 is not
fully functional.
Personalities : [raid1] [raid6] [raid5] [raid4]
md1 : active raid5 sdc2[0] sdb2[2] sdd2[1]
468856832 blocks level 5, 64k chunk,
With the last kernel update, I think I've encountered the problem again.
My guess is that this machine will not be able to reboot so I hope to
keep it running for long enough to provide any log files that might be
related. To start with, I'm attaching a screenshot which shows the
error message.
*
The latest kernel update worked fine so I am assuming that the problem
no longer exists. This report should be closed.
--
failed kernel update followed by boot failure
https://bugs.launchpad.net/bugs/107249
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
I have re-installed using the release version.
I did save all of the contents from my /var/log directory so any files
that would have been there are still available.
Also - I recovered my firefox session where I was searching for an
answer after the upgrade failure and before the reboot. The str
** Changed in: lilo (Ubuntu)
Sourcepackagename: update-manager => lilo
--
failed kernel update followed by boot failure
https://bugs.launchpad.net/bugs/107249
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
the /var/log/dist-upgrade directory is empty.
BTW: mounted md0 by the following steps:
installed mdadm (not positive this was necessary)
created directory /mnt/md0
typed "sudo mount -t auto /dev/md0 /mnt/md0"
--
failed kernel update followed by boot failure
https://bugs.launchpad.net/bugs/
Installing RAID support on the live CD should work, no? I'm not a expert
for RAID, but the livecd does allow installing of packages, changing
sources.list etc.
--
failed kernel update followed by boot failure
https://bugs.launchpad.net/bugs/107249
You received this bug notification because you ar
Right now I don't have access to md0 which contains that directory. If
I could install RAID support after booting from the live CD, then I
might be able to access these files.
--
failed kernel update followed by boot failure
https://bugs.launchpad.net/bugs/107249
You received this bug notificati
Thanks for your bugreport.
Can you please attach the files in /var/log/dist-upgrade ? This will
help us diagnose the problem.
Thanks,
Michael
** Changed in: update-manager (Ubuntu)
Status: Unconfirmed => Confirmed
Target: None => later
** Changed in: update-manager (Ubuntu)
** Changed in: update-manager (Ubuntu)
Sourcepackagename: None => update-manager
--
failed kernel update followed by boot failure
https://bugs.launchpad.net/bugs/107249
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bug
I expect to install the release version of Feisty tomorrow evening -
I've decided that having a running system is far more important than
preserving the configuration data stored on /etc/openvpn, /etc/apache2,
and /var (addressing the repair/restore install issue). However, I
still fear that the u
** Description changed:
I installed feisty from the 4/14/07 alternate CD (to support software
RAID) and was able to boot thanks to the fix to bug #103177.
The system worked fine for a day or so - then the update manager
provided kernel 2.6.20-15, which was not able to install (not sure
** Description changed:
I installed feisty from the 4/14/07 alternate CD (to support software
- RAID) and was able to boot thanks to the fix to bug #103177:
-
- https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/103177
+ RAID) and was able to boot thanks to the fix to bug #103177.
The
18 matches
Mail list logo
