Re: Debian slug won't reboot (steady amber)--ideas?
- So, after some trawling, I came across some stuff that pointed me to
http://www.nslu2-linux.org/wiki/HowTo/ResetSysConf (Using netsetman -
http://www.netsetman.com/as helped as an easy way to change my ip
between the 3 settings I needed).
Following the instructions here, I was able to get the Linksys
firmware installed, login change the settings then get slugOS
installed and back running again.
--- In email@example.com, "montyny1" <monty@...> wrote:
> Mmm, wonder if anyone has an answer to this? It seems this is what's
> happening to my slug now too. After leaving it for a long tmie, it
> comes up with a steady yellow and no network led.
> I had problems, reflashed several times. Latest was Debian/NSLU2
> Experimental 5.0beta2.
> --- In firstname.lastname@example.org, Victor Putz <vputz@> wrote:
> > I've got a slug running Debian (used the debian installer to install
> > Unfortunately I lost the first attempt at this email, which had a
> bit more
> > data, but the upshot of it is that when a drive went dead (my "data"
> > periodically goes offline) I disconnected the wrong one (the system
> > thus forcing a reboot.
> > The reboot never finishes--I get the beginnings of a boot sequence
> > of green flashy LEDs, then system/ready goes red for a bit, then
> > and just stays steady amber). The system drive even flashes to note
> > it's being accessed, but only for a bit--and then it stays as steady
> as the
> > amber light.
> > I've connected the drive to a laptop, but there are no new entries in
> > /var/log/* (time stamps remain the same). I've tried ResetSysConf
> > RedBoot, but it didn't make any difference. I did reflash with the
> new .bin
> > file mentioned on the debian upgrade page, because my /boot directory
> > contained what looked like the right stuff (2.6.18 kernel,
> apex.flash, etc).
> > Still, not much progress. The only thing I haven't tried yet is
> > the drive from a Linux box, but while I'd worry about a forced
> > not sure that's the case since the drive doesn't look very active
> after the
> > "hung boot"--but I could be wrong.
> > Any ideas on how to repair this if it doesn't turn out to be a fsck?