24 Apr
2004
24 Apr
'04
6:06 a.m.
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?
24 Apr
24 Apr
8:08 a.m.
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?
8:29 a.m.
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:
__________________________________
Do you Yahoo!?
Yahoo! Photos: High-quality 4x6 digital prints for 25�
http://photos.yahoo.com/ph/print_splash
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?
8:37 a.m.
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:
__________________________________
Do you Yahoo!?
Yahoo! Photos: High-quality 4x6 digital prints for 25¢
http://photos.yahoo.com/ph/print_splash 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?
2:37 p.m.
On 24 Apr 2004 05:34:38 -0500
Jan Depner <eviltwin69(a)cableone.net> wrote:
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.
remount the root partition read only.. see man mount.. i think that should lessen the
probability of damage.. after fsck just reboot, do not remount ro..
flo
P.S.: i'm not sure though...
--
Fm7 Bbm7 Eb7b9 Abmaj7 Dbmaj7 G7b13b9 Cmaj7 ...
2:45 p.m.
If you remount it ro you can't fix anything. I was referring to when
the root partition is actually so broken that it won't do the auto fsck.
Jan
On Sat, 2004-04-24 at 11:32, Florian Schmidt wrote:
On 24 Apr 2004 05:34:38 -0500
Jan Depner <eviltwin69(a)cableone.net> wrote:
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.
remount the root partition read only.. see man mount.. i think that should lessen the
probability of damage.. after fsck just reboot, do not remount ro..
flo
P.S.: i'm not sure though...
--
Fm7 Bbm7 Eb7b9 Abmaj7 Dbmaj7 G7b13b9 Cmaj7 ...
7:17 p.m.
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:
__________________________________
Do you Yahoo!?
Yahoo! Photos: High-quality 4x6 digital prints for 25¢
http://photos.yahoo.com/ph/print_splash 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?
7:59 p.m.
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
8:27 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
8:49 p.m.
If you're going to rebuild use ext3 instead of ext2 for the root
partition. It's journalled. Use Reiserfs for the data partition. The
hard drive may not be physically (hard) trashed. You can try booting
from CD and mounting the root drive partitions. You'll need another
drive to copy data to however (actually you really should have a second
drive for data). Gotta run.
Jan
On Sat, 2004-04-24 at 19:17, Aaron Trumm wrote:
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
26 Apr
26 Apr
3:52 p.m.
New subject: [linux-audio-user] Journaling filesystems [was: Ardour Crash + can't boot]
If you're going to rebuild use ext3 instead of
ext2 for the root
partition. It's journalled. Use Reiserfs for the data partition. The
What is the reason for using two different filesystems here? Is reiserfs
more suitable for (audio) data?
Personally, I am using xfs (also journalled) for all workstations I
install, after having used it successfully on a heavy duty fileserver
for more than 2 years. It never gave me any problems, and I have done
some nasty tests.
Now, I have never run Ardour - on top of my TODO list for a looong time
:-), so I can't say how Ardour and xfs play together, but I'd be surprised
if there are any problems. Anyway, I would be very much interested to hear
if others are using xfs, and how it behaves under heavy multitrack audio
IO.
Ah, and xfs has a special "realtime" mode. From the kernel configuration:
If you say Y here you will be able to mount and use XFS filesystems
which contain a realtime subvolume. The realtime subvolume is a
separate area of disk space where only file data is stored. The
realtime subvolume is designed to provide very deterministic
data rates suitable for media streaming applications.
which sounds very interesting. BUT!:
This feature is unsupported at this time, is not yet fully
functional, and may cause serious problems.
Serious problems... Hmm, looking at Aaron's mail, he already got
enough serious problems even without experimental xfs features...
xfs is in kernel 2.6.x, and has been included in 2.4.25 as well.
(before that, sgi provides patches)
maarten
4:09 p.m.
New subject: [linux-audio-user] Journaling filesystems [was: Ardour Crash + can't boot]
I would be willing to bet that XFS might be even better than reiserfs
but I have no data on that. Mark Knecht documented the responses of the
different filesystems using Benno Senoner's Latency Test program. I
have the results on my site at:
http://myweb.cableone.net/eviltwin69/Arcana.html
My own (totally unscientific) results are also commented on there.
Jan
On Mon, 2004-04-26 at 12:40, Maarten de Boer wrote:
If you're
going to rebuild use ext3 instead of ext2 for the root
partition. It's journalled. Use Reiserfs for the data partition. The
What is the reason for using two different filesystems here? Is reiserfs
more suitable for (audio) data?
Personally, I am using xfs (also journalled) for all workstations I
install, after having used it successfully on a heavy duty fileserver
for more than 2 years. It never gave me any problems, and I have done
some nasty tests.
Now, I have never run Ardour - on top of my TODO list for a looong time
:-), so I can't say how Ardour and xfs play together, but I'd be surprised
if there are any problems. Anyway, I would be very much interested to hear
if others are using xfs, and how it behaves under heavy multitrack audio
IO.
Ah, and xfs has a special "realtime" mode. From the kernel configuration:
If you say Y here you will be able to mount and use XFS filesystems
which contain a realtime subvolume. The realtime subvolume is a
separate area of disk space where only file data is stored. The
realtime subvolume is designed to provide very deterministic
data rates suitable for media streaming applications.
which sounds very interesting. BUT!:
This feature is unsupported at this time, is not yet fully
functional, and may cause serious problems.
Serious problems... Hmm, looking at Aaron's mail, he already got
enough serious problems even without experimental xfs features...
xfs is in kernel 2.6.x, and has been included in 2.4.25 as well.
(before that, sgi provides patches)
maarten 
4:50 p.m.
New subject: [linux-audio-user] Journaling filesystems [was: Ardour Crash + can't boot]
Jan Depner wrote:
I would be willing to bet that XFS might be even
better than reiserfs
but I have no data on that. Mark Knecht documented the responses of the
different filesystems using Benno Senoner's Latency Test program. I
have the results on my site at:
http://myweb.cableone.net/eviltwin69/Arcana.html
My own (totally unscientific) results are also commented on there.
Jan
Hi,
I think the value of XFS vs. reiserfs will likely be a bit dependent
on *what* audio application you are running.
I was interested in XFS when I did the tests on Jan's site but I
didn't (and still don't) have the skillset to add XFS to a 2.4 series
kernel so I left it out. I think it would be interesting to give XFS a try.
When I was doing all of this stuff I did some reading from a number
of interesting sites. One of the reasons someone *might* be interested
in XFS over reiserfs is that (and this is totally from memory right now
so I could have it backward) XFS is apparently better tuned for large
files. I would think that, based on my work with Pro Tools where I end
up with large 500MB-2GB wave files all the time, folks primarily running
Audour for audio recording might do better with XFS. That needs to be
verified, but I wouldn't be suprised if it worked out that way.
On the other hand, someone running some audio app that makes use of
a large number of small files, for instance a tracker like Skale or
Cheese Tracker, might find reiserfs works better.
If I have the large/small - reiserfs/XFS thing backward then please
just reverse the example.
Once again, this is all just supposition. It needs to be looked at
in a controlled manner.
Cheers,
Mark
6:40 p.m.
New subject: [linux-audio-user] Journaling filesystems [was: Ardour Crash + can't boot]
On Mon, 2004-04-26 at 13:42, Mark Knecht wrote:
When I was doing all of this stuff I did some reading from a number
of interesting sites. One of the reasons someone *might* be interested
in XFS over reiserfs is that (and this is totally from memory right now
so I could have it backward) XFS is apparently better tuned for large
files. I would think that, based on my work with Pro Tools where I end
up with large 500MB-2GB wave files all the time, folks primarily running
Audour for audio recording might do better with XFS. That needs to be
verified, but I wouldn't be suprised if it worked out that way.
This was my take on it as well.
Jan
27 Apr
27 Apr
12:44 p.m.
New subject: [linux-audio-user] Journaling filesystems [was: Ardour Crash + can't boot]
On Mon, 2004-04-26 at 13:42, Mark Knecht wrote:
> When I was doing all of this stuff I did some
reading from a number
>of interesting sites. One of the reasons someone *might* be interested
>in XFS over reiserfs is that (and this is totally from memory right now
>so I could have it backward) XFS is apparently better tuned for large
>files. I would think that, based on my work with Pro Tools where I end
>up with large 500MB-2GB wave files all the time, folks primarily running
>Audour for audio recording might do better with XFS. That needs to be
>verified, but I wouldn't be suprised if it worked out that way.
It will be interesting to see how the new Reiser4 file system stacks up
in terms of speed. Once it is stable of course. AFAIK, it is for 2.6
kernels only, and is marked "EXPERIMENTAL".
Namesys brags it to be "the fastest filesystem", according to these
benchmarks:
http://namesys.com/benchmarks.html
In the config of the 2.6 kernel, they also claim it to be 10 times
faster than NTFS, for example...
More info from namesys.com website.
Personally, I may wait for it to not have that funny little warning
before I switch everything over, but it seems to be promising.
best,
d.
--
derek holzer ::: http://www.umatic.nl
---Oblique Strategy # 56:
"Do the washing up"
26 Apr
26 Apr
5:29 p.m.
New subject: [linux-audio-user] Journaling filesystems [was: Ardour Crash + can't boot]
I am using xfs on my fedora/ccrma box (kernel from atrpms), but I
haven't got down to any audio work yet - when i do I'll report my
results.
On Apr 26, 2004, at 3:06 PM, Jan Depner wrote:
I would be willing to bet that XFS might be even
better than reiserfs
but I have no data on that. Mark Knecht documented the responses of
the
different filesystems using Benno Senoner's Latency Test program. I
have the results on my site at:
http://myweb.cableone.net/eviltwin69/Arcana.html
My own (totally unscientific) results are also commented on there.
Jan
On Mon, 2004-04-26 at 12:40, Maarten de Boer wrote:
If
you're going to rebuild use ext3 instead of ext2 for the root
partition. It's journalled. Use Reiserfs for the data partition.
The
What is the reason for using two different filesystems here? Is
reiserfs
more suitable for (audio) data?
Personally, I am using xfs (also journalled) for all workstations I
install, after having used it successfully on a heavy duty fileserver
for more than 2 years. It never gave me any problems, and I have done
some nasty tests.
Now, I have never run Ardour - on top of my TODO list for a looong
time
:-), so I can't say how Ardour and xfs play together, but I'd be
surprised
if there are any problems. Anyway, I would be very much interested to
hear
if others are using xfs, and how it behaves under heavy multitrack
audio
IO.
Ah, and xfs has a special "realtime" mode. From the kernel
configuration:
If you say Y here you will be able to mount and use XFS filesystems
which contain a realtime subvolume. The realtime subvolume is a
separate area of disk space where only file data is stored. The
realtime subvolume is designed to provide very deterministic
data rates suitable for media streaming applications.
which sounds very interesting. BUT!:
This feature is unsupported at this time, is not yet fully
functional, and may cause serious problems.
Serious problems... Hmm, looking at Aaron's mail, he already got
enough serious problems even without experimental xfs features...
xfs is in kernel 2.6.x, and has been included in 2.4.25 as well.
(before that, sgi provides patches)
maarten
4:11 p.m.
New subject: [linux-audio-user] Journaling filesystems [was: Ardour Crash + can't boot]
Oh, I forgot to mention, the reason for using ext3 on the root and boot
partitions is that it is pretty much bullet-proof. I'm sure that
reiserfs is pretty stable at this point but I'm not worried about speed
on root and boot just reliability.
Jan
On Mon, 2004-04-26 at 12:40, Maarten de Boer wrote:
If you're
going to rebuild use ext3 instead of ext2 for the root
partition. It's journalled. Use Reiserfs for the data partition. The
What is the reason for using two different filesystems here? Is reiserfs
more suitable for (audio) data?
Personally, I am using xfs (also journalled) for all workstations I
install, after having used it successfully on a heavy duty fileserver
for more than 2 years. It never gave me any problems, and I have done
some nasty tests.
Now, I have never run Ardour - on top of my TODO list for a looong time
:-), so I can't say how Ardour and xfs play together, but I'd be surprised
if there are any problems. Anyway, I would be very much interested to hear
if others are using xfs, and how it behaves under heavy multitrack audio
IO.
Ah, and xfs has a special "realtime" mode. From the kernel configuration:
If you say Y here you will be able to mount and use XFS filesystems
which contain a realtime subvolume. The realtime subvolume is a
separate area of disk space where only file data is stored. The
realtime subvolume is designed to provide very deterministic
data rates suitable for media streaming applications.
which sounds very interesting. BUT!:
This feature is unsupported at this time, is not yet fully
functional, and may cause serious problems.
Serious problems... Hmm, looking at Aaron's mail, he already got
enough serious problems even without experimental xfs features...
xfs is in kernel 2.6.x, and has been included in 2.4.25 as well.
(before that, sgi provides patches)
maarten
24 Apr
24 Apr
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
8:57 p.m.
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?
Sounds bad, like the filesystem got corrupted.
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.
What kind of error messages did you get during the new install and at
what point in the process? What is the current partitioning structure of
the disk (after all that happened)? You can find out by doing "fdisk -l"
from the rescue prompt, I guess.
It could be that the new install did not update grub (who knows why) to
point to the newly installed system and you are still trying to boot the
old one. Hmmmm, if fact that could be the case if you have duplicated
labels. Check the labels of the partitions that are supposed to be the
"/" partition (you should have two if I understand correctly what you
did). If one of your root partitions is /dev/hda2 then:
e2label /dev/hda2
should output "/"
Do that with the other partitions. If you have two "/"'s then there's
the boot confusion. Change the OLD one to something else with (replace
with the proper device):
e2label /dev/hdx "OLD/"
Try booting again...
-- Fernando
11:11 p.m.
What kind of error messages did you get during the new
install and at
what point in the process? What is the current partitioning structure of
the disk (after all that happened)? You can find out by doing "fdisk -l"
from the rescue prompt, I guess.
one - which I can't remember the wording but it was basically akin to can't
read from drive hda
It could be that the new install did not update grub
(who knows why) to
point to the newly installed system and you are still trying to boot the
old one. Hmmmm, if fact that could be the case if you have duplicated
labels. Check the labels of the partitions that are supposed to be the
"/" partition (you should have two if I understand correctly what you
did). If one of your root partitions is /dev/hda2 then:
e2label /dev/hda2
should output "/"
interesting - e2label /dev/hda2 - which I believe is the root, gives me the
error about a too high revision (ext3/ext2 thing)
e2label /dev/hda - same error - hda0 (which may not exist) same, hda1 same -
hda3 it give:
/boot
there's two drives in this machine - so I tried
e2label /dev/hdb
same error
e2label /dev/hdb2 gives me
/
25 Apr
25 Apr
12:08 a.m.
It could be
that the new install did not update grub (who knows why) to
point to the newly installed system and you are still trying to boot the
old one. Hmmmm, if fact that could be the case if you have duplicated
labels. Check the labels of the partitions that are supposed to be the
"/" partition (you should have two if I understand correctly what you
did). If one of your root partitions is /dev/hda2 then:
e2label /dev/hda2
should output "/"
interesting - e2label /dev/hda2 - which I believe is the root, gives me the
error about a too high revision (ext3/ext2 thing) e2label /dev/hda - same error - hda0 (which may not
exist) same, hda1 same -
hda3 it give:
/boot
The boot partition (where the kernel lives). No way to know if it is the
old, or the new or it is used by both installs (well, you could mount it
and see the dates of the files, I guess).
there's two drives in this machine - so I tried
e2label /dev/hdb
same error
e2label /dev/hdb2 gives me
/
So this is probably where the new install is located. Did you try
/dev/hdb1? There must be one. What is the output of:
fdisk -l /dev/hda
fdisk -l /dev/hdb
Anyway, any grub experts out there? Probably grub needs to be pointed to
/dev/hdb1 as the root partition, right?
-- Fernando
1:01 a.m.
The boot partition (where the kernel lives). No way to
know if it is the
old, or the new or it is used by both installs (well, you could mount it
and see the dates of the files, I guess).
hmmm - the whole "mount" idea isn't going too well either *laugh* - it
tends to say that modprobe can't find module yp or something - tried many
versions of this stuff - sorry no detail on this *laugh*
So this is probably where the new install is located.
Did you try
/dev/hdb1? There must be one. What is the output of:
fdisk -l /dev/hda
fdisk -l /dev/hdb
I believe I tried e2label /dev/hdb1 and got the same error as on hda2 - but
not SURE - the machine is currently off - at some point I tried a reboot and
it got stuck (and old oddity) and I turned it off for the time being as I am
leaving shortly...
Anyway, any grub experts out there? Probably grub
needs to be pointed to
/dev/hdb1 as the root partition, right?
an interesting problem is GETTING to grub. I did find a grub.conf - I think
in /dev/hdb2/etc - somewhere or other - but when I tried to edit it, it
couldn't get it open
I wish I knew the options at that floppy's boot: prompt because I sort of
guess at things to try - like I tried booting and giving that prompt "linux
boot=/dev/hdb3 and such and init= and root= and a few different things. at
this point it's always the same, since I first booted up using "linux
single", it now has always booted and not done the kernel panic, but given
me the filesystem error and dropped me to a shell.
that's why I keep asking on here 'cause I don't know too well how these
directories are structured, what the parameter possibilities are, etc.
somewhere I have a damn linux reference but I can't find it yet
hmmm. very odd. very interesting.
1:10 a.m.
So this is
probably where the new install is located. Did you try
/dev/hdb1? There must be one. What is the output of:
fdisk -l /dev/hda
fdisk -l /dev/hdb
I believe I tried e2label /dev/hdb1 and got the same error as on hda2 - but
not SURE - the machine is currently off - at some point I tried a reboot and
it got stuck (and old oddity) and I turned it off for the time being as I am
leaving shortly...
Anyway, any grub experts out there? Probably grub
needs to be pointed to
/dev/hdb1 as the root partition, right?
an interesting problem is GETTING to grub. I did find a grub.conf - I think
in /dev/hdb2/etc - somewhere or other - but when I tried to edit it, it
couldn't get it open
I wish I knew the options at that floppy's boot: prompt because I sort of
guess at things to try - like I tried booting and giving that prompt "linux
boot=/dev/hdb3 and such and init= and root= and a few different things. at
this point it's always the same, since I first booted up using "linux
single", it now has always booted and not done the kernel panic, but given
me the filesystem error and dropped me to a shell.
6:47 a.m.
So you can get a root shell? Check /etc/fstab to see
if it is pointing
to the right places, particular that "/" is pointing to the right
device.
you know, it's not a normal "root" shell - not that I know what I'm
talking
about there - but its prompt is
(repair file system) #
and you can't just change to /etc (unless i'm crazy or something) - you
gotta like go find /dev/hdb3 or hda2 or whatnot - it took a little sniffing
to get to /etc - - but now that I think about it, maybe I was crazy.
I will try again to make sure.
I'm still kind of curious as to the CAUSE of this problem. I didn't expect
that an ardour crash could corrupt the file system or maybe even the
physical disk, and that's what started the mess - unless that was a
coincidence... hmmm...
1:56 p.m.
On Sun, 2004-04-25 at 03:37, Aaron Trumm wrote:
I'm still kind of curious as to the CAUSE of this
problem. I didn't expect
that an ardour crash could corrupt the file system or maybe even the
physical disk, and that's what started the mess - unless that was a
coincidence... hmmm...
Most likely it is a coincidence. It seems quite unlikely to me that
Ardour could cause Linux to destroy a hard drive.
On the other hand hard drives do fail. Logically, they are likely to be
running a program when they do fail. It's therefore easy to think it's
the program hurting the drive when in fact it was just the drive
failing.
I don't know much about running the 'SMART' tools, but I think it's time
for me to start learning.
And again, I think that having a good LiveCD for looking at these things
helps a lot.
- Mark
4:14 p.m.
So you can get
a root shell? Check /etc/fstab to see if it is pointing
to the right places, particular that "/" is pointing to the right
device.
you know, it's not a normal "root" shell - not that I know what I'm
talking
about there - but its prompt is
(repair file system) # and you can't just change to /etc (unless i'm
crazy or something) - you
gotta like go find /dev/hdb3 or hda2 or whatnot - it took a little sniffing
to get to /etc - - but now that I think about it, maybe I was crazy.
Yes, at that point you don't have a "working" "/" because it could
not
be checked. So, the kernel is either trying to boot into /dev/hda2
(which is known broken), or /dev/hdb3 is also broken (unlikely). When
you say you got to /etc, how did you do it?
Things I would try:
- try to boot into /dev/hdb3 (this assumes the install was fine). When
you get to the grub screen highlight the original redhat kernel (not the
Planet CCRMA one), press "e" to edit, go to the kernel boot line, press
"e" to edit, make sure the root= option is pointing to /dev/hdb3, press
"b" to boot from this kernel with the options selected.
- if this does not work then probably the hdb3 partition does not
contain a valid install (depends on how it fails).
I'm still kind of curious as to the CAUSE of this
problem. I didn't expect
that an ardour crash could corrupt the file system or maybe even the
physical disk, and that's what started the mess - unless that was a
coincidence... hmmm...
Could be a hardware failure or could be a kernel problem (unlikely but
possible). I doubt that Ardour was the cause of what happened.
-- Fernando
28 Apr
28 Apr
7:11 a.m.
Well, y'all, to continue this little discussion
Fernando asked what the exact error I got was, when I was trying to
REINSTALL RedHat - it was:
Invalid argument during seek for read on /dev/hda
I actually gathered up backups (what I had) and swapped drives around, put
the drive in question in another machine as slave, the machine booted fine
of course but this drive failed to mount, and Gnome's hardware browswer
showed the drive, but the root partition said "no filesystem" Then I
swapped some more and it now sits alone in a machine, and I'm attempting to
wipe clean and install Red Hat, and I'm getting the above error periodically
during the preparation stage (before you actually click "install")
Sounds like bad disk to ME - but I'm going forward with the install just for
fun. Told disk druid to check for bad blocks. Is this going to format the
drive, low level format, or just? what? - i dunno what other options I
would put in that list *laugh*
fun fun fun
7:21 a.m.
I believe that "check for bad blocks" runs the badblocks command with
the -w option. It writes a pattern to every block and then reads it to
check that it's OK.
Jan
On Wed, 2004-04-28 at 06:01, Aaron Trumm wrote:
Well, y'all, to continue this little discussion
Fernando asked what the exact error I got was, when I was trying to
REINSTALL RedHat - it was:
Invalid argument during seek for read on /dev/hda
I actually gathered up backups (what I had) and swapped drives around, put
the drive in question in another machine as slave, the machine booted fine
of course but this drive failed to mount, and Gnome's hardware browswer
showed the drive, but the root partition said "no filesystem" Then I
swapped some more and it now sits alone in a machine, and I'm attempting to
wipe clean and install Red Hat, and I'm getting the above error periodically
during the preparation stage (before you actually click "install")
Sounds like bad disk to ME - but I'm going forward with the install just for
fun. Told disk druid to check for bad blocks. Is this going to format the
drive, low level format, or just? what? - i dunno what other options I
would put in that list *laugh*
fun fun fun
24 Apr
24 Apr
8:55 a.m.
On Saturday 24 April 2004 10:57 am, Aaron Trumm wrote:
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
Boot-prompt-HOWTO ?
Does the kernel still panic if you try to boot with no options?
It's good to know which partition you're booting from (I have to write it down
somewhere) and also what the kernel's alias is (It's no use booting
'linux'
if it's actually known as 'knoppix' for example - press TAB to get a list).
also check /etc/lilo.conf.
boot: linux single
Will start you up in single user mode. It's always worth a try.
All the Best
tim hall
10:01 p.m.
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 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?
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?
25 Apr
25 Apr
5:15 p.m.
On Sat, Apr 24, 2004 at 08:05:56PM -0700, Aaron Trumm wrote:
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!
Aaron - At the root shell prompt, enter you root password. Then do the
following:
e2fsck /dev/hda1
e2fsck /dev/hda2
e2fsck /dev/hdb1
e2fsck /dev/hdb2
e2fsck /dev/hdb3
,etc., until it doesn't give you any more errors. Note that the fix routine
could take a long time if there is a lot of damage but I have seen an
apparently thrashed drive come out of its coma unscathed by using e2fsck.
Worh a try.
--
Jack Bowling
mailto: jbinpg(a)shaw.ca
7543
days inactive
7547
days old
linux-audio-user@lists.linuxaudio.org
32 comments
12 participants
participants (12)
-
Aaron Trumm -
derek holzer -
Fernando Pablo Lopez-Lezcano -
Florian Schmidt -
Jack Bowling -
Jan Depner -
Joey Reid -
Maarten de Boer -
Mark Knecht -
Mark Knecht -
R Parker -
tim hall