bburns

I am thinking of replacing my smaller disks with one larger disks. Can you reduce the number of disks in the array easily?

I have tried changing some of my Share parameters, because it appears that Unraid was not honoring the Share to drive assignments that I had setup (Share folders were on drives that were excluded). But now it appears that I can change any of them: allocation method, min free, etc. Here is the syslog snippet of when I tried to change the share parameters...any ideas on what is wrong? Jan 4 19:17:55 Ungol emhttp: put_config_idx: fopen /boot/config/shares/Meredith.cfg: Read-only file system (Other emhttp) Jan 4 19:17:55 Ungol emhttp: shcmd (195): :>/etc/samba/smb-shares.conf (Other emhttp) Jan 4 19:17:55 Ungol emhttp: Restart SMB... (Other emhttp) Jan 4 19:17:55 Ungol emhttp: shcmd (196): killall -HUP smbd (Minor Issues) Jan 4 19:17:55 Ungol emhttp: shcmd (197): ps axc | grep -q rpc.mountd (Other emhttp) Jan 4 19:17:55 Ungol emhttp: _shcmd: shcmd (197): exit status: 1 (Other emhttp) Jan 4 19:17:55 Ungol emhttp: shcmd (198): /usr/local/sbin/emhttp_event svcs_restarted (Other emhttp) Jan 4 19:17:55 Ungol emhttp_event: svcs_restarted (Other emhttp) Jan 4 19:18:13 Ungol emhttp: put_config_idx: fopen /boot/config/shares/TV.cfg: Read-only file system (Other emhttp) Jan 4 19:18:13 Ungol emhttp: shcmd (199): :>/etc/samba/smb-shares.conf (Other emhttp) Jan 4 19:18:13 Ungol emhttp: Restart SMB... (Other emhttp) Jan 4 19:18:13 Ungol emhttp: shcmd (200): killall -HUP smbd (Minor Issues) Jan 4 19:18:13 Ungol emhttp: shcmd (201): ps axc | grep -q rpc.mountd (Other emhttp) Jan 4 19:18:13 Ungol emhttp: _shcmd: shcmd (201): exit status: 1 (Other emhttp) Jan 4 19:18:13 Ungol emhttp: shcmd (202): /usr/local/sbin/emhttp_event svcs_restarted (Other emhttp) Jan 4 19:18:13 Ungol emhttp_event: svcs_restarted (Other emhttp)

I ran the "File System Check" from unmenu and it found two corruptions: Comparing bitmaps..Checking Semantic tree: finished 2 found corruptions can be fixed when running with --fix-fixable ########### I am now running the fix file system. Hopefully that fixes my problem.

I have already run it for 12 hours with no failures. I would think that at the rate that I'm seeing file corruption that memtest would have seen it very quickly.

So I removed the cache drive and I did more moving of large video files, but this time I used teracopy and verified each copy. I had about a 50% success rate of the first copy not having any errors:( So how should I go about debugging this? Is there a chkdsk program for unraid to see if there are bad sectors on the drives? Does the long SMART test identify bad sectors?

Here is the results: It seems okay to me? SMART status Info for /dev/sdm smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.10 family Device Model: ST3500630AS Serial Number: 9QG3W646 Firmware Version: 3.AAK User Capacity: 500,107,862,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Tue Dec 31 11:45:10 2013 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 430) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 163) minutes. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 108 097 006 Pre-fail Always - 30787889 3 Spin_Up_Time 0x0003 093 093 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 096 096 020 Old_age Always - 4890 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 087 060 030 Pre-fail Always - 520025772 9 Power_On_Hours 0x0032 054 054 000 Old_age Always - 40611 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 480 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 069 052 045 Old_age Always - 31 (Lifetime Min/Max 22/38) 194 Temperature_Celsius 0x0022 031 048 000 Old_age Always - 31 (0 11 0 0) 195 Hardware_ECC_Recovered 0x001a 063 056 000 Old_age Always - 240790440 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 17 200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0 202 TA_Increase_Count 0x0032 100 253 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 40602 - # 2 Extended offline Completed without error 00% 18731 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.

So after I removed my cache drive, I now am getting a disk space full error when I try to copy a file to one of my shares. My share settings are: Name: TV Comments: Allocation method: High-water Min. free space: Split level: 0 Included disk(s): disk6, disk7 Excluded disk(s): disk1,disk2,disk3,disk4,disk5,disk8 Share empty? No The disks 6 & 7 are 2TB and roughly 50% free each. I tried using a new disk for cache drive to see if the problem would go away, no joy:( I then tried changing some of the share setting, like Allocation Method and Min free space, but the changes don't seem to take effect?!?!? What is going on?

I removed my cache drive completely and copied the same file again. This time Teracopy verified the file correctly. So I guess my problem is with the cache drive. Although one test is not very definitive:) Should I run SMART on the cache drive? Is their a tool that I can use on a Windows PC to check the drive with? B2

I have an 8 port SATA card: Supermicro AOC-SASLP-MV8

My system is: MB: GIGABYTE GA-F2A85XM-D3H Processor: AMD A4-5300 APU with Radeon HD Graphics Memory: 8G Total disk: 8 2TB Data Disks + 1 2TB Parity disk + 500GB Cache Drive Just did another test. I copied a 4GB file to my unraid with Teracopy. The file was written to my cache drive. I then used Tearacopy to verify it and it was corrupt on the cache drive. So it must be getting corrupted on the initial write.

So I just checked the syslog and I see the following. Should I be concerned about the page errors or the ata error? Dec 28 12:54:10 Ungol kernel: [mem 0x00000000-0x000fffff] page 4k (Errors) Dec 28 12:54:10 Ungol kernel: [mem 0x37800000-0x379fffff] page 2M (Errors) Dec 28 12:54:10 Ungol kernel: [mem 0x34000000-0x377fffff] page 2M (Errors) Dec 28 12:54:10 Ungol kernel: [mem 0x00100000-0x001fffff] page 4k (Errors) Dec 28 12:54:10 Ungol kernel: [mem 0x00200000-0x33ffffff] page 2M (Errors) Dec 28 12:54:10 Ungol kernel: [mem 0x37a00000-0x37bfdfff] page 4k (Errors) Dec 28 12:54:10 Ungol kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20130117/tbfadt-599) (Minor Issues) Dec 28 12:54:10 Ungol kernel: sas: ata13: end_device-2:0: dev error handler (Errors) Dec 28 12:54:10 Ungol kernel: sas: ata13: end_device-2:0: dev error handler (Errors) Dec 28 12:54:10 Ungol kernel: sas: ata14: end_device-2:1: dev error handler (Errors) Dec 28 12:54:10 Ungol kernel: sas: ata13: end_device-2:0: dev error handler (Errors) Dec 28 12:54:10 Ungol kernel: sas: ata14: end_device-2:1: dev error handler (Errors) Dec 28 12:54:10 Ungol kernel: sas: ata15: end_device-2:2: dev error handler (Errors) Dec 28 12:54:10 Ungol kernel: sas: ata13: end_device-2:0: dev error handler (Errors) Dec 28 12:54:10 Ungol kernel: sas: ata14: end_device-2:1: dev error handler (Errors) Dec 28 12:54:10 Ungol kernel: sas: ata15: end_device-2:2: dev error handler (Errors) Dec 28 12:54:10 Ungol kernel: sas: ata16: end_device-2:3: dev error handler (Errors) Dec 28 12:54:11 Ungol avahi-daemon[1396]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! (Minor Issues) Dec 28 12:54:16 Ungol emhttp: shcmd (56): killall -HUP smbd (Minor Issues) Dec 29 03:52:08 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/movie.nfo (Minor Issues) Dec 29 03:52:08 Ungol logger: cd+++++++++ Movies/CouchPotato/Machete Kills (2013)/ (Minor Issues) Dec 29 03:52:08 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/movie.nfo (Minor Issues) Dec 29 03:52:08 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/movie.tbn (Minor Issues) Dec 29 03:52:08 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/movie.tbn (Minor Issues) Dec 29 03:52:08 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/Machete Kills.orig.nfo (Minor Issues) Dec 29 03:52:08 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/Machete Kills.orig.nfo (Minor Issues) Dec 29 03:52:08 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/Machete Kills.mkv (Minor Issues) Dec 29 03:52:08 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/Machete Kills.mkv (Minor Issues) Dec 29 03:54:05 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/Machete Kills.nfo (Minor Issues) Dec 29 03:54:05 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/Machete Kills.nfo (Minor Issues) Dec 29 03:54:05 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/Machete Kills.tbn (Minor Issues) Dec 29 03:54:05 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/Machete Kills.tbn (Minor Issues) Dec 29 03:54:05 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/fanart.jpg (Minor Issues) Dec 29 03:54:05 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/fanart.jpg (Minor Issues) Dec 29 03:54:05 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013)/Machete Kills-fanart.jpg (Minor Issues) Dec 29 03:54:05 Ungol logger: >f+++++++++ Movies/CouchPotato/Machete Kills (2013)/Machete Kills-fanart.jpg (Minor Issues) Dec 29 03:54:05 Ungol logger: ./Movies/CouchPotato/Machete Kills (2013) (Minor Issues)

I appear to be experiencing file corruption on my Unraid server:( I have noticed that many of my mkv files will stop playing periodically. It is almost like there is a bad spot in the file, if I skip over the place that it stops prematurely it will play fine?!?! Since it has been happening more and more frequently, I have started debugging it some. BTW I use XBMC to play my video stuff. If I play a failing file with VLC it seems to play fine. I have several XBMC machines and a failing file seems to fail on all machines at the same point, which lead me to believe that there must be something wrong with the file. So first I ran a memory check for 12 hours and it did not find any memory problems. I then performed a binary file compare on a failing file, which I had a backup copy on another machines. There was indeed file corruption:( Now I am extremely worried about other files on my system being corrupt. It doesn't happen all the time or at least I don't think so (maybe some corruption goes undetected). The problem seemed to start about the time that I upgraded my Unraid motherboard to a GIGABYTE GA-F2A85XM-D3H. Also at that time I upgraded UNRAID for 4.7 to 5.0 rc? and now I am running the released version of 5.0. This was around April. So where is the problem? - Motherboard? - UNRAID 5.0? - Network issue? Any Ideas on how to narrow down where the problem is? B2

I have been using this board since last April. I have noticed that many of my mkv files will stop playing periodically. It is almost like there is a bad spot in the file, if I skip over the place that it stops prematurely it will play fine?!?! I have not spent a lot of time debugging it since it doesn't happen on all files. It does seem to be happening more and more frequently. I use XBMC to play my video stuff. If I play a failing file with VLC it seems to play fine. I have several XBMC machines and a failing file seems to fail on all machines at the same point, which lead me to believe that there must be something wrong with the file. But a friend of mine who has a similar setup except he does not use Unraid can play the same file on his XBMC without a problem. Since the failure occurs at the same file location, that seemed to rule out network issues to me. So I have been wondering if it maybe MB related issues? My previous unraid MB did not seem to have this issue. I'm just not sure when exactly the problem started occurring. So I am thinking it must be either my MB or an Unraid glitch. I am running version 5.0. I think before upgrading the MB, I updated OS to one of the 5.0rc from 4.7? Any Ideas on how to narrow down where the problem is? B2

You guys were right on target!! Fortunately I backed up the files on the new flash before I copied my old files on to it. I was able to restore the Pro2.key file and everthing is working as it should now!! Thanks!!! B2

I purchased a new flash drive from Lime Tech. My existing system had 8 drives plus parity and cache. I copy all the files from my old flash drive to my new flash drive except for license.txt (I figured this was the license file for the new flash drive). When I boot, the main screen has an empty configuration:( I saved a printout of the old drive assignment page. So I tried to manually add the drives to the config, but it only allows you to add 2 drives plus parity. It seems that it does not recognize that I have the full version of Unraid...what did I do wrong?

I definitely had checked the BIOS boot order many times during the process. I finally left the server powered down for about 15 minutes and then powered on and it seemed to boot ok?!? This makes me concerned that the flash drive is marginal and may fail at any time. I think the original unmenu issue that started me down this path is a clue that the flash drive may be suspect. So what is the warranty on the flash drives? B2

I have been running my unraid server with the USB Flash drive that I purchased from Lime Tech over 4 years ago. I recently upgraded to the unRAIDServer-5.0-i386.zip image from 5.0 rc8 image. Everything seemed to go fine. The system booted recognized all of my disks correctly and performed a parity check without a problem. I then attempted to view an unmenu web page and got "e</BODY></HTML>0" back. I looked at the syslog and it said that the unmenu html file was not present. I then did an ls in /boot and it was empty. I shiut down the server and plug the flash into another PC and everything seemed good. I then place the flash back into my unraid server and powered on. Now it says there is not a boot device!! Tried all the USB ports same result. I then tried a Memtest86 USB boot stick I had and the system recognized it and booted. I then tried to load the Unraid on another Flash that use to boot ok, but it will not boot either (unraid server or other PC). So I suspect that my original Unraid USB drive maybe going bad. What should I do or try next? I would really like to get the system back up as soon as possible. I guess I could order another Flash from Lime tech. Is there a warranty on the Flash drives. Do I have to pay for the software again? B2

Is there a way to see which drive is attached to which SATA controller from the web interface or from the cli? I find that this would be very useful information, so I don't have to open the case and trace back cables.

I need to replace my Unraid MB, I have been trying to decide between an AM3+ board vs. FM2 Board. I was wondering if anyone had any experience with these in a Unraid server. The current Motherboard Compatibility list seems quite stale. Here is what I currently have: * ASUS M4A78 PRO with six SATA ports * AM2+ 3.2GHz Athlon II Quad core processor * SUPERMICRO AOC-SASLP-MV8 PCI-Express x4 Low Profile SAS RAID Controller * 4 Port SATA PCI E x1 * 4 Port SATA PCI * 8 GB RAM * 8 2TB Hard Drives (+parity + cache) Here are the ones I am looking at: GIGABYTE GA-970A-D3 AM3+ AMD 970 SATA 6Gb/s USB 3.0 ATX AMD Motherboard - http://www.newegg.com/Product/Product.aspx?Item=N82E16813128521 - 6 Onboard SATA but has NO video:( GIGABYTE GA-F2A85XM-D3H FM2 AMD A85X (Hudson D4) SATA 6Gb/s USB 3.0 HDMI Micro ATX AMD Motherboard - http://www.newegg.com/Product/Product.aspx?Item=N82E16813128572 - This has 8 onboard SATA Ports plus video Cost is almost identical. How does the Athlon II processors compare to A4-5300 Trinity processors?

If you mean making a new USB stick, I have tried a couple. From reading, some other forums this seems to be a problem with M4A78 PRO. I was just hoping that some other Unraid User who had a M4A78 Pro had found a workaround.

My old motherboard stopped reading the USB thumb drive this week (I tried all ports and all the USB headers, so I guess the USB controller died). So I re-purposed an ASUS M4A78 Pro motherboard that I already had. I upgraded the BIOS to the latest version. Now getting this board to boot from USB drive ia a PITA!! Since it appears on the hardware list, I assume someone has figured this out. The problem is that I have to press the F8 key at boot BIOS flash screen in order to get a boot menu that I can select the Unraid USB drive, thus requiring keyboard and monitor and me being physically present to boot the box. Here is what I have tried: Upgrade BIOS to latest from ASUS Disable Floppy Controller (no big deal, but I could not get USB to boot at all unless I did this) Made "Removable Device" first in BIOS boot priority list Removed all other possibilities from boot priority list Any ideas on what else to try? Thanks, b2

This is now happening every time I reboot my server:( I have to unplug it for a minute or so and then restart it. Anybody have any ideas what maybe causing this? B2

I recently upgraded from v4.7 to v5-rc8a and I have noticed that my unraid server does not always show up in the Network Explorer (Windows Explorer Network section) on my Win7 boxes. In the past, when the unraid server did not appear in the Network Explorer, I could just hit "refresh" and it would show up. However, now most times it will not show up, but then maybe an hour or so later it will be there...very strange. Now when it is not showing up in Network Explorer I know that I have network connectivity to it, because: I can telnet to it Access the Web GUI Mounted Shares have full access I can type in the path manually into Network Explorer and access the server So it is not really an issue...more of an annoyance. I'm not sure how windows decides to add a server to the network map. I'm guessing that unraid is not responding to some network query that windows is making.

After a cold reboot, it came up. Not sure if I have some hardware that is questionable or what.

I followed the instructions at http://lime-technology.com/wiki/index.php?title=UnRAID_Server_Version_5.0-beta_Release_Notes. When I rebooted, I got the attached screen (see screen shot) I have a total of 10 disks in my system: 1 parity, 1 cache and 8 data drives