NASLite Network Attached Storage

www.serverelements.com
Task-specific simplicity with low hardware requirements.
It is currently Fri Apr 19, 2024 9:28 am

All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 4 posts ] 
Author Message
 Post subject: sys log error
PostPosted: Mon Apr 15, 2013 1:28 pm 
Offline

Joined: Tue Nov 13, 2007 4:37 pm
Posts: 160
Location: Leeds, West yorkshire, uk
Can anybody shed some lite on this error log please ?

•Apr 15 17:58:13 [5] hde: task_pio_intr: status=0x51 { DriveReady SeekComplete Error }
•Apr 15 17:58:13 [5] hde: task_pio_intr: error=0x04 { DriveStatusError }
•Apr 15 17:58:13 [5] hde: possibly failed opcode: 0xa1
•Apr 15 17:58:13 [5] hde: task_pio_intr: status=0x51 { DriveReady SeekComplete Error }
•Apr 15 17:58:13 [5] hde: task_pio_intr: error=0x04 { DriveStatusError }
•Apr 15 17:58:13 [5] hde: possibly failed opcode: 0xa1
•Apr 15 17:58:13 [5] hde: task_pio_intr: status=0x51 { DriveReady SeekComplete Error }
•Apr 15 17:58:13 [5] hde: task_pio_intr: error=0x04 { DriveStatusError }
•Apr 15 17:58:13 [5] hde: possibly failed opcode: 0xa1
•Apr 15 17:58:17 [2] sky2 eth0: enabling interface
•Apr 15 17:58:19 [2] sky2 eth0: Link is up at 1000 Mbps, full duplex, flow control both
•Apr 15 17:58:27 [5] hde: task_pio_intr: status=0x51 { DriveReady SeekComplete Error }
•Apr 15 17:58:27 [5] hde: task_pio_intr: error=0x04 { DriveStatusError }
•Apr 15 17:58:27 [5] hde: possibly failed opcode: 0xa1


a strange thing happened at the weekend one of my drives disapeered in the listing

rebooted nas box and drive 3 reported as failed.
removed drive and tested with Western Digitals data life guard diagnostics no errors where reported on s.m.a.r.t or on bad blocks

reformatted again and put back into service . .
just looked now and have the following errors

steve


Top
 Profile  
 
 Post subject: Re: sys log error
PostPosted: Mon Apr 15, 2013 5:23 pm 
Offline

Joined: Sat Nov 19, 2005 6:39 pm
Posts: 633
Location: California
Difficult to diagnose. But if the disk diagnostics passed you should look at anything hardware related except the disks. Including something as simple as cabling. I had a case like this recently ... thought my disks were going bad, but it turned out to be the SATA controller on the motherboard. The errors would appear after running fine for several days. I ended up replacing the motherboard. No more trouble with the same disk drives.


Top
 Profile  
 
 Post subject: Re: sys log error
PostPosted: Tue Apr 16, 2013 11:53 am 
Offline

Joined: Tue Nov 13, 2007 4:37 pm
Posts: 160
Location: Leeds, West yorkshire, uk
georg i replaced the sata cable as a matter of course

will try another port and have a go

cheers

steve


Top
 Profile  
 
 Post subject: Re: sys log error
PostPosted: Wed Apr 17, 2013 12:42 am 
Offline

Joined: Tue Nov 13, 2007 4:37 pm
Posts: 160
Location: Leeds, West yorkshire, uk
dam thing started to beep its little head off last nite .

suspect drive 3 is not mounted as i have not sorted it out yet

got this error log is it all part of same thing or somthing different

Apr 15 18:01:00 [2] warning: `smbd' uses 32-bit capabilities (legacy support in use)
Apr 16 00:01:59 [5] hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Apr 16 00:01:59 [5] hdg: dma_intr: error=0x40 { UncorrectableError }, LBAsect=889733070, sector=889733065
Apr 16 00:01:59 [5] hdg: possibly failed opcode: 0x25
Apr 16 00:01:59 [5] end_request: I/O error, dev hdg, sector 889733065
Apr 17 00:01:23 [6] EXT2-fs error (device hdg1): ext2_check_page: bad entry in directory #26150738: : unaligned directory entry - offset=0, inode=4050264272, rec_len=23921, name_len=83
Apr 17 00:01:23 [6] EXT2-fs error (device hdg1): ext2_check_page: bad entry in directory #26150739: : unaligned directory entry - offset=0, inode=4227810971, rec_len=25826, name_len=197
Apr 17 00:01:23 [6] EXT2-fs error (device hdg1): ext2_check_page: bad entry in directory #26479020: : unaligned directory entry - offset=0, inode=4227628539, rec_len=65529, name_len=247
Apr 17 00:01:23 [6] EXT2-fs error (device hdg1): ext2_check_page: bad entry in directory #26479021: : directory entry across blocks - offset=0, inode=1222364124, rec_len=12412, name_len=80
Apr 17 00:01:26 [6] EXT2-fs error (device hdg1): ext2_free_blocks: Freeing blocks not in datazone - block = 743438679, count = 1
Apr 17 00:01:26 [6] EXT2-fs error (device hdg1): ext2_free_blocks: Freeing blocks not in datazone - block = 2329683122, count = 1
Apr 17 00:01:26 [6] EXT2-fs error (device hdg1): ext2_free_blocks: Freeing blocks not in datazone - block = 3295995547, count = 1


Apr 17 00:01:43 [6] EXT2-fs error (device hdg1): ext2_check_page: bad entry in directory #25264253: : unaligned directory entry - offset=0, inode=1159558622, rec_len=199, name_len=8
Apr 17 00:01:43 [6] EXT2-fs error (device hdg1): ext2_check_page: bad entry in directory #25264254: : unaligned directory entry - offset=0, inode=2946588519, rec_len=21077, name_len=154

steve


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 4 posts ] 

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 69 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group