24 Apr
2004
24 Apr
'04
8:29 p.m.
that's what i'm thinkin - I don't care i'll rebuild - but I do want to
know
if anyone has some advice on how I might be able to at least recover some
data - I have some backups, some stuff can be rebuilt, but there are like
four tracks in my latest ardour project that I would LOVE to get rescued...
hmmm...maybe DOS will see it? oh jeeze.
I'm wondering too HOW the harddrive hosed itself, because it's pretty
frickin new (got it last fall) - I did move though - so maybe it bumped - or
maybe ardour zapped it *laugh* damn you Paul! ;)
----- Original Message -----
From: "Jan Depner" <eviltwin69(a)cableone.net>
To: "A list for linux audio users" <linux-audio-user(a)music.columbia.edu>
Sent: Saturday, April 24, 2004 2:57 PM
Subject: Re: [linux-audio-user] Ardour Crash + can't boot
Man, that doesn't sound good. I believe at this
point that you are the
proud owner of a smoked system. The disk may not be physically bad but
it sounds like it might be. Maybe someone else has more insight into
this though.
Jan
On Sat, 2004-04-24 at 18:07, Aaron Trumm wrote:
> Well - interesting.
>
> Thanks to these replies, I learned to use "linux single" at that boot:
> prompt
>
> That got me in a shell, along with this error:
>
> The superblock could not be read or does not describe a correct ext2
> filesytem. If the device is valid and it really contains an ext2
filesystem
> (and not swap or ufs or something else), then the
superblock is corrupt,
and
> you might try running e2fsck with an alternate
superblock:
> e2fsck -b 8193 <device>
>
> fsck.ext3: Filesystem revision too high while trying to open /dev/hda2
>
> eek, I say. so I said oh alright and entered:
> e2fsck -b 8193 /dev/hda2
>
> and got the same superblock error
>
> so I referred to Jan's email and typed:
> fsck /dev/hda2
>
> and got the same superblock error
>
> so I said hmm and tried:
> fsck /dev/hda
>
> and got a similar superblock error only it mentioned ext2 - odd?
>
>
> and that's where I'm stuck currently - worried that I've got a hardware
> malfunction :)
>
>
> here's the caveat: last night before hearing back from anyone, I, in my
> grand wise impatience, booted with the red hat cd and entered the rescue
> mode. there, per instructions I found in an archived email, I attempted
to
> mount hda2 and it said the device doesn't
exist. eek. so then, in my
GRAND
> GRAND wise impatience, I decided to let Red Hat
CD install a new OS,
while
> keeping all partitions and just using free space.
during this install
> process, I got error messages while reading hda - i hobbled through the
> process, let it reboot, and came out with the same kernel panic, which
led
> me to believe I was having a harddisk screw up.
then I went to bed and
got
> up and tried the above.
>
> Aaron will be backing up more often from this day forward. :)
>
> ideas?
>
> ----- Original Message -----
> From: "Jan Depner" <eviltwin69(a)cableone.net>
> To: "A list for linux audio users"
<linux-audio-user(a)music.columbia.edu>
> Sent: Saturday, April 24, 2004 3:34 AM
> Subject: Re: [linux-audio-user] Ardour Crash + can't boot
>
>
> > If you boot in single user mode you should only get that if you're
> > trying to fsck the root partition. AFAIK you kinda have to ignore it
in
> > that case. I don't know what recourse
you have in the case of a hosed
> > root partition. I've never had a problem with fsck'ing the root
> > partition though (that covers about 16 years of UNIX sysadmin (and 11
of
Linux)). Of course, it could blow up on me the next
time I have to do
it ;-) Man, you're up early today Ron.
Jan
On Sat, 2004-04-24 at 05:22, R Parker wrote:
Jan,
Do you ignore the warning that running fsck on a
mounted partition can cause serious damage? I used to
ignore it and never had a problem but as my collection
of valuable material grows I become more paranoid. I
imagine Aaron will see that message.
ron
--- Jan Depner <eviltwin69(a)cableone.net> wrote:
> Aaron,
>
> Sounds strange. If you are using LILO to boot
> press <Ctrl>-x at the
> splash screen and then enter "linux single" at the
> boot: prompt to boot
> into single user mode. If you are using GRUB you
> can press "e" when the
> GRUB splash screen comes up. Highlight your normal
> boot line with the
> arrow keys, press "e" again, add " single" to the
> end of the boot line,
> press Enter, press "b". This will boot you into
> single user mode. At
> that point you can look around your system and see
> if anything is
> amiss. Many times just getting it to boot into
> single user mode and
> then doing a clean reboot will clear up any problems
> you have. If
> you're getting a message about having to manually
> fix a disk partition
> you can manually fsck a disk partition by entering
> "fsck
> /dev/hdWHATEVER". Usually I just agree to let it
> fix whatever is wrong
> at that point since anything more involved is
> "magic". Good luck.
>
>
> Jan
>
>
>
> On Sat, 2004-04-24 at 04:57, Aaron Trumm wrote:
> > reposting this cuz I ALWAYS forget to make the
> messages plain text from my
> > windows machine:
> >
> > Hello all - this has actually become a general
> problem, but I think it was
> > caused by Ardour, so I'm cross posting on linux
> audio and the ardour lists
> >
> > I'm running Red Hat and the latest ardour from
> Planet CCRMA which I think is
> > 0.9beta11.2-1 - I was recording a take, and upon
> pushing stop Ardour
> > crashed - a similar has happened many times with
> this version, actually
> > pretty much every time - after the take, it gives
> me a memory error, I click
> > ok, ardour exits, I go back, but it kept the take.
> >
> > but this time, it crashed without that, i started
> ardour again, the take
> > WASN'T there, and then ardour either froze or
> crashed I can't remember which
> > cuz I was in session so it was hectic, and I
> needed to reboot manually and
> > so I did, and now, though, it won't boot - it
> hangs and says "kernel panic.
> > no init found. try passing the init= option"
> >
> > I can provide more details if needed - I think the
> kernel is also the latest
> > planet kernel - but from what I've been able to
> find I don't think it
> > matters.
> >
> > so I grabbed my emergency boot disk, or what I
> think is my emergency boot
> > disk, because I have never used it, and reset, and
> I get what I'm sure is a
> > familiar prompt to most, the 'ol
> >
> > boot:
> >
> > and it's telling me to hit return or wait ten
> seconds to boot from /dev/hda2
> > (hmmm - is that where the boot loader really is on
> my system? not sure) -
> > and that I can "type "linux <params>", and press
> <return> if I want to
> > override the defaults
> >
> > now I know nothing about these params and I'm more
> familiar with a dos boot
> > disk where i shove that thing in and reboot and
> I'm looking at a dos prompt
> > even if my harddrive is totally wanked.
> >
> > what I've read has told me to boot up and edit
> some files - fstab maybe?
> > but uh - *blush* - how can I get to a danged
> prompt?
> >
> >
> > for the ardour list: does this sound familiar, is
> this version of ardour
> > known to do this kind of thing?
> >
>
>
__________________________________
Do you Yahoo!?
Yahoo! Photos: High-quality 4x6 digital prints for 25ยข
http://photos.yahoo.com/ph/print_splash