I currently have 4 Sata drives (one of which is the parity drive) and one ide drive attached to my array. Things were going **ok** when it was just the sata drives - except for the issue of the Realtek LAN driver, which I hope will be sorted with the next realease of Unraid in a wee while. LAN problems notwithstanding, I was still able to write to the array and so had filled up the sata drives with data. I then added the ide drive. Ever since adding the ide drive the array has crashed on a regular basis. The ide drive now has about 100gb of data on it. i did a parity check this afternoon, and after it ahd finished it reported "(Last checked on 3/5/2008 5:52:22 PM, finding 128 errors.)"!!!

 

I got hold of the syslog which reads as follows:

 

Tower login: root

 

[Disconnect bypassed -- root login allowed.]

Linux 2.6.22.5.

root@Tower:~# ifconfig

eth0      Link encap:Ethernet  HWaddr 00:1E:8C:1C:0D:12

          inet addr:192.168.0.180  Bcast:192.168.0.255  Mask:255.255.255.0

          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:8428 errors:0 dropped:0 overruns:0 frame:0

          TX packets:3387 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:1302354 (1.2 MiB)  TX bytes:2422146 (2.3 MiB)

          Interrupt:10 Base address:0xe000

 

lo        Link encap:Local Loopback

          inet addr:127.0.0.1  Mask:255.0.0.0

          UP LOOPBACK RUNNING  MTU:16436  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

 

root@Tower:~# tail -f /var/log/syslog

Mar  5 18:58:42 Tower kernel: [ 9918.307089] hdb: drive_cmd: error=0x04 { DriveStatusError }

Mar  5 18:58:42 Tower kernel: [ 9918.307093] ide: failed opcode was: 0xb0

Mar  5 18:58:42 Tower emhttp[1798]: get_temperature: ioctl (smart): Input/output error

Mar  5 19:00:28 Tower in.telnetd[1800]: connect from 192.168.0.157 (192.168.0.157)

Mar  5 19:01:06 Tower in.telnetd[1802]: connect from 192.168.0.157 (192.168.0.157)

Mar  5 19:01:16 Tower emhttp[1807]: get_temperature: ioctl (smart): Input/output error

Mar  5 19:01:16 Tower kernel: [10072.024412] hdb: drive_cmd: status=0x51 { Drive Ready SeekComplete Error }

Mar  5 19:01:16 Tower kernel: [10072.024420] hdb: drive_cmd: error=0x04 { DriveStatusError }

Mar  5 19:01:16 Tower kernel: [10072.024424] ide: failed opcode was: 0xb0

Mar  5 19:01:34 Tower login[1808]: ROOT LOGIN  on `pts/0' from `192.168.0.157'

 

'd be reallt grateful for any advice...

 

Could you give us a complete syslog, as well as tell us more about your hardware, especially what motherboard and addon cards.

 

To obtain a copy of your current syslog, at the unRAID console or in a Telnet session, type the command:

 

  cp  /var/log/syslog  /boot

 

This will make a copy of the system log in the root directory of your flash drive, which you can either copy directly from the flash share of your server, or plug the flash drive into your PC and access the syslog there.  Any file manager such as Windows Explorer can access the file across the network.  For example, if your unRAID server name is Tower, then you can access your newly created syslog as \\Tower\flash\syslog.  I recommend renaming it with the date and time and the .txt extension, for example syslog2007-08-28-1630.txt.

 

A helpful Wiki link:  http://lime-technology.com/wiki/index.php?title=Viewing_the_System_Log

 

The errors in your "tail syslog" seem to be related to getting the drive temperature.  Perhaps you can type:

cp  /var/log/syslog  /boot/syslog.txt

 

Then zip it and attach it to a post so we can see all the errors.

 

Many IDE errors can be traced to poor quality or out-of-spec IDE cables, or using older 40 conductor cables instead of newer 80 conductor cables.   

 

Are you using any older cables? or round cables (these are never in-spec).

 

Another possibility, but less likely is a marginal power supply, but since you don't have a lot of drives, that is probably not it.

 

Joe L.

System log attached (hopefully).

 

The disk status screen is just showing an asterisk in place of the temperature of the ide drive.

The errors in your "tail syslog" seem to be related to getting the drive temperature.  Perhaps you can type:

cp  /var/log/syslog  /boot/syslog.txt

 

Then zip it and attach it to a post so we can see all the errors.

 

Many IDE errors can be traced to poor quality or out-of-spec IDE cables, or using older 40 conductor cables instead of newer 80 conductor cables.   

 

Are you using any older cables? or round cables (these are never in-spec).

 

Another possibility, but less likely is a marginal power supply, but since you don't have a lot of drives, that is probably not it.

 

Joe L.

I'm using the brand new cable that came with the mobo Joe. Could the jumper setting affect it? I have it set to 'cable select'. The drive itself is a Seagate Barracuda 750GB that has been sitting in a Netgear SC101 for the last year or so running quite happily.

That drive is having a problem with its SMART system, may or may not be harmless.  There's a recent thread with a command to turn on SMART, might be interesting to try.  As well, it would be useful to try the smartctl tool on this drive.  Some other small changes you could try, change the jumpering to Single or Master, connect the cable to the other connector, and do try another cable, even though this one is new.

 

Threads about SMART:

http://lime-technology.com/forum/index.php?topic=1472

http://lime-technology.com/forum/index.php?topic=1521

 

Well, I ran the smartctl utility (see attached), which seems to have picked up a couple of errors, but I have to be honest and say that this is somewhat uncharted territory for me....

 

I think I'll change the ide cable as suggested and take it from there.

...on the other hand....having just rechecked the web info page, it now is showing the temperature! 

 

It's now runnig another parity check to see what, if any, errors it shows now. Is it worth re-installing the drive from scratch?

I did not see the cause of your parity errors.  They could be almost anything.

 

Good that you used the cable supplied by the MB.  Make sure the correct connector is attached to the motherboard. (usually it is the blue one. )  If you only have one drive connected, connect it to the end connector, not the one in the middle. It should not matter if it is cable select.

 

Yes, do another parity check.  It will let you know if problems still exist.  Post another syslog when it is completed.

 

Joe L.

 

 

Well, I ran the smartctl utility (see attached), which seems to have picked up a couple of errors

 

Your smartctl log looks quite clean to me, at least to these un-expert eyes, and SMART IS enabled (until the next reboot?!?).  Those errors showing are from a long time ago, probably within the first day or two of use.

 

Just completed another parity check, with zero errors.  It's also now managing to transfer files without crashing, althoughthis is still very slow (4.6MB/sec). hopefully the next Unraid release will fix that. I still have another 750GB ide drive to attach to the array, but the mobo only has a single ide connector. Do you think it will manage with two on one cable?

I'm sure the motherboard will handle two drives on one cable.

I don't think I've ever seen one that did not.

Well, I ran the smartctl utility (see attached), which seems to have picked up a couple of errors, but I have to be honest and say that this is somewhat uncharted territory for me....

 

I think I'll change the ide cable as suggested and take it from there.

 

I looked at this and noticed that the temperature on the drive goes up to 61C!  That is too hot.  The temp is reporting at 45C when the test was run.  That is pretty warm too.  I have exactly the same drive and my temp range is 23-40.  Not sure where the 40C came from - max in my case is about 33.  I'd recommend you look at cooling options for your case!

It's too bad that a timestamp isn't recorded for the highest temp, so we would know if that 61 occurred very early when those SMART errors occurred, or later when in the Netgear SC101, or recently in the unRAID case.  I don't know if that Netgear has a fan, but many drive enclosures get very hot!

 

Two things.

 

1) I've had brand new cables shipped with drives and M/Bs turn out to be bad. It's a royal PITA to troubleshoot since surely they are "high quality" so who would suspect but yup I've found bad ones before. Swapping it is a good idea, hopefully that will clear this up for good.

 

2) Checkout pastebin.com for logs. Slap that sucker on their site and link it, easy as can be and easy to read for others to troubleshoot too!

 

Okay, more thoughts heh. What's the current temp of the drive and how hot does it get when parity checking? I've got drives in little standalone enclosures too and even with the tiny fans in them the drives get scorching hot - not good for them longterm so hopefully no damage. Hopefully this drive is way cooler in this new case but check the temps anyway and try to keep them down. All of my drives get airflow in my NAS and except for infant mortality I generally do not have drive failures. If issues continue grab the drive checking utility on Seagate's site. Back it up first and then let that thing goto town, if it finds enough errors it'll be return time. Might want to check warranty status too while you're thinking about it. These days when I put a drive in I take a Sharpie and write the size and date put in service on the drive. Makes life easy when I can see size by the light of a flashlight while my head is poked in the case and by tracking service time I know about how many hours a drive has on it when and if it fails. Note that most companies seem to start the warranty period at manufacture date <sigh>