This might sound crazy but I had a net5501 power supply go bad and how I
found out was hard drive errors. I first thought it was the drive and
replaced that but a brand new drive had the same errors minutes later.

I replaced the power supply and haven't had a problem since. I would
suggest atleast trying a new power supply.

On Mon, Mar 03, 2014 at 11:10:20PM +0100, Muffinman wrote:
> Hello all,
> 
> I've been running Voyage Linux + MPD on a net5501 for little over 2
> years now, and it has been running great. However, since a couple of
> months I've been noticing glitches in playback. It wasn't that often so
> I didn't bother to look into it. However, it has gotten worse and there
> are some troubling messages in dmesg. After a bit, the system becomes
> unresponsive (both ssh and serial) Here are some facts:
> - I'm not sure if there is a relation, but I started noticing it after I
> upgraded from Voyage Linux 7.5 to 9 (Debian Squeeze to Wheezy).
> - The music/data is stored on a sata drive, connected to an external
> sata drive containing 3.5" hdd.
> - It doesn't happen on cold boot. Last 2 times it happened after running
> for about 70 minutes.
> - After it happens, a reboot doesn't matter. After a reboot, sometimes
> the volume is mounted, but it's only a matter of minutes before the
> issue surfaces again
> - Most often, the volume is not mounted at this point on boot. Sometimes
> fdisk -l shows the disk, sometimes it doesn't. If I try to mount the
> volume, the system crashes (both ssh and serial).
> - When the system crashes the yellow disk becomes solid.
> Tried solutions:
> - I've tried different power supplies on both the external hdd and the
> net5501
> - I've tried different hdd casings/models
> - After failure of one drive, I've tried a different hdd with different
> enclosure. That didn't help.
> - Last time I checked SMART didn't show anything
> - the CF drive works like a charm
> 
> Below I've added some terminal output.
> 
> Does anyone know if this is a software or hardware issue? If software,
> does anyone know a (possible) solution. I'm especially troubled by the
> fact it only happens after a while and a reboot doesn't result in a
> similar cycle.
> 
> Thanks in advance,
> 
> Maarten
> 
> ssh output - the system was responsive, the hdd not:
> 
> [ 4198.734112] hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> [ 4198.739754] hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
> [ 4198.746650] hdb: possibly failed opcode: 0x35
> [ 4323.561751] hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> [ 4323.567315] hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
> [ 4323.576169] hdb: possibly failed opcode: 0x25
> 
> Serial console output - after the last message the system became
> unresponsive:
> 
> [ 1182.916830] hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> [ 1182.921766] hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
> [ 1182.927520] hdb: possibly failed opcode: 0x25
> [ 1183.277114] hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> [ 1183.282001] hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
> [ 1183.287754] hdb: possibly failed opcode: 0x25
> 
> ls
> cd ..
> ^C
> root@voyage:/mnt# cd [ 1203.347218] hdb: ide_dma_sff_timer_expiry: DMA
> status (0x61)
> 
> SSH output - I think the system became unresponsive, but I'm not 100%
> sure. I add this because the messages are a bit different:
> 
> [ 8873.557996] hdb: ide_dma_sff_timer_expiry: DMA status (0x61)
> [ 8883.572465] hdb: DMA timeout error
> [ 8883.573437] hdb: dma timeout error: status=0xd0 { Busy }
> [ 8883.573437] hdb: possibly failed opcode: 0x25
> [ 8883.573437] hda: DMA disabled
> [ 8883.573437] hdb: DMA disabled
> [ 8883.622452] ide0: reset: success
> [ 8883.624518] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 8883.628788] hdb: possibly failed opcode: 0x25
> [ 8883.629654] hdb: drive not ready for command
> [ 8883.679440] ide0: reset: success
> [ 8883.683496] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 8883.687756] hdb: possibly failed opcode: 0x25
> [ 8883.688623] hdb: drive not ready for command
> [ 8883.738431] ide0: reset: success
> [ 8883.742487] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 8883.746778] hdb: possibly failed opcode: 0x25
> [ 8883.747628] end_request: I/O error, dev hdb, sector 1700177527
> [ 8883.748639] hdb: drive not ready for command
> [ 8883.750277] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 8883.754232] hdb: possibly failed opcode: 0x25
> [ 8883.755425] hdb: DMA disabled
> [ 8883.757250] hdb: drive not ready for command
> [ 8883.805423] ide0: reset: success
> [ 8883.806844] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 8883.810812] hdb: possibly failed opcode: 0x25
> [ 8883.811945] hdb: drive not ready for command
> [ 8883.861414] ide0: reset: success
> [ 8883.865468] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 8883.869723] hdb: possibly failed opcode: 0x25
> [ 8883.870569] end_request: I/O error, dev hdb, sector 1950614151
> [ 8883.871580] hdb: drive not ready for command
> [ 8883.873222] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 8883.877177] hdb: possibly failed opcode: 0x25
> [ 8883.878308] hdb: drive not ready for command
> [ 8883.878941] Aborting journal on device hdb1-8.
> [ 8883.927402] ide0: reset: success
> [ 8883.929015] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 8883.933282] hdb: possibly failed opcode: 0x25
> [ 8883.934147] hdb: drive not ready for command
> [ 8883.983392] ide0: reset: success
> [ 8883.987449] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 8883.991717] hdb: possibly failed opcode: 0x25
> [ 8883.992560] end_request: I/O error, dev hdb, sector 1700177527
> [ 8883.993566] hdb: drive not ready for command
> [ 8883.995219] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 8883.999172] hdb: possibly failed opcode: 0x25
> [ 8884.000301] hdb: drive not ready for command
> [ 8884.049387] ide0: reset: success
> [ 8884.050834] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 8884.054800] hdb: possibly failed opcode: 0x25
> [ 8884.055935] hdb: drive not ready for command
> [ 8884.105376] ide0: reset: success
> [ 8884.109432] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 8884.113711] hdb: possibly failed opcode: 0x25
> [ 8884.114558] end_request: I/O error, dev hdb, sector 1950613567
> [ 8884.115553] Buffer I/O error on device hdb1, logical block 243826688
> [ 8884.116662] lost page write due to I/O error on hdb1
> [ 8884.117474] hdb: drive not ready for command
> [ 8884.119122] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 8884.123077] hdb: possibly failed opcode: 0x25
> [ 8884.124207] hdb: drive not ready for command
> [ 8884.124828] JBD2: Error -5 detected when updating journal superblock
> for hdb1-8.
> [ 8884.173364] ide0: reset: success
> [ 8884.177419] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 8884.181681] hdb: possibly failed opcode: 0x25
> [ 8884.182546] hdb: drive not ready for command
> [ 8884.232357] ide0: reset: success
> [ 8884.236415] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 8884.240702] hdb: possibly failed opcode: 0x25
> [ 8884.241544] end_request: I/O error, dev hdb, sector 63
> [ 8884.242379] Buffer I/O error on device hdb1, logical block 0
> [ 8884.243333] lost page write due to I/O error on hdb1
> [ 8884.245149] hdb: drive not ready for command
> [ 8884.245777] EXT4-fs error (device hdb1): ext4_journal_start_sb:349:
> Detected aborted journal
> [ 8884.248566] EXT4-fs (hdb1): Remounting filesystem read-only
> [ 8884.250007] EXT4-fs (hdb1): previous I/O error to superblock detected
> [ 8884.251685] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 8884.255982] hdb: possibly failed opcode: 0x25
> [ 8884.256846] hdb: drive not ready for command
> [ 8884.306347] ide0: reset: success
> [ 8884.310402] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 8884.314675] hdb: possibly failed opcode: 0x25
> [ 8884.315542] hdb: drive not ready for command
> [ 8884.365337] ide0: reset: success
> [ 8884.369395] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 8884.373698] hdb: possibly failed opcode: 0x25
> [ 8884.374540] end_request: I/O error, dev hdb, sector 63
> [ 8884.375376] Buffer I/O error on device hdb1, logical block 0
> [ 8884.376327] lost page write due to I/O error on hdb1
> [ 8884.378141] hdb: drive not ready for command
> [ 8884.379554] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 8884.383895] hdb: possibly failed opcode: 0x25
> [ 8884.384760] hdb: drive not ready for command
> [ 8884.434327] ide0: reset: success
> [ 8884.438382] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 8884.442642] hdb: possibly failed opcode: 0x25
> [ 8884.443508] hdb: drive not ready for command
> [ 8884.493316] ide0: reset: success
> [ 8884.497373] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 8884.501662] hdb: possibly failed opcode: 0x25
> [ 8884.502664] end_request: I/O error, dev hdb, sector 1700177527
> [ 8884.503678] hdb: drive not ready for command
> [ 8884.506169] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 8884.511305] hdb: possibly failed opcode: 0x25
> [ 8884.512449] hdb: drive not ready for command
> [ 8884.562309] ide0: reset: success
> [ 8884.566367] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 8884.570649] hdb: possibly failed opcode: 0x25
> [ 8884.571518] hdb: drive not ready for command
> [ 8884.621296] ide0: reset: success
> [ 8884.625351] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 8884.629618] hdb: possibly failed opcode: 0x25
> [ 8884.630621] end_request: I/O error, dev hdb, sector 1700151359
> [ 8884.631636] hdb: drive not ready for command
> [ 8884.633374] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 8884.637438] hdb: possibly failed opcode: 0x25
> [ 8884.638624] hdb: drive not ready for command
> [ 8884.688287] ide0: reset: success
> [ 8884.692344] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 8884.696620] hdb: possibly failed opcode: 0x25
> [ 8884.697484] hdb: drive not ready for command
> [ 8884.747278] ide0: reset: success
> [ 8884.751334] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 8884.755588] hdb: possibly failed opcode: 0x25
> [ 8884.756432] end_request: I/O error, dev hdb, sector 1700151359
> [ 8884.757445] hdb: drive not ready for command
> [ 8884.760380] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 8884.764398] hdb: possibly failed opcode: 0x25
> [ 8884.765584] hdb: drive not ready for command
> [ 8884.815270] ide0: reset: success
> [ 8884.819327] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 8884.823631] hdb: possibly failed opcode: 0x25
> [ 8884.824497] hdb: drive not ready for command
> [ 8884.874258] ide0: reset: success
> [ 8884.878312] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 8884.882600] hdb: possibly failed opcode: 0x25
> [ 8884.883444] end_request: I/O error, dev hdb, sector 1700151359
> [ 8884.884459] hdb: drive not ready for command
> [ 9035.102784] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 9035.108182] hdb: possibly failed opcode: 0x25
> [ 9035.109054] hdb: drive not ready for command
> [ 9035.158342] ide0: reset: success
> [ 9035.162401] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 9035.166671] hdb: possibly failed opcode: 0x25
> [ 9035.167539] hdb: drive not ready for command
> [ 9035.217322] ide0: reset: success
> [ 9035.221379] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 9035.225640] hdb: possibly failed opcode: 0x25
> [ 9035.226486] end_request: I/O error, dev hdb, sector 1700237951
> [ 9035.227505] hdb: drive not ready for command
> [ 9035.229712] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 9035.233985] hdb: possibly failed opcode: 0x25
> [ 9035.234850] hdb: drive not ready for command
> [ 9035.284313] ide0: reset: success
> [ 9035.288371] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 9035.292736] hdb: possibly failed opcode: 0x25
> [ 9035.293600] hdb: drive not ready for command
> [ 9035.343303] ide0: reset: success
> [ 9035.347358] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 9035.351647] hdb: possibly failed opcode: 0x25
> [ 9035.352495] end_request: I/O error, dev hdb, sector 1700237951
> [ 9035.353507] hdb: drive not ready for command
> [ 9035.355696] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 9035.359995] hdb: possibly failed opcode: 0x25
> [ 9035.360861] hdb: drive not ready for command
> [ 9035.410293] ide0: reset: success
> [ 9035.414350] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 9035.418639] hdb: possibly failed opcode: 0x25
> [ 9035.419505] hdb: drive not ready for command
> [ 9035.469284] ide0: reset: success
> [ 9035.473337] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 9035.477607] hdb: possibly failed opcode: 0x25
> [ 9035.478450] end_request: I/O error, dev hdb, sector 1700237951
> [ 9035.479460] hdb: drive not ready for command
> [ 9035.481912] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 9035.485951] hdb: possibly failed opcode: 0x25
> [ 9035.487133] hdb: drive not ready for command
> [ 9035.536274] ide0: reset: success
> [ 9035.540335] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 9035.544596] hdb: possibly failed opcode: 0x25
> [ 9035.545464] hdb: drive not ready for command
> [ 9035.595264] ide0: reset: success
> [ 9035.599319] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 9035.603616] hdb: possibly failed opcode: 0x25
> [ 9035.604462] end_request: I/O error, dev hdb, sector 1700184127
> [ 9035.605480] hdb: drive not ready for command
> [ 9035.607631] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 9035.611912] hdb: possibly failed opcode: 0x25
> [ 9035.612776] hdb: drive not ready for command
> [ 9035.662256] ide0: reset: success
> [ 9035.666310] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 9035.670607] hdb: possibly failed opcode: 0x25
> [ 9035.671473] hdb: drive not ready for command
> [ 9035.721245] ide0: reset: success
> [ 9035.725301] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 9035.729576] hdb: possibly failed opcode: 0x25
> [ 9035.730418] end_request: I/O error, dev hdb, sector 1700184127
> [ 9035.731431] hdb: drive not ready for command
> [ 9035.734075] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 9035.739131] hdb: possibly failed opcode: 0x25
> [ 9035.739317] hdb: drive not ready for command
> [ 9035.789237] ide0: reset: success
> [ 9035.793293] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 9035.797565] hdb: possibly failed opcode: 0x25
> [ 9035.798430] hdb: drive not ready for command
> [ 9035.848228] ide0: reset: success
> [ 9035.852283] hdb: status error: status=0x30 { DeviceFault SeekComplete }
> [ 9035.856584] hdb: possibly failed opcode: 0x25
> [ 9035.857431] end_request: I/O error, dev hdb, sector 1700184127
> [ 9035.858440] hdb: drive not ready for command
> _______________________________________________
> Soekris-tech mailing list
> [email protected]
> http://lists.soekris.com/mailman/listinfo/soekris-tech
> 

-- 
James Turner
_______________________________________________
Soekris-tech mailing list
[email protected]
http://lists.soekris.com/mailman/listinfo/soekris-tech

Reply via email to