Tight_wad

User Customizations · March 11, 2011

Since I started using the cache_dir, I am seeing faster write times with DVDFab to the unRAID. They are averaging about 1/3 faster than I have been normally getting. I am not complaining at all, but are improvements like this normal?

User Customizations · March 10, 2011

Set this up last night, and it really seems to make a difference with my XBMC live. Now I have a question.

When I need to powerdown, do I need to do it like this?

cache_dirs -q
powerdown

If I setup clean powerdown in the packages of unMENU, then I would just be able to do the powerdown, is that correct?

I tried to download the clean powerdown last night but it errored on me saying in the log that it could not be found. Not sure if I need to update my unMENU or not to get it to work, I'm using unMENU 1.3.

Thanks for this, combined with using the dds fanart, my XBMC is running smooth and snappy!

User Customizations · October 2, 2010

I changed my power cable to one that I have been using on a drive. I wish I could report that it made the difference, but it didn't. Totally frozen by 96% complete of step 2.

Time to RMA this drive.

User Customizations · October 1, 2010

Since you've already move the drive from one disk controller to another, it would eliminate the disk controller from being a possibility.

The drive initially responds when the SMART report is first performed and then it times-out. The OS resets it and tries again, it still fails to respond. All the subsequent writes to it fail with errors written to the syslog. Eventually, the syslog would grow to where it uses all memory, and your server would become un-responsive as you've discovered.

Only other possibility, besides the drive itself, would be a poor or intermittent power connection to the drive. (try an alternate power connection) Other than that... I'd say RMA the drive. Be thankful it was discovered before you tried using it in your array.

I will try it again tonight with a different power connection and see what it does. Right now it is on the last connection of 4 on the Corsair's power cable. Hopefully this is it.

Thank you

User Customizations · October 1, 2010

I had to add the syslog to the above post.

User Customizations · October 1, 2010

I ran a preclear on a Hitachi 2 tb drive yesterday and when it came towards the end I got this message

Sorry /dev/sdj mbr was not precleared or close to that. It made it through all but the final step.

This is actually my 3 time trying to run preclear on this drive. The first time, my system totally lockup, couldn't http in or telnet, and counsel was frozen, so I couldn't get a syslog. I was running 2 preclears at the same time. And both on the Sata Card ports.

I ran it again, this time just this drive, and did the same thing. And no syslog because everything froze.

So I thought 3rd times a charm. I moved this drive off of the Sata card, and on to the Motherboard port. Thinking that might help. I also ran the preclear with the (-n) as this preclear_disk.sh -n /dev/sdj. My thinking here was that it always made it up to the end, so if it worked this way, I would run it again. Well, it did and it didn't work. It failed, but this time, nothing locked up so I have a Syslog this time.

I have shortened the syslog at the point that it starts repeating similar info. If not it would be thousands of lines long and about 44Mb's.

I figure that I have a bad brand new hard drive, but would like someone to take a look if possible.

syslog.txt

User Customizations · September 25, 2010

Thats good news, the Hitachi drive indeed has bad airflow. It seems the bottom tray is around 5 degrees warmer then the top ones (Zalman 3-in-3 bay) and thats with an empty bay in the middle. But i'll try to play with the fans a little more to make it a little cooler, thanks for the help

If you put something in the empty bay to block the air, similar to how a drive would, that will improve the airflow around the disks.

User Customizations · September 24, 2010

Could someone take a look at my Syslog please.

I have 3 different drives running preclear right now. I thought I would look at my syslog, and I see errors at the end for all 3 drives concerning the SMART. I have precleared 8 other drives and never had this show up before. There are also several warnings that I am not sure of. Log is attached

Edit: Don't need an answer to the last question about "HDIO_GET_IDENTITY", found that in the UnMenu thread.

syslog-2010-09-23.txt

User Customizations · September 19, 2010

Here are my preclear results. What exactly do they mean? It says it was successfully precleared, but it has error?

ep 18 20:42:59 Tower preclear_disk-diff[31210]: ============================================================================