What : BBS - The Documentary film
Where: HoloDek, Hampton, NH
Dates: Wed July 9, 16, 23, 30
Time : 7:00 PM
The Ubuntu Local Community Team of NH is presenting "BBS: The
Documentary", as a four-part film series, Wednesdays evenings
throughout July.
The documentary covers the history of BBSes -
On 7/15/08, Jarod Wilson <[EMAIL PROTECTED]> wrote:
> Its all the same bring-up bits, but passing in the 'rescue' flag should
> replace all "installer" strings with "rescue environment" ... Could be
> ... that particular string doesn't get replaced...
Google results lead me to believe that is th
On 7/15/08, Ben Scott <[EMAIL PROTECTED]> wrote:
> Yah, me too. If you're going to be wiping things clean anyway, you
> may want to run some basic confidence tests on the system. I suggest:
Oh, and if your computer hardware OEM/VAR/etc provides any
diagnostics, run those, too.
-- Ben
___
On 7/15/08, Jim Kuzdrall <[EMAIL PROTECTED]> wrote:
>Curious. Why not use the non-destructive badblocks write option -n?
Background: The "non-destructive write test" goes through the disk,
one block at a time, reading the existing contents into memory, then
writing and reading test patterns
On Tuesday 15 July 2008 19:08, Ben Scott wrote:
> Run a destructive write test on the disk. (WARNING: This will
> *DESTROY ALL DATA* on the disk.) Boot a working rescue/install CD
> and get a shell prompt, and then run "badblocks -s -v -w /dev/foo",
> where "foo" is the name of the whole-disk
On Tue, 2008-07-15 at 19:28 -0400, Tom Buskey wrote:
>
>
> On Tue, Jul 15, 2008 at 3:26 PM, Jarod Wilson <[EMAIL PROTECTED]>
> wrote:
> On Tue, 2008-07-15 at 15:02 -0400, Ben Scott wrote:
> > On Tue, Jul 15, 2008 at 2:33 PM, Labitt, Bruce
> > <[EMAIL PROTECTED]> wrote:
>
On Tue, 2008-07-15 at 18:43 -0400, Ben Scott wrote:
> On Tue, Jul 15, 2008 at 5:25 PM, Jarod Wilson <[EMAIL PROTECTED]> wrote:
> > Ew, that sounds... bad. Although it sounds like it didn't actually go
> > into the rescue env. but rather tried to install, based on the "install
> > exited abnormally"
On Tue, Jul 15, 2008 at 3:26 PM, Jarod Wilson <[EMAIL PROTECTED]> wrote:
> On Tue, 2008-07-15 at 15:02 -0400, Ben Scott wrote:
> > On Tue, Jul 15, 2008 at 2:33 PM, Labitt, Bruce
> > <[EMAIL PROTECTED]> wrote:
> > > I was running as a user. NOT root.
> >
> > Worrysome.
> >
> > Though, come to
On Tue, Jul 15, 2008 at 6:41 PM, Labitt, Bruce
<[EMAIL PROTECTED]> wrote:
> I don't have a problem with a fresh start ... except that I have
> no idea what really hosed me to begin with.
Yah, me too. If you're going to be wiping things clean anyway, you
may want to run some basic confidence tes
On Tue, Jul 15, 2008 at 5:21 PM, Dan Miller <[EMAIL PROTECTED]> wrote:
> Is there a store locally that tailors to networks?
Define "locally". The usual suspects are Graybar, Anixter, and
Wesco. I know there are branches in the greater NH area.
I can also say SmartHome (http://www.smarthome.
On Tue, Jul 15, 2008 at 5:25 PM, Jarod Wilson <[EMAIL PROTECTED]> wrote:
> Ew, that sounds... bad. Although it sounds like it didn't actually go
> into the rescue env. but rather tried to install, based on the "install
> exited abnormally" message.
I think part of the "installer" is still in cha
On Tue, Jul 15, 2008 at 4:25 PM, Labitt, Bruce
<[EMAIL PROTECTED]> wrote:
> It installed some ata_piix ?? stuff
That's the driver module for your motherboard's SATA adapter.
Normal. (The name is vestigial; "PIIX" was some old Intel IDE
controller chipset, circa 1995.)
> then back to black scre
Right now, I don't have another working running system (linux) at work.
I don't have a problem with a fresh start, (time to recreate everything
is a pain) except that I have no idea what really hosed me to begin
with. That is the part that is scary...
Bruce
-Original Message-
From: [EMAI
On Tue, Jul 15, 2008 at 5:56 PM, Labitt, Bruce
<[EMAIL PROTECTED]> wrote:
> I'm thinking at this point perhaps I should detach the problem 80GB disk
> and fresh install 5.2 on the 300GB disk.
That is likely to be the easiest way. At the very least, it will
make trouble-shooting the problem disk
I'm thinking at this point perhaps I should detach the problem 80GB disk
and fresh install 5.2 on the 300GB disk. Afterwards I could attach the
old 80GB disk and see if I can extract anything. Does this sound like
it would be the safest course of action at this point?
-Original Message-
How many physical hard disk drives are part of this system?
[Labitt, Bruce] Two. The first drive 80GB has the system on it.
Are there any hardware RAID controllers or such in use?[Labitt, Bruce]
no.
> It appears I can access /data and its contents.
Appearances can be deceiving. Have you run
On Tue, 15 Jul 2008 17:21:55 -0400,
Dan Miller wrote:
> Is there one store were I could get about a 6U swinging rack, cat6
> patch panel, cat6 spools, cat6 plugs, and then coax plugs and patch
> panel or pluggable patch panel?
Check out LightYear Cable in Manchester, (603) 647-5920.
http://www.l
PHP, MySQL and Apache
Dojo Using the Dojo Javascript Library to build Ajax Applications
--
Lloyd Kvam
Venix Corp
DLSLUG/GNHLUG library
http://dlslug.org/library.html
http://www.librarything.com/catalog/dlslug
http://www.librarything.com/rsshtml/recent/dlslug
http://www.librarything.com/rss/rece
On Tue, 2008-07-15 at 16:25 -0400, Labitt, Bruce wrote:
> I just ran the SL5.2 CD1 and typed linux rescue. It ran a bunch of
> stuff and got to a colored (bright blue with red writing) display. It
> installed some ata_piix ??
It loaded the ata_piix module, as it detected you had a controller
dri
I'm thinking about doing some wiring of data, phone, and coax and want a
rack to for all this stuff.
I can find various parts but some don't appear to be for a rack unit. Is
there a store locally that tailors to networks? I'm looking for cat6
plugs and patch panels.
I would also like a RF di
I just ran the SL5.2 CD1 and typed linux rescue. It ran a bunch of
stuff and got to a colored (bright blue with red writing) display. It
installed some ata_piix ?? stuff then back to black screen a long list
of hex addresses? then
install exited abnormally [1/1]
sending termination signals...don
On Tue, 2008-07-15 at 15:02 -0400, Ben Scott wrote:
> On Tue, Jul 15, 2008 at 2:33 PM, Labitt, Bruce
> <[EMAIL PROTECTED]> wrote:
> > I was running as a user. NOT root.
>
> Worrysome.
>
> Though, come to think of it, aren't some disc-recording types of
> programs normally installed SUID root
On Tue, Jul 15, 2008 at 2:33 PM, Labitt, Bruce
<[EMAIL PROTECTED]> wrote:
> I was running as a user. NOT root.
Worrysome.
Though, come to think of it, aren't some disc-recording types of
programs normally installed SUID root?
> There maybe a typo in there, I had to copy it from one screen t
Bill,
I was running as a user. NOT root.
#cat /etc/fstab
/dev/VolGroup00/LogVol00/ ext3defaults
1 1
LABEL=/boot /boot ext3
defaults1 2
tempfs /dev/shmtmpfs defaults
On Tue, 2008-07-15 at 13:42 -0400, Ben Scott wrote:
> On Tue, 2008-07-15 at 11:05 -0400, Labitt, Bruce wrote:
> >> Attempt to read block from filesystem resulted in short read while
> >> trying to open /var.
>
> On Tue, Jul 15, 2008 at 11:59 AM, Jarod Wilson <[EMAIL PROTECTED]> wrote:
> > You need
On Jul 15, 2008, at 11:01, John Abreau wrote:
> It sounds like the filesystem is thoroughly hosed. Based on the
> symptoms
> you describe, my first guess would be that you mistakenly pointed
> K3b at
> your hard drive instead of the DVD drive.
Bruce, were you running k3b as root? We can sav
On Tue, Jul 15, 2008 at 11:54 AM, Michael ODonnell
<[EMAIL PROTECTED]> wrote:
> ... unless you want to do (or more likely, pay for) some
> nasty by-hand salvage... :-/
That actually raises a good point: If this filesystem had valuable
unique data on it, and you don't have backups, then you shou
On Tue, Jul 15, 2008 at 12:28 PM, John Abreau <[EMAIL PROTECTED]> wrote:
> Perhaps. Or maybe k3b only started scribbling on the /var partition, then
> the machine rebooted when something critical in /var was stomped on.
Or maybe k3b thought /dev/sda3 (or whatever) was the block device to
write t
On Tue, 2008-07-15 at 11:05 -0400, Labitt, Bruce wrote:
>> Attempt to read block from filesystem resulted in short read while
>> trying to open /var.
On Tue, Jul 15, 2008 at 11:59 AM, Jarod Wilson <[EMAIL PROTECTED]> wrote:
> You need to give it a block device, not a file system path. i.e., you
>
On Tue, 15 Jul 2008, Michael ODonnell wrote:
>
>
>> my first guess would be that you mistakenly pointed K3b at your
>> hard drive instead of the DVD drive.
>
> I'd think the damage would be much worse if that were the case,
> so my guess is that some b0rken kernel code (or maybe a HW
> problem) co
> I would definitely recommned booting from external media (DVD)
> and checking *all* the filesystems. There may be undetected
> corruption elsewhere on your disk. And you can't check the root
> filesystem of the running system.
Good advice. Note that you can sometimes manage to fsck even
the
On Tue, Jul 15, 2008 at 11:12 AM, Labitt, Bruce
<[EMAIL PROTECTED]> wrote:
> Thanks Jarod. Hmm, I only have a 5.1 DVD right now. Will that work?
It should. The on-disk filesystem format is the same.
I would definitely recommned booting from external media (DVD) and
checking *all* the files
You need to give it a block device, not a file system path. i.e., you
need to pass /dev/foo to fsck, not /var.
On Tue, 2008-07-15 at 11:05 -0400, Labitt, Bruce wrote:
> I have been able to log into root in cli mode.
>
> I tried fsck -cvfn /var and got
>
> Attempt to read block from filesystem r
> my first guess would be that you mistakenly pointed K3b at your
> hard drive instead of the DVD drive.
I'd think the damage would be much worse if that were the case,
so my guess is that some b0rken kernel code (or maybe a HW
problem) corrupted some memory that happened to correspond to
metada
It sure looks like k3b was involved. However, k3b only gave me the
addresses for the two optical drives I have. ??
-Original Message-
From: John Abreau [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 15, 2008 11:01 AM
To: Labitt, Bruce
Cc: gnhlug-discuss@mail.gnhlug.org
Subject: Re: Syste
Yep, fsck would be the place to start. Look in /mnt/sysimage/etc/fstab
to see what physical device /var is and fsck that bad boy. I'd start
with just a simple 'fsck /dev/sdaX' and go from there.
On Tue, 2008-07-15 at 11:12 -0400, Labitt, Bruce wrote:
> Thanks Jarod. Hmm, I only have a 5.1 DVD ri
On Tue, July 15, 2008 10:18 am, Labitt, Bruce said:
> What tools are available for recovery of a linux system? I have no idea
> what happened - but my system took a dump. SciLinux5.2 (RHEL5.2). I
> make it through the text mode then go into the x detail mode. I get a
> lot of daemons failing a
Thanks Jarod. Hmm, I only have a 5.1 DVD right now. Will that work?
Or do I have to create a 5.2 dvd on another machine?
As for repairs they would be fsck?
Thanks,
Bruce
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jarod
Wilson
Sent: Tuesday, July 1
I have been able to log into root in cli mode.
I tried fsck -cvfn /var and got
Attempt to read block from filesystem resulted in short read while
trying to open /var.
What does that mean? more importantly, what is the recommended course
of action?
-Bruce
-Original Message-
From: [EMAI
Thanks. It appears that I cannot descend into /var, but I can go into
other root directories.
What would be the recommended fsck options?
#fsck -CV /var -n ?
-Bruce
From: Mark Greene [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 15, 2008 10
On Tue, 2008-07-15 at 10:34 -0400, Mark Greene wrote:
> I'd start by booting it off of the system CD, run fsck on /var and see
> how much of it is still intact. Then check the system logs for hard
> drive and PCI errors.
i.e., insert Scientific Linux 5.2, CD1 (or DVD), and boot it like so:
boo
I'd start by booting it off of the system CD, run fsck on /var and see how
much of it is still intact. Then check the system logs for hard drive and
PCI errors.
Good luck with it.
mark
On Tue, Jul 15, 2008 at 10:18 AM, Labitt, Bruce <
[EMAIL PROTECTED]> wrote:
> What tools are available for re
What tools are available for recovery of a linux system? I have no idea
what happened - but my system took a dump. SciLinux5.2 (RHEL5.2). I
make it through the text mode then go into the x detail mode. I get a
lot of daemons failing and the odd lines that say stuff like:
touch cannot touch /va
"Ben Scott" <[EMAIL PROTECTED]> writes:
> > kernel /vmlinuz-1.6.20-1.2944.fc6 ro root=/dev/VolGroup00/LogVol00 rhgb
> quiet irqpoll
>
> You've got a typo in the above. "1.6.20" should be "2.6.20". If
> that's your actual kernel command (and not merely a transcription
> error), that'
44 matches
Mail list logo
