HiSoC8Y

Ah ok, thanks. I didn't know that. But the problem is, If i convert my disks, then I can never roll back to v5, right? I wouldn't actually want to rollback if this problem is fixed.

Hi unRAIDers, 10 days ago I upgraded my unRAID from 5.0.6 to 6.3.5. My unRAID is on ESXi as a VM, and I have passed thru the disks. Due to the known issue of usb and unRAID as VM, I have an extra usb plugged in and passed thru to the unRAID to stop the usb warning alerts (this a link to the known issue): Since the upgrade, my unRAID system becomes totally unresponsive and the GUI doesn't reload, and I can't access the shares. I have to shutdown the unRAID (force it, unclean shutdown). The problem is, before the system becomes unresponsive, there are no warnings or errors in the logs, and when it becomes unresponsive, and after the force shutdown, there is nothing in the logs either. I'm honestly stuck, as this will eventually hurt my setup if I continue to forcefully shutdown. Any help will be appreciated.

ok, i upgraded to 6.1.9 and it's a really bad version for me. It just doesnt work, works a bit, and then it stops. Can't even stop the array, i have to shut it down improperly every time, I've done this about 10 times so far. So I want to rollback to the previous version i had, 5.0.5. I have a full backup of my USB, of 5.0.5. What is the procedure to revert back? by the way, I haven't formatted any hard drives yet to the new format, as I was expecting to roll back. Thanks

Hi I just upgraded to 6.1.9 from 5.0.5. I didn't convert any of the disks to the new format. I don't have a parity disk installed. I have a total of 16 drives, 80+ TB. Everything is fine, until late night (seems around 2-3 am). When i wake up in the morning, I can't access the network shares from my PC, it just shows that it's trying to open it (the clock icon). from the unRAID GUI, When I refresh, it goes on and on, to refresh but it never completes it. Also, my plex server can't read from the network shares anymore. I'm forced to shutdown the unRAID without the proper shutdown procedure. This is happening every night since I upgraded. I'm noticing that it's happening when no access to the shares for a long time (3 am), where I don't have my family watching content off my plex server, the content is stored on the unRAID shares. Any idea how to fix this?

here is a copy of my log http://pastebin.com/gYGFprya

Ok I was running a parity check, building my parity drive, and suddenly the system is showing my shares are empty. So i stopped the array, and restarted unRAID, brought it up, and now, one of my disks (disk2) is showing as unformatted. I had 3 TB of data on it. Is there a way to recover it?

unRAID as a VM?

Ok, just to confirm, unRAID as VM is supported with 6.1.9, without any workarounds. Correct?

Ok, so I'm a newbie with the SMART reports. I did run the preclear_script.sh on an HGST 8 TB drive, took 59 hours. I checked the SMART logs (below), can't understand it well honestly. Am i good to go to use the drive as my parity or there is something with it? The start report: Disk: /dev/sdb smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: HGST HUH728080ALE604 Serial Number: 2EG25V1P LU WWN Device Id: 5 000cca 23bc0feaa Firmware Version: A4GNW514 User Capacity: 8,001,563,222,016 bytes [8.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Thu Dec 10 02:58:33 2015 PST 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: (0x80) Offline data collection activity was never started. 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: ( 101) 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: ( 2) minutes. Extended self-test routine recommended polling time: (1267) minutes. SCT capabilities: (0x003d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 100 100 054 Pre-fail Offline - 0 3 Spin_Up_Time 0x0007 100 100 024 Pre-fail Always - 0 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 4 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 100 100 020 Pre-fail Offline - 0 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 1 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 4 22 Unknown_Attribute 0x0023 100 100 025 Pre-fail Always - 100 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 8 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 8 194 Temperature_Celsius 0x0002 176 176 000 Old_age Always - 34 (Min/Max 22/34) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 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 Short offline Aborted by host 90% 0 - 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. The Finish report: Disk: /dev/sdb smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: HGST HUH728080ALE604 Serial Number: 2EG25V1P LU WWN Device Id: 5 000cca 23bc0feaa Firmware Version: A4GNW514 User Capacity: 8,001,563,222,016 bytes [8.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Sat Dec 12 14:13:55 2015 PST 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: (0x84) Offline data collection activity was suspended by an interrupting command from host. 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: ( 101) 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: ( 2) minutes. Extended self-test routine recommended polling time: (1267) minutes. SCT capabilities: (0x003d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 129 129 054 Pre-fail Offline - 124 3 Spin_Up_Time 0x0007 100 100 024 Pre-fail Always - 0 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 4 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 100 100 020 Pre-fail Offline - 0 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 60 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 4 22 Unknown_Attribute 0x0023 100 100 025 Pre-fail Always - 100 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 10 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 10 194 Temperature_Celsius 0x0002 181 181 000 Old_age Always - 33 (Min/Max 22/34) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 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 Short offline Aborted by host 90% 0 - 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. and the RPT report: ========================================================================1.15 == invoked as: ./preclear_disk.sh /dev/sdb == HGSTHUH728080ALE604 2EG25V1P == Disk /dev/sdb has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 14:54:23 (149 MB/s) == Last Cycle's Zeroing time : 13:53:11 (160 MB/s) == Last Cycle's Post Read Time : 30:26:49 (72 MB/s) == Last Cycle's Total Time : 59:15:23 == == Total Elapsed Time 59:15:23 == == Disk Start Temperature: 34C == == Current Disk Temperature: 33C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Throughput_Performance = 129 100 54 ok 124 Temperature_Celsius = 181 176 0 ok 33 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================

Got another question. I'm currently using the Norco-4224, which connects the HDDs via SFF8087 connectors, not SATA 3. Is it possible to use some sort of cables/converters to use the same method as Norco? that means, connecting multiple HDDs via SFF8087 connector to my SATA Controller card. This way, I want to reduce connecting each HDD to the motherboard via the traditional SATA cable. Possible? If so, any recommendations?

thanks everyone for your valuable inputs and feedback. Now i'm seriously thinking of getting it. when i browse the lian-li website, their accessories page, how can i determine which parts are compatible with the D8000? About the fans, I own and love the Noctua fans, will they will work this case? if so, which ones for which part of the case?

Ok, so I'm looking to replace my Norco 4224 box. Someone suggested the Lian-Li D8000, which from the first impression i loved it. I like the idea of the available space in the box, many possibilities! So who has experience with this? what are the cons of it, and how to overcome them? What additional accessories should i get if i decide to buy it? Because my Norco 4224 connects the HDDs to the cards via the cables (SFF-8087 to SFF-8087), and the Lian-Li D8000 doesn't have that backplane for each HDD slot, what will be the solution?

Very interesting! I like it a lot. Anyone out there who has this case?

Ok, So here is my build, My711 https://lime-technology.com/forum/index.php?topic=21470.0 I'm using LSI MegaRAID card with an Intel RAID Twenty-four port Expander Card RES2SV240. disks 1-4 are connected via one port directly to the LSI MegaRAID card. disks 5-8 are connected via one port directly to the Intel expander card. disks 9-12 are connected via one port directly to the Intel expander card. disks 13-16 are connected via one port directly to the Intel expander card. disks 17-20 are connected via one port directly to the Intel expander card. disks 21-24 are connected via one port directly to the Intel expander card. and the two cards are connected via a port on each. When I transfer large amount of data from disk 3 to disk 10 for example, can someone explain the data transmission? What about if I transfer data between two disks that are using the same port connection (e.g. disk18 to disk19)? Will it be faster? I need to identify the bottlenecks in the above tasks.

please describe, what you tried ? and give us some info about your setup.. Ok, I tried the workaround mentioned (using two USBs) with plop, no go. About the other recommendation of passing thru the USB controller, I can't do that, because i'm using a USB as my ESXi OS. I was having a difficulty distinguishing between all the listed controllers in the ESXi passthru list. Therefore, I didn't try it, didn't want to risk it.

I tried some of the workarounds mentioned, none of them worked. Can someone list all the workarounds?

Ok I want to know what would you recommend for a case, Tower only, that can hold the maximum number of HDDs (via HDD bays). I'm not looking for a rackmount case. Thnx

After I went through the hassle of upgrading, on the first boot which was successful, I noticed the slowness, and I came to know that it's not supported with unRAID as a virtual machine, the topic of this thread. This is really disappointing from the unRAID team, how can they not support this out of the box in the first release? having unRAID as a VM is very common nowadays. I had to rollback, deleted all the content of the USB (v6.1.3 content) and copied back my 5.0.5 content and brought my unRAID back up for the time being.

Hi Can i use this same method for unRAID 6?

Maybe i didn't explain it, this drive that i tried to use as parity, only remaining building parity for 10 minutes maybe and then i stopped it because it was too slow. So with that case, do I still need to preclear it before using this same disk as a data disk? I will not have any parity for now, I don't care for now.

Ok So I was planning to use a disk as a parity, and for technical reasons, I can't (don't worry about the details of this..) I already precleared this disk that took about 2 days (it's a 6 TB). When I first tried to use it as parity, it was too slow because I think I reached the max # of drives my system can handle. Now, I want to use it as a data disk. my question is: - If i set it as a data disk, will it preclear again, or it won't? Thanks

Ok So i came home and found that the unRAID is unresponsive. I had no choice but to shutdown the VM (unRAID VM) and start it again. Kindly note that I'm not running a parity drive. 1. How can I see what went wrong that the array stopped functioning? 2. Now after I started the system, what do I need to do to make sure the system is fine?

I started reading about the next gen SSDs, with NVMe. Here is one by Intel on newegg.com Intel 750 Series SSDPEDMW400G4R5 HHHL (CEM2.0) 400GB PCIe NVMe 3.0 x4 MLC Internal Solid State Drive (SSD) http://www.newegg.com/Product/Product.aspx?Item=N82E16820167300&cm_re=NVMe-_-20-167-300-_-Product From an unRAID perspective, will we see any differences over normal SSDs? Your thoughts are welcome!

Thanks see, building a rig is tricky, they make you change your whole system with all these limited configs. lol If I change my motherboard, i might as well change the cards, memory, cpu...etc. One question I have in regards to CrashPlan. CrashPlan, by standard, doesn't allow to backup a mapped drive (network drive), but with v6, will I be able to backup my entire array?

Is it better to connect directly to the SATA ports on the motherboard or via a card? Any difference btw?