PDA

View Full Version : Slimserver 5.3.0b1 Crashes when rescanning OGG files



Camp Murphy
2004-08-21, 18:04
Hi,



I posted yesterday about Slimserver crashing every time I tried to rescan
(or wipe & rescan) my library. After some work with the command line
version of Slimserver I have discovered the crashes only occur when the
rescan hits .ogg files. I should note it doesn't crash for all my .ogg
files -some get rescanned perfectly fine. I don't know what to do short of
deleting these bad files.and the only way I can find a bad ogg file is to
let Slimserver crash while rescanning. Even the "bad" ones play just fine
in every media player I use.



I know 5.3.0b1 has built-in support for decoding .ogg. I downloaded
oggdec.exe thinking there might be a newer version but it appears to be the
exact same as the version shipping with 5.3.0b1. I have also read some
people have had to edit their convert.conf file to get ogg working right. I
looked at the convert.conf file and have zero clue as to what to do. It's
Greek to me. :-)



Any ideas? Thanks in advance,



-Camp

Peter Pouliot
2004-08-22, 14:53
Hi All,
I actually have a similar problem, however I have no ogg files. Just a
large library, 124gb (20427 songs). It crashes when I rescan, usually
runs for about 5 minutes and then dies. I end up with the following
error on the console.

hde: dma_timer_expiry dma status == 0x21
hde: error waiting for DMA
hde: dma timeout retry: status=0x51
[ DriveReady Seek Complete Error}
hde: dma timeout retry: error 0x40 {UncorrectableError },
LBAsect=27259783, high=16, low=6824327, sector-275259600
end_request: I/O error, dev 21:01 (hde) sector 275259600
blk: queue c03d4c98, I/O limit 4095MB (mask 0xffffffff)
hde: read_intr: status=0x59 {DriveReady SeakComplete DataRequest Error }
hde: read_intr: error=0x40 {UncorrectableError }, LBAsect-275259783,
high=16, low=6824327, sector=275259720

This is in /var/log/messages:

Aug 22 12:28:45 mp3 kernel: hde: dma_timer_expiry: dma status == 0x21
Aug 22 12:28:55 mp3 kernel: hde: error waiting for DMA
Aug 22 12:28:55 mp3 kernel: hde: dma timeout retry: status=0x51 {
DriveReady SeekComplete Error }
Aug 22 12:28:55 mp3 kernel: hde: dma timeout retry: error=0x40 {
UncorrectableError }, LBAsect=275259783, high=16, low=6824327,
sector=275259600
Aug 22 12:28:55 mp3 kernel: end_request: I/O error, dev 21:01 (hde),
sector 275259600
Aug 22 12:28:55 mp3 kernel: blk: queue c03d4c98, I/O limit 4095Mb (mask
0xffffffff)

Here's the output of a fsck on the drive.

[root@mp3 root]# fsck -av /dev/hde1
fsck 1.34 (25-Jul-2003)
/mp3: clean, 22825/24428544 files, 33299168/48839600 blocks

I tried upgrading to the latest nightly however still having the same
problem, here's my version.

[root@mp3 root]# rpm -qa |grep slim
slimserver-2004_08_22-1

Any help would be greatly appreciated. If there's anything I can do on
my end. Please let me know..

cheers,

pp


On Sat, 2004-08-21 at 21:04, Camp Murphy wrote:

> Hi,
>
>
>
> I posted yesterday about Slimserver crashing every time I tried to
> rescan (or wipe & rescan) my library. After some work with the
> command line version of Slimserver I have discovered the crashes only
> occur when the rescan hits .ogg files. I should note it doesn’t crash
> for all my .ogg files –some get rescanned perfectly fine. I don’t
> know what to do short of deleting these bad files…and the only way I
> can find a bad ogg file is to let Slimserver crash while rescanning.
> Even the “bad” ones play just fine in every media player I use.
>
>
>
> I know 5.3.0b1 has built-in support for decoding .ogg. I downloaded
> oggdec.exe thinking there might be a newer version but it appears to
> be the exact same as the version shipping with 5.3.0b1. I have also
> read some people have had to edit their convert.conf file to get ogg
> working right. I looked at the convert.conf file and have zero clue
> as to what to do. It’s Greek to me. J
>
>
>
> Any ideas? Thanks in advance,
>
>
>
> -Camp
>
>
>
>

Victor Brilon
2004-08-22, 14:58
It looks like your hde drive is going back. I'd suggest backing it up
and getting a new one.

Victor

Peter Pouliot wrote:
> Hi All,
> I actually have a similar problem, however I have no ogg files. Just a
> large library, 124gb (20427 songs). It crashes when I rescan, usually
> runs for about 5 minutes and then dies. I end up with the following
> error on the console.
>
> hde: dma_timer_expiry dma status == 0x21
> hde: error waiting for DMA
> hde: dma timeout retry: status=0x51
> [ DriveReady Seek Complete Error}
> hde: dma timeout retry: error 0x40 {UncorrectableError },
> LBAsect=27259783, high=16, low=6824327, sector-275259600
> end_request: I/O error, dev 21:01 (hde) sector 275259600
> blk: queue c03d4c98, I/O limit 4095MB (mask 0xffffffff)
> hde: read_intr: status=0x59 {DriveReady SeakComplete DataRequest Error }
> hde: read_intr: error=0x40 {UncorrectableError }, LBAsect-275259783,
> high=16, low=6824327, sector=275259720
>
> This is in /var/log/messages:
>
> Aug 22 12:28:45 mp3 kernel: hde: dma_timer_expiry: dma status == 0x21
> Aug 22 12:28:55 mp3 kernel: hde: error waiting for DMA
> Aug 22 12:28:55 mp3 kernel: hde: dma timeout retry: status=0x51 {
> DriveReady SeekComplete Error }
> Aug 22 12:28:55 mp3 kernel: hde: dma timeout retry: error=0x40 {
> UncorrectableError }, LBAsect=275259783, high=16, low=6824327,
> sector=275259600
> Aug 22 12:28:55 mp3 kernel: end_request: I/O error, dev 21:01 (hde),
> sector 275259600
> Aug 22 12:28:55 mp3 kernel: blk: queue c03d4c98, I/O limit 4095Mb (mask
> 0xffffffff)
>
> Here's the output of a fsck on the drive.
>
> [root@mp3 root]# fsck -av /dev/hde1
> fsck 1.34 (25-Jul-2003)
> /mp3: clean, 22825/24428544 files, 33299168/48839600 blocks
>
> I tried upgrading to the latest nightly however still having the same
> problem, here's my version.
>
> [root@mp3 root]# rpm -qa |grep slim
> slimserver-2004_08_22-1
>
> Any help would be greatly appreciated. If there's anything I can do on
> my end. Please let me know..
>
> cheers,
>
> pp
>
>
> On Sat, 2004-08-21 at 21:04, Camp Murphy wrote:
>
>> /Hi,//
>>
>>
>>
>> I posted yesterday about Slimserver crashing every time I tried to
>> rescan (or wipe & rescan) my library. After some work with the
>> command line version of Slimserver I have discovered the crashes only
>> occur when the rescan hits .ogg files. I should note it doesn’t crash
>> for all my .ogg files –some get rescanned perfectly fine. I don’t
>> know what to do short of deleting these bad files…and the only way I
>> can find a bad ogg file is to let Slimserver crash while rescanning.
>> Even the “bad� ones play just fine in every media player I use.
>>
>>
>>
>> I know 5.3.0b1 has built-in support for decoding .ogg. I downloaded
>> oggdec.exe thinking there might be a newer version but it appears to
>> be the exact same as the version shipping with 5.3.0b1. I have also
>> read some people have had to edit their convert.conf file to get ogg
>> working right. I looked at the convert.conf file and have zero clue
>> as to what to do. It’s Greek to me. J
>>
>>
>>
>> Any ideas? Thanks in advance,
>>
>>
>>
>> -Camp
>>
>>
>> /
>> ------------------------------------------------------------------------
>>
>>/

Jules Taplin
2004-08-22, 15:04
Hi Peter.

Right. That looks like a disc corruption to me. I'd suggest that your HDD is on the verge of collapse. Bear in mind that fsck is really there to check file system structure integrity, not to ensure that the media itself isn't defective.

If I were you, I'd start seriously thinking about words like 'backup'. It's possible that you can mark the blocks on that disk bad (if you're running an ext2/ext3 filesystem, then you can probably scan, for it - see the '-c' option to e2fsck), but in my experience - once a disk starts throwing errors, it's time to get shot of it before it can hurt your data.

Take a look at the man page for 'badblocks' - you should be able to use it to scan the actual media for errors. However... be careful - if you pass the wrong command line switch to it, you can ask it to erase data. Read the man page first!


Best Regards,


Jules


----- Original Message -----
From: Peter Pouliot
To: Slim Devices Discussion
Sent: Sunday, August 22, 2004 10:53 PM
Subject: [slim] Slimserver Crashes when rescanning


Hi All,
I actually have a similar problem, however I have no ogg files. Just a large library, 124gb (20427 songs). It crashes when I rescan, usually runs for about 5 minutes and then dies. I end up with the following error on the console.

hde: dma_timer_expiry dma status == 0x21
hde: error waiting for DMA
hde: dma timeout retry: status=0x51
[ DriveReady Seek Complete Error}
hde: dma timeout retry: error 0x40 {UncorrectableError }, LBAsect=27259783, high=16, low=6824327, sector-275259600
end_request: I/O error, dev 21:01 (hde) sector 275259600
blk: queue c03d4c98, I/O limit 4095MB (mask 0xffffffff)
hde: read_intr: status=0x59 {DriveReady SeakComplete DataRequest Error }
hde: read_intr: error=0x40 {UncorrectableError }, LBAsect-275259783, high=16, low=6824327, sector=275259720

This is in /var/log/messages:

Aug 22 12:28:45 mp3 kernel: hde: dma_timer_expiry: dma status == 0x21
Aug 22 12:28:55 mp3 kernel: hde: error waiting for DMA
Aug 22 12:28:55 mp3 kernel: hde: dma timeout retry: status=0x51 { DriveReady SeekComplete Error }
Aug 22 12:28:55 mp3 kernel: hde: dma timeout retry: error=0x40 { UncorrectableError }, LBAsect=275259783, high=16, low=6824327, sector=275259600
Aug 22 12:28:55 mp3 kernel: end_request: I/O error, dev 21:01 (hde), sector 275259600
Aug 22 12:28:55 mp3 kernel: blk: queue c03d4c98, I/O limit 4095Mb (mask 0xffffffff)

Here's the output of a fsck on the drive.

[root@mp3 root]# fsck -av /dev/hde1
fsck 1.34 (25-Jul-2003)
/mp3: clean, 22825/24428544 files, 33299168/48839600 blocks

I tried upgrading to the latest nightly however still having the same problem, here's my version.

[root@mp3 root]# rpm -qa |grep slim
slimserver-2004_08_22-1

Any help would be greatly appreciated. If there's anything I can do on my end. Please let me know..

cheers,

pp


On Sat, 2004-08-21 at 21:04, Camp Murphy wrote:
Hi,



I posted yesterday about Slimserver crashing every time I tried to rescan (or wipe & rescan) my library. After some work with the command line version of Slimserver I have discovered the crashes only occur when the rescan hits .ogg files. I should note it doesn’t crash for all my ..ogg files –some get rescanned perfectly fine. I don’t know what to do short of deleting these bad files…and the only way I can find a bad ogg file is to let Slimserver crash while rescanning. Even the “bad” ones play just fine in every media player I use.



I know 5.3.0b1 has built-in support for decoding .ogg. I downloaded oggdec.exe thinking there might be a newer version but it appears to be the exact same as the version shipping with 5.3.0b1. I have also read some people have had to edit their convert.conf file to get ogg working right. I looked at the convert.conf file and have zero clue as to what to do. It’s Greek to me. J



Any ideas? Thanks in advance,



-Camp



----------------------------------------------------------------------------

Ted Rathkopf
2004-08-22, 15:09
Meanwhile, back at the model home, Victor Brilon <victor (AT) victorland (DOT) com> said:

> It looks like your hde drive is going back. I'd suggest backing it up
> and getting a new one.

I think Victor means "going bad."

And I would second the advice to back it up quickly.

I would also recommend installing the smartmontools to run periodic
self-tests on your drives so that you know when a drive starts to fail
before it gets to the state yours is currently in.

http://smartmontools.sourceforge.net/

I've had two drives fail in the last month. After rebuilding my
system (luckily my mp3's weren't on the bad disk, and I had a backup
of my home directory that was only a month old) I installed the
smartmontools on that system and on another system. On the other
system, it immediately let me know that I had a drive that was getting
some DMA read errors. I've retired that drive, as well.

While I'm tossing out advice, I'll also mention mondo.

http://www.microwerks.net/~hugo/index.html

Mondo creates a bootable CD backup that will let you rebuild your
system from bare metal, if necessary. Wish I'd tried it out a month
ago, before my troubles started.

--
Ted Rathkopf

Peter Pouliot
2004-08-22, 18:40
Hey guys thanks for the imput, fortunately from day one I've done the
master/slave.. I.e. My master is a 200gb external drive which I rsync
to the slave (one spitting the errors), however In this instance I'm
wondering if it could be the controller rather than the disk. In terms
of the system itself, it's an via epia mobo, and I'm using a promise
card for extra ide ports. I know the promise cards have issues on
linux... (We've had issues w/ them at work). I'd like to know what
people think... Thanks again for the input...

p

On Sun, 2004-08-22 at 22:09, Ted Rathkopf wrote:

> Meanwhile, back at the model home, Victor Brilon <victor (AT) victorland (DOT) com> said:
>
> > It looks like your hde drive is going back. I'd suggest backing it up
> > and getting a new one.
>
> I think Victor means "going bad."
>
> And I would second the advice to back it up quickly.
>
> I would also recommend installing the smartmontools to run periodic
> self-tests on your drives so that you know when a drive starts to fail
> before it gets to the state yours is currently in.
>
> http://smartmontools.sourceforge.net/
>
> I've had two drives fail in the last month. After rebuilding my
> system (luckily my mp3's weren't on the bad disk, and I had a backup
> of my home directory that was only a month old) I installed the
> smartmontools on that system and on another system. On the other
> system, it immediately let me know that I had a drive that was getting
> some DMA read errors. I've retired that drive, as well.
>
> While I'm tossing out advice, I'll also mention mondo.
>
> http://www.microwerks.net/~hugo/index.html
>
> Mondo creates a bootable CD backup that will let you rebuild your
> system from bare metal, if necessary. Wish I'd tried it out a month
> ago, before my troubles started.

Peter Pouliot
2004-08-22, 20:54
Well Fella's, I after some further investigation it definately is the
disk... An fsck -cv caused it to crash. As did the rescan, got a good
deal on a replacement 200gb via pricewatch... Thanks again for all the
help...

p

On Mon, 2004-08-23 at 01:40, Peter Pouliot wrote:

> Hey guys thanks for the imput, fortunately from day one I've done the
> master/slave.. I.e. My master is a 200gb external drive which I rsync
> to the slave (one spitting the errors), however In this instance I'm
> wondering if it could be the controller rather than the disk. In
> terms of the system itself, it's an via epia mobo, and I'm using a
> promise card for extra ide ports. I know the promise cards have
> issues on linux... (We've had issues w/ them at work). I'd like to
> know what people think... Thanks again for the input...
>
> p
>
> On Sun, 2004-08-22 at 22:09, Ted Rathkopf wrote:
>
> > Meanwhile, back at the model home, Victor Brilon <victor (AT) victorland (DOT) com> said:
> >
> > > It looks like your hde drive is going back. I'd suggest backing it up
> > > and getting a new one.
> >
> > I think Victor means "going bad."
> >
> > And I would second the advice to back it up quickly.
> >
> > I would also recommend installing the smartmontools to run periodic
> > self-tests on your drives so that you know when a drive starts to fail
> > before it gets to the state yours is currently in.
> > http://smartmontools.sourceforge.net/
> >
> > I've had two drives fail in the last month. After rebuilding my
> > system (luckily my mp3's weren't on the bad disk, and I had a backup
> > of my home directory that was only a month old) I installed the
> > smartmontools on that system and on another system. On the other
> > system, it immediately let me know that I had a drive that was getting
> > some DMA read errors. I've retired that drive, as well.
> >
> > While I'm tossing out advice, I'll also mention mondo.
> > http://www.microwerks.net/~hugo/index.html
> >
> > Mondo creates a bootable CD backup that will let you rebuild your
> > system from bare metal, if necessary. Wish I'd tried it out a month
> > ago, before my troubles started.
>
>
>
>