RE: Broken System After Update[Solved]

2012-02-05 Thread Ogya Chief
Hi There, I found a solution by Michael Tokarev which addressed BusyBox bug# 646284. It required updating BusyBox and running update-initramfs in a chroot environment. Thank you all for your suggestions. Regards, Ogya

RE: Broken System After Update

2012-02-05 Thread Ogya Chief
From: carlo.bore...@gmail.com Date: Sun, 5 Feb 2012 02:09:18 -0300 Subject: Re: Broken System After Update To: debian-user@lists.debian.org [...] Yes, I have /usr and /var on separate partitions and both were required to be mounted before the command worked. I tried your alternative

Re: Broken System After Update

2012-02-04 Thread Carlo Borelli
> > [...] > > Yes, I have /usr and /var on separate partitions and both were required to > be mounted before the command worked. I tried your alternative solution as > well but none fixed my problem. I am convinced that my problem is not a > corrupt initrd. I am at a loss as to what to do next to

RE: Broken System After Update

2012-02-04 Thread Ogya Chief
> > > # /usr/sbin/update-initramfs -u -k $(uname -r) -u > > It is also possible that a broken initrd is not the problem and that > the problem is elsewhere on your system > > > This is what I did: > > Thank you for the very nice and complete description of what you did! > That was very go

Re: Broken System After Update

2012-02-04 Thread Bob Proulx
Ogya Chief wrote: >No init found. Try passing init= bootarg Ouch. > I googled for solution and this is the solution I got. The solution > talks about chrooting and running the following command: > update-initramfs -u -k $(uname -r) -u Seems reasonable. This should rebuild the initrd (in

RE: Broken System After Update

2012-02-04 Thread Ogya Chief
> To: debian-user@lists.debian.org > From: hvw59...@care2.com > Subject: Re: Broken System After Update > Date: Sat, 4 Feb 2012 15:11:03 -0600 > > Ogya Chief wrote: > > Hi All, > > > > I am running Sid and a couple of months ago I updated my system > &

Re: Broken System After Update

2012-02-04 Thread hvw59601
Ogya Chief wrote: Hi All, I am running Sid and a couple of months ago I updated my system including the kernel. After restarting my machine, I realised that my system was broken. Whenever I start the machine, I get a message lilke this: No init found. Try passing init= bootarg BusyBox

Broken System After Update

2012-02-04 Thread Ogya Chief
Hi All, I am running Sid and a couple of months ago I updated my system including the kernel. After restarting my machine, I realised that my system was broken. Whenever I start the machine, I get a message lilke this: No init found. Try passing init= bootarg BusyBox v1.19.2 (Debian 1:1.