On Thu, Jul 19, 2018 at 12:47 PM Brad Rogers wrote:
> On Thu, 19 Jul 2018 18:14:19 +0200
> deloptes wrote:
>
> >why not use something more decent like ext3 or ext4? we are in 2018 ;-)
>
> (your smiley noted)
> Ken gave no indication of time-frame, other than in the past. Could've
> been last we
On Thu, Jul 19, 2018 at 06:45:16PM -0400, Felix Miata wrote:
Cheap is a relative term. It's only "cheap" if it's cheap enough for a
particular context to enjoy. Even if a HD was only a dollar a TB, it wouldn't be
cheap to someone with 0 dollars.
Well, you can't buy any storage with zero dollars
deloptes composed on 2018-07-20 00:00 (UTC+0200):
> Felix Miata wrote:
>> 1: /boot is functionally readonly except during kernel installation and
>> removal
> not really an argument - the system did not boot for this reason
>> 2: journals consume disk space
> not really an argument - the syste
Felix Miata wrote:
> 1: /boot is functionally readonly except during kernel installation and
> removal
>
not really an argument - the system did not boot for this reason
> 2: journals consume disk space
not really an argument - the system did not boot for this reason and space
in MBs is cheap
deloptes composed on 2018-07-19 18:14 (UTC+0200):
> why not use something more decent like ext3 or ext4? we are in 2018 ;-)
1: /boot is functionally readonly except during kernel installation and removal
2: journals consume disk space
I would be spending an enormous amount of time rescuing file
On Thu, 19 Jul 2018 18:14:19 +0200
deloptes wrote:
Hello deloptes,
>why not use something more decent like ext3 or ext4? we are in 2018 ;-)
(your smiley noted)
Ken gave no indication of time-frame, other than in the past. Could've
been last week, could've been twenty years ago.
--
Regards
Kenneth Parker wrote:
> My worst, was kind of "mild", though scary: I had to rebuild /boot (on
> ext2), because the last action was placing a copy of the Linux Kernel on
> /boot.
why not use something more decent like ext3 or ext4? we are in 2018 ;-)
regards
On Thu, Jul 19, 2018, 8:09 AM Brad Rogers wrote:
> On Thu, 19 Jul 2018 07:56:34 -0400
> Kenneth Parker wrote:
>
> Hello Kenneth,
>
> >My worst, was kind of "mild", though scary: I had to rebuild /boot (on
> >ext2), because the last action was placing a copy of the Linux Kernel on
> >/boot.
>
>
On Thu, 19 Jul 2018 07:56:34 -0400
Kenneth Parker wrote:
Hello Kenneth,
>My worst, was kind of "mild", though scary: I had to rebuild /boot (on
>ext2), because the last action was placing a copy of the Linux Kernel on
>/boot.
It was the fear of such an issue (an inability to boot) that finally
On Thu, Jul 19, 2018, 2:20 AM Brad Rogers wrote:
>
> Worst I had happen as a result of power failure was that disk the
> journal couldn't recover everything required, such that sector errors
> were reported on every boot. A reformat got around that. Tiresome, but
> not fatal.
>
My worst, was
On Fri, Dec 12, 2008 at 01:01:08PM +0800, rjubio wrote:
> I found a file in the /etc partition called nologin. I just removed it.
> Voila! I got connected.
The root problem really isn't solved. Who put the nologin file that
said powerfail (or whatever) there in the first place? What was its
tim
On Fri, Dec 12, 2008 at 12:55:25PM +0800, Rod James Bio wrote:
> Well that's a problem. I am using a Mac X server that doesnt have a VGA
> behind it. What I tried though was to unmount the harddisk manually and
> mount it on another X server that I have. I know that a lock file of some
> sort has t
I found a file in the /etc partition called nologin. I just removed it.
Voila! I got connected.
Thanks for the help
Jeff D wrote:
On Fri, 12 Dec 2008, rjubio wrote:
I am experiencing some kind of error regarding a recent power failure in our
campus.
When I try sshing to on of our server
Well that's a problem. I am using a Mac X server that doesnt have a VGA
behind it. What I tried though was to unmount the harddisk manually and
mount it on another X server that I have. I know that a lock file of some
sort has to be deleted to fix the problem.
On Fri, Dec 12, 2008 at 12:35 PM, Jef
On Fri, 12 Dec 2008, rjubio wrote:
> I am experiencing some kind of error regarding a recent power failure in our
> campus.
>
> When I try sshing to on of our server I get an error message:
>
> POWER FAILURE
> then I get thrown back to the login prompt.
>
> Any suggestions how to go on this.
> Tha
Guillaume TESSIER wrote:
"power failure during upgrade"
Damn...
Actually, it was faulty hardware. My fault entirely.
Maybe while being disapointed and sending all damnation on the power
plant, you forgot to modify your sources.lists
No. I shouldn't have to touch these. They still point
Joe Mc Cool wrote:
in order to upgrade from woody to sarge I did:
apt-get update
apt-get dist-upgrade
off it went, but unfortunately I had a power failure during the
upgrade and my system got hosed. (I repeated the above steps, but my
system would then boot only with a ro root filesys
nal Message-
> From: Didi Damian [mailto:[EMAIL PROTECTED]
> Sent: Saturday, 10 July 1999 4:51
> To: Patrick Kirk
> Cc: Debian User
> Subject: Re: Power failure
>
>
> Patrick Kirk [EMAIL PROTECTED] wrote:
> > Hi all,
> >
> > A fuse blew last night taking
Patrick Kirk [EMAIL PROTECTED] wrote:
> Hi all,
>
> A fuse blew last night taking out the power supply to the server with my new
> debian linux installation.:-(
>
> On reboot this morning, the second NIC wasn't present so I had to modprobe
> /lib/...tulip.o, then ifconfig eth1, then route add, th
19 matches
Mail list logo
