thegizzard

This is the array now. It's building parity for parity disk 2 but shows 5.04 TB free in the array. Am I reading this correctly? Sent from my SM-N950U using Tapatalk

Correct. I did not do a new config. All I did was add a new parity disk parity 2. I stop the array, and then I assigned the new disc to parity too. I thought I had a good understanding of how parity works when I have a single parity disk. I have not done any investigation on how parity to affects the size of the array. I assume that what is happening is exactly what should be happening. It does not look like an error. I am simply surprised that the size of the array increased by adding a parity disc. In the past, I do not remember increasing the size of the parity disk changing the amount of available free space in the array. I expect that what is happening is something that I simply do not understand but is all good. When I get back home I can show you a picture of the before and after configuration. Like I said it seems that half the size of the new disc was added to the amount of available free space in the array. It seems like the second parity disk allowed less of the data disks to be used for parity. Or something like that. Sent from my SM-N950U using Tapatalk

I am sure this is a simple question. I just added Parity 2 for the first time. It added about 4 TB of space to my array. With the new config I now have 2 8TB parity disks. Can someone explain why free space was added with my second Parity disk?

Is this still the best tool for this function?

It seems I need to restart Zoneminder somewhsy frequently. Is there a way to put it on a reboot schedule? Sent from my SM-N950U using Tapatalk

That worked. Thanks Sent from my SM-N950U using Tapatalk

I copied the cache drive, formatted BRFS, copied data back, but now the docker won't start. Can anyone assist? Diagnostics attached. grimlock-diagnostics-20180115-0149.zip

I guess some changes were made to UD? A year or so ago I lost all my data because I used UD in an attempt to migrate my disks to XFS. After I copied all of the data, UNRAID didn't recognize the UD XFS partitions. Fortunately I had an off-site back up for everything critical, but my takeaway was to on trust UNRAID to format a drive. Sent from my SM-N950U using Tapatalk

Is there a preferred filesystem for the cache drive now? Xfs vs Brfs? Sent from my SM-N950U using Tapatalk

I am pretty sure I formatted it originally with UD. I'll give that a try since I know I can go back and forth if I need to.

Reverting back to 6.3.5 fixed it. Whew. Not sure why that happened. But I will avoid 6.4 for now.

Can I downgrade back to the last stable release and see if this problem goes away?

I just upgraded. Unraid now says my Cache Drive is Unmountable. It is a brtfs 1 TB SSD. All my dockers were on there. I hope they are not lost. Help. Diagnostics attached. grimlock-diagnostics-20180114-1057.zip

You guys are great. This drive is a warranty replacement. I just received it from the Amazon Marketplace vendor. As a warranty replacement, I did not necessarily expect it to be new. But I wanted to check it out for health before using it. I took these stats before I started my first PRECLEAR. I will run 3 preclears and see how it holds up. Thanks guys. For giggles I will reach out to the Amazon Marketplace vendor and ask about the drives origin. Sent from my SM-N920V using Tapatalk

Should I be worried about anything here? # Attribute Name Flag Value Worst Threshold Type Updated Failed Raw Value 1 Raw read error rate 0x000f 118 099 006 Pre-fail Always Never 172238720 3 Spin up time 0x0003 093 091 000 Pre-fail Always Never 0 4 Start stop count 0x0032 100 100 020 Old age Always Never 554 5 Reallocated sector count 0x0033 100 100 010 Pre-fail Always Never 0 7 Seek error rate 0x000f 078 060 030 Pre-fail Always Never 4376309874 9 Power on hours 0x0032 099 099 000 Old age Always Never 1458 (2m, 1d, 18h) 10 Spin retry count 0x0013 100 100 097 Pre-fail Always Never 0 12 Power cycle count 0x0032 100 100 020 Old age Always Never 128 183 Runtime bad block 0x0032 100 100 000 Old age Always Never 0 184 End-to-end error 0x0032 100 100 099 Old age Always Never 0 187 Reported uncorrect 0x0032 100 100 000 Old age Always Never 0 188 Command timeout 0x0032 100 099 000 Old age Always Never 8590065671 189 High fly writes 0x003a 100 100 000 Old age Always Never 0 190 Airflow temperature cel 0x0022 076 032 045 Old age Always In the past 24 (1 169 24 21 0) 191 G-sense error rate 0x0032 100 100 000 Old age Always Never 0 192 Power-off retract count 0x0032 100 100 000 Old age Always Never 420 193 Load cycle count 0x0032 100 100 000 Old age Always Never 1426 194 Temperature celsius 0x0022 024 068 000 Old age Always Never 24 (0 18 0 0 0) 195 Hardware ECC recovered 0x001a 118 099 000 Old age Always Never 172238720 197 Current pending sector 0x0012 100 100 000 Old age Always Never 0 198 Offline uncorrectable 0x0010 100 100 000 Old age Offline Never 0 199 UDMA CRC error count 0x003e 200 200 000 Old age Always Never 0 240 Head flying hours 0x0000 100 253 000 Old age Offline Never 455 (44 205 0) 241 Total lbas written 0x0000 100 253 000 Old age Offline Never 38398887063 242 Total lbas read 0x0000 100 253 000 Old age Offline Never 431466919958

Ok. I replaced P1 DIMM 3A with a spare 8 GB stick and it seems to be running fine and reporting 48 GB of Ram. Thanks again GC.

I think I have an approach. The following command gives this output. It shows I have 5 x 8GB sticks installed. But I know I have 6x 8gb sticks installed. The Locator field tells me the name of the DIMM Slot. So it looks like P1 DIMM 3A is either a bad slot or had a bad stick. Did I interpret this properly? I have attached a diagram of the motherboard. # dmidecode -t 17 # dmidecode 3.0 Getting SMBIOS data from sysfs. SMBIOS 2.6 present. Handle 0x0017, DMI type 17, 28 bytes Memory Device Array Handle: 0x0015 Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: 8192 MB Form Factor: DIMM Set: None Locator: P1-DIMM1A Bank Locator: BANK0 Type: DDR3 Type Detail: Other Speed: 1066 MHz Manufacturer: Hyundai Serial Number: C9B4A928 Asset Tag: Part Number: HMT31GR7BFR4C-H9 Rank: Unknown Handle 0x0019, DMI type 17, 28 bytes Memory Device Array Handle: 0x0015 Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: No Module Installed Form Factor: DIMM Set: None Locator: P1-DIMM1B Bank Locator: BANK1 Type: DDR3 Type Detail: Other Speed: Unknown Manufacturer: Serial Number: Asset Tag: Part Number: Rank: Unknown Handle 0x001B, DMI type 17, 28 bytes Memory Device Array Handle: 0x0015 Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: No Module Installed Form Factor: DIMM Set: None Locator: P1-DIMM1C Bank Locator: BANK2 Type: DDR3 Type Detail: Other Speed: Unknown Manufacturer: Serial Number: Asset Tag: Part Number: Rank: Unknown Handle 0x001D, DMI type 17, 28 bytes Memory Device Array Handle: 0x0015 Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: 8192 MB Form Factor: DIMM Set: None Locator: P1-DIMM2A Bank Locator: BANK3 Type: DDR3 Type Detail: Other Speed: 1066 MHz Manufacturer: Hyundai Serial Number: 59833027 Asset Tag: Part Number: HMT31GR7BFR4C-H9 Rank: Unknown Handle 0x001F, DMI type 17, 28 bytes Memory Device Array Handle: 0x0015 Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: No Module Installed Form Factor: DIMM Set: None Locator: P1-DIMM2B Bank Locator: BANK4 Type: DDR3 Type Detail: Other Speed: Unknown Manufacturer: Serial Number: Asset Tag: Part Number: Rank: Unknown Handle 0x0021, DMI type 17, 28 bytes Memory Device Array Handle: 0x0015 Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: No Module Installed Form Factor: DIMM Set: None Locator: P1-DIMM2C Bank Locator: BANK5 Type: DDR3 Type Detail: Other Speed: Unknown Manufacturer: Serial Number: Asset Tag: Part Number: Rank: Unknown Handle 0x0023, DMI type 17, 28 bytes Memory Device Array Handle: 0x0015 Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: No Module Installed Form Factor: DIMM Set: None Locator: P1-DIMM3A Bank Locator: BANK6 Type: DDR3 Type Detail: Other Speed: Unknown Manufacturer: Serial Number: Asset Tag: Part Number: Rank: Unknown Handle 0x0025, DMI type 17, 28 bytes Memory Device Array Handle: 0x0015 Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: No Module Installed Form Factor: DIMM Set: None Locator: P1-DIMM3B Bank Locator: BANK7 Type: DDR3 Type Detail: Other Speed: Unknown Manufacturer: Serial Number: Asset Tag: Part Number: Rank: Unknown Handle 0x0027, DMI type 17, 28 bytes Memory Device Array Handle: 0x0015 Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: No Module Installed Form Factor: DIMM Set: None Locator: P1-DIMM3C Bank Locator: BANK8 Type: DDR3 Type Detail: Other Speed: Unknown Manufacturer: Serial Number: Asset Tag: Part Number: Rank: Unknown Handle 0x0029, DMI type 17, 28 bytes Memory Device Array Handle: 0x0015 Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: 8192 MB Form Factor: DIMM Set: None Locator: P2-DIMM1A Bank Locator: BANK9 Type: DDR3 Type Detail: Other Speed: 1066 MHz Manufacturer: Hyundai Serial Number: A37F4026 Asset Tag: Part Number: HMT31GR7BFR4C-H9 Rank: Unknown Handle 0x002B, DMI type 17, 28 bytes Memory Device Array Handle: 0x0015 Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: No Module Installed Form Factor: DIMM Set: None Locator: P2-DIMM1B Bank Locator: BANK10 Type: DDR3 Type Detail: Other Speed: Unknown Manufacturer: Serial Number: Asset Tag: Part Number: Rank: Unknown Handle 0x002D, DMI type 17, 28 bytes Memory Device Array Handle: 0x0015 Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: No Module Installed Form Factor: DIMM Set: None Locator: P2-DIMM1C Bank Locator: BANK11 Type: DDR3 Type Detail: Other Speed: Unknown Manufacturer: Serial Number: Asset Tag: Part Number: Rank: Unknown Handle 0x002F, DMI type 17, 28 bytes Memory Device Array Handle: 0x0015 Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: 8192 MB Form Factor: DIMM Set: None Locator: P2-DIMM2A Bank Locator: BANK12 Type: DDR3 Type Detail: Other Speed: 1066 MHz Manufacturer: Hyundai Serial Number: 16373101 Asset Tag: Part Number: HMT31GR7BFR4C-H9 Rank: Unknown Handle 0x0031, DMI type 17, 28 bytes Memory Device Array Handle: 0x0015 Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: No Module Installed Form Factor: DIMM Set: None Locator: P2-DIMM2B Bank Locator: BANK13 Type: DDR3 Type Detail: Other Speed: Unknown Manufacturer: Serial Number: Asset Tag: Part Number: Rank: Unknown Handle 0x0033, DMI type 17, 28 bytes Memory Device Array Handle: 0x0015 Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: No Module Installed Form Factor: DIMM Set: None Locator: P2-DIMM2C Bank Locator: BANK14 Type: DDR3 Type Detail: Other Speed: Unknown Manufacturer: Serial Number: Asset Tag: Part Number: Rank: Unknown Handle 0x0035, DMI type 17, 28 bytes Memory Device Array Handle: 0x0015 Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: 8192 MB Form Factor: DIMM Set: None Locator: P2-DIMM3A Bank Locator: BANK15 Type: DDR3 Type Detail: Other Speed: 1066 MHz Manufacturer: Hyundai Serial Number: 3F7F6001 Asset Tag: Part Number: HMT31GR7BFR4C-H9 Rank: Unknown Handle 0x0037, DMI type 17, 28 bytes Memory Device Array Handle: 0x0015 Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: No Module Installed Form Factor: DIMM Set: None Locator: P2-DIMM3B Bank Locator: BANK16 Type: DDR3 Type Detail: Other Speed: Unknown Manufacturer: Serial Number: Asset Tag: Part Number: Rank: Unknown Handle 0x0039, DMI type 17, 28 bytes Memory Device Array Handle: 0x0015 Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: No Module Installed Form Factor: DIMM Set: None Locator: P2-DIMM3C Bank Locator: BANK17 Type: DDR3 Type Detail: Other Speed: Unknown Manufacturer: Serial Number: Asset Tag: Part Number: Rank: Unknown

So right now. My system is running perfectly. But it reports 40gb of RAM. Is there a tool that will tell me which slots the ram is in? Whichever one is not present should be the bad stick or slot, no? I just need something to tell me what slots my system thinks are currently in use. Sent from my SM-N920V using Tapatalk

I have 48gb of RAM. There is a bad 8gb stick in there somewhere. Most of the time my system shows 40gb on boot and all is well. Occasionally the system shows 48gb and the system is slow as molasses. How do I identify the bad ram? Sent from my SM-N920V using Tapatalk

Most people view on phones and OTT boxes like Roku and AppleTV. For these, Plex is perfect. Sent from my SM-N920V using Tapatalk

Plex Sent from my SM-N920V using Tapatalk

I have one too. No problems. Sent from my SM-N920V using Tapatalk

Thanks Gary. I will do exactly that. Sent from my SM-N920V using Tapatalk

Ok. I did a cold boot and a new config. I put the suspect drive back and I am rebuilding parity. When it is done and I want to replace disk 8 again. is there any specific requirement? I already ran preclear on the replacement disk. do I need to do it again since it was in the array for 24 hours? Just trying to figure out the safest way to replace disk 8 once parity is back up and running.

Something is definitely not right. Its slowed down to 5 MB/sec. Can anyone tell me what will happen if I stop the rebuild and swap disk 8 with the suspect drive? I could then let it rebuild properly then swap the drives properly (without formatting). Before the starting the array again I will do a full shut down and hopefully fix whatever is slowing everything down at the moment. I am hoping to get access to the 6.5tb of files I have on the suspect drive while I do all of this.