April 2, 201412 yr I restarted my Media Server (v5.0.5) and ever since I can no longer mount my primary User share on any device (at least OS X machines thus far); they all sit there in a seemingly never-ending wait cycle. Subsequent restarts have not resolved the issue. When I attempt to view my primary User share contents via the web GUI ("Shares" tab), the web page also appears to be stuck waiting for the page to be drawn. There are no apparent errors in the syslog. I can access the individual drives via web GUI as well as mounting successfully on client machines (though I haven't tried all 23 data drives yet). The SMART plug-in via unMENU shows no errors. I started a Resierfs check on the first data drive and it's still at it after an hour and a half (4TB drive). There are 13 4TB, 6 3TB, and 4 2TB data drives, and I'm afraid this will take at least a week to run a Resierfs check on every one of them, or longer since I cannot sit in front of the computer 24/7 to immediately interpret results and initiate the next scan. Once the first drive check completes, I will test all other User shares, mount all drives individually, and try mounting on non-OS X devices. What are my other courses of action beyond these?
April 3, 201412 yr Author I just came back home and saw the reiserfs check was clean, so I proceeded to view every individual drive, both via the web GUI and mounting them on my desktop: no problems. Next, I inspected and mounted every other User share: no problems. Finally, I held my breath and tried the problematic User share: mounted like a charm. I now believe this is somehow related to my suspicions of hardware performance issues, even though there are absolutely no errors ever reported by unRAID or the SMART plug-in. I had just posted a new thread regarding my concerns with the hardware when I experienced this apparently temporary issue with the User share: http://lime-technology.com/forum/index.php?topic=32687.msg300061#msg300061. I am now pursuing a course of action to systematically replace certain components of the system one-by-one to track down any potential hardware-related issues.
Archived
This topic is now archived and is closed to further replies.