24 Apr
2004
24 Apr
'04
11:15 p.m.
hmmm good idea - although I'm not comfortable with ANY of those tools -
gonna have to get one - or make one, which means I gotta get this machine to
boot if I want to be able to burn a CD
hmmm
what I'm thinking is that something is corrupted, hopefully not physically,
on my big harddrive. so I think what I'm gonna do is take it out, get the
system going with the other drive (smaller), cuz I don't THINK it's screwed
(although I could be wrong) - then make a cd of one of those and maybe try
my real goal as always is two fold - learn new stuff, expand skillset, but
also be able to work - but right now my goal is to get the data (especially
these tracks i just recorded and hadn't backed up), store it, reinstall from
scratch, wipe, clean, wipe butt, shower, reinstall audio apps, get data back
and be back on track.
hmm deee dooommmmm - man it was screwy because this crash happened in the
middle of the first session with any other players in my new
studio/apartment - DOH!
----- Original Message -----
From: "Mark Knecht" <markknecht(a)comcast.net>
To: "A list for linux audio users" <linux-audio-user(a)music.columbia.edu>
Sent: Saturday, April 24, 2004 4:54 PM
Subject: Re: [linux-audio-user] Ardour Crash + can't boot
Aaron,
Bummer. Disk problems.
I see you've gotten a large number of responses. I haven't read too
many of them yet, but my input would be to reboot using a CD-based
LiveCD, like Knoppix, Damn Small Linux or Dynebolic. These give you
access to disks so you can do some checking. From here you can run all
the normal tools (parted, fdisk, cfdisk - whatever you are most
comfortable with) and you can determine if it's the partition that's
messed up or the partition table.
If you have another hard disk hanging around then you might rebuild
the system using it and not this drive. Once that system is up and going
you could then do some more work with the drive if you needed to.
Sorry to hear about your problems.
- Mark
On Sat, 2004-04-24 at 02: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
ure) -
> 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?