[Motherboard / CPU advise for media storage server]

5 minutes ago, Teejoo said:

Hi, I also use a IBM ServeRAID M1015 SAS/SATA RAID Controller with 8 ports.

 

In total I have 9 discs installed: 8 WD RED pro's 16TB and a 2TB SSD for cache.

 

Ah, now I see... thanks for the info!

 

[Motherboard / CPU advise for media storage server]

On 3/27/2022 at 11:44 AM, Teejoo said:

I made a decision and ordered these:

 

- Asus PRIME Z590-A

- Intel Core Intel Core i3 10300 boxed

- Corsair DDR4 Vengeance LPX 2x8GB 3600

- 7x WD Red Pro, 16TB (incl 2 parity drives)

- Samsung 870 Evo 2TB (cache)

- Corsair RM550x PSU

 

Looking forward to built it into the Define 7 XL and start to play with unraid!

 

Nice build but I have a question. I checked the specs for the Asus PRIME Z590-A motherboard just now and it seems to only have 6 SATA ports. Just curious how you were able to get 7x WD Reds connected?

 

[Quick way to set share to read-only?]

Also, don't ever map shares to drives.  Most virus / ransomware aren't going to be scanning your network, but are going to be scanning your local drives (of which for all intents and purposes a mapped share appears to be)

 

Locky ransomware does scan for mapped and unmapped network shares and will attempt to encrypt any media files it finds. That's what made me take a close look at our home network environment to see about hardening security there.

 

More info about Locky ransomware here, for anyone who is interested.

 

Somehow, this malware has already infected hundreds of computers in Europe, Russia, the US, Pakistan, and Mali. The malicious script downloads Locky's malware executable file from a Web server and stores it in the "Temp" folder associated with the active user account. Once installed, it starts scanning for attached drives (including networked drives) and encrypts document, music, video, image, archive, database, and Web application-related files. Networked drives don't need to be actively mapped to be found, however.

 

My wife works from home and she's always emailing MS Office and other documents with co-workers. So after the ransomware attack at my workplace I decided to take a closer look at the security settings on our home network as well.

 

Anyways, it sounds like the current method is the best option for setting read-only on my unraid shares. I expected as much but just thought I would check in case there was a faster way to toggle read-only on unraid shares.

 

Thanks for the suggestions....

[Quick way to set share to read-only?]

We had a ransomware attack at the office recently (Locky) and I've learned quite a bit from the experience. The smoke has now cleared and I've had time to assess any potential holes on our home network and I've decided it would be prudent to make our unraid shares read-only to help prevent damage to our precious media files in the event of a future ransomware attack.

 

Currently I am running a stock unraid v6.1.9 install (using Windows7 and Windows8 clients) and was wondering if there's a quick way to toggle the read-write / read-only setting for my unraid shares. The idea is to toggle read-only when there are no file/copy transactions occurring, then toggle read-write whenever I need to copy/move/delete files. I'd like to keep the shares read-only the majority of the time and I will change to read-write only when I need to make changes.

 

Currently, the process I am using requires about 5-steps: Navigate to the main unraid main menu, click shares, click the share name, scroll down and change to read-only, click apply. I was wondering if there is a faster way?

 

Thanks for any advice!

[Preclear.sh results - Questions about your results? Post them here.]

Well I am by no means an expert but there are lots of I/O errors in there and it looks to me like at some point unRAID had to reset the link to the drive because of this.  Here are some of the lines from the report ...

 

Oct 29 02:47:09 Titan kernel: ata5.00: failed command: CHECK POWER MODE
Oct 29 02:47:09 Titan kernel: ata5.00: cmd e5/00:00:00:00:00/00:00:00:00:00/40 tag 0
Oct 29 02:47:09 Titan kernel:          res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
Oct 29 02:47:09 Titan kernel: ata5.00: status: { DRDY }
Oct 29 02:47:09 Titan kernel: ata5: hard resetting link

 

Maybe you have a bad power connection and/or SATA cable.  Check the connections and cables.  I'd recommend switching them with a known good power connector and SATA cable.  Perhaps use ones that are connected to another drive that is working fine now.  Then try the precelar again.

 

I checked the cables just now, even moved it to a different SATA port on the motherboard but unraid still throws errors about this disk when I reboot.

 

I pulled the disk out of the array and put it on my external SATA dock on my Windows 7 machine and tried to check it using CrystalDiskInfo but it didn't even see the disk.  The disk isn't showing up in the BIOS of my Windows PC at boot time either.

 

So all signs point to a bad disk.  Time to start the RMA process with Newegg.

 

Thanks for your help!

 

Seven

[Preclear.sh results - Questions about your results? Post them here.]

Looks like preclear failed on a brand new disk I purchased to keep on hand as a spare drive.  I've attached all of the logfiles and output I could find....  I did not find a smart_finish report in the /tmp directory. 

 

This is a new WD20EARS drive from Newegg and I did install a jumper over pins 7/8 before attaching to my server.

 

Any thoughts or suggestions would be appreciated.  Thanks!

Logs.zip