quincyg

Thanks for all of the help! This build seems to be working well, using less power and handling all of my tasks way faster. My SMB load times went from 10 minutes to load a large directory to more like 2 minutes. Boot time on the server went from 5+ minutes to 30 seconds or so. I ended up buying this psu instead: https://www.amazon.com/dp/B0CCZW1X9Q?psc=1&ref=ppx_yo2ov_dt_b_product_details

Yeah. I guess the issue is how many watts per device once you start using a splitter.

I'm ordering parts. I see that my power supply only has 5 sata connectors. How will I get power for my other 3 sata hard drive with the motherboard? Also the photos of the motherboard just show an rj45 port on the back plate, but the description says 2.5Gb ethernet. Which is correct? Thank you all for your help!! Super appreciate it. psu https://pcpartpicker.com/product/t8c48d/be-quiet-pure-power-11-400-w-80-gold-certified-atx-power-supply-bn292 board https://www.newegg.com/p/N82E16813162031?Item=N82E16813162031

I haven't looked at my power usage settings in years. I don't remember adjusting anything except for spin down delay for disks. I also ended up turning off my ups and will only turn it on when we have projecting power outages in my area. I briefly read up on powertop, but didn't see a way to install it within unraid and didn't want to mess around with my unraid setup stability. Can someone explain how a new psu+mb will conserve power vs an old one? Thanks!

Ok, so I guess that's going to be my build, unless I hear any objections!

Well there's this one at 400W it apparently but it lacks an additional connector. Not sure if that would be needed. be quiet! Pure Power 11 400 W 80+ Gold Certified ATX Power Supply https://pcpartpicker.com/product/t8c48d/be-quiet-pure-power-11-400-w-80-gold-certified-atx-power-supply-bn292 Note: The ASRock Z690 PG Riptide ATX LGA1700 Motherboard has an additional 4-pin ATX power connector but the be quiet! Pure Power 11 400 W 80+ Gold Certified ATX Power Supply does not have any available. This connector is used to supply additional current. While the system will likely still run without it, higher current demands or extreme overclocking may require it.

I'll look into it. I figured the old one was working fine and seems overpowered at 650w. If I go for a new psu I won't of going smaller will save energy?

I guess I'll swap for the recommended cpu instead: intel Core i3-12100 3.3 GHz Quad-Core Processor https://pcpartpicker.com/product/qrhFf7/intel-core-i3-12100-33-ghz-quad-core-processor-bx8071512100 It looks like it comes with a stock cooler. Is that sufficient usually. My case has 7 drives @ 30 degrees and a 650W psu. Computer is in an 80 degrees laundry room. Thanks again for the help everyone! Really appreciated.

htop shows top line cpu fluctuating at roughly 50-98% when running a synchronized backup on one mounted share. Primarily it is simply reading the files on the server at this point. When I look down the headings below it shows root cpu fluctuating between 7-40%. Red D's are pooping up in the SHR S column. Then dashboard cpu shows a steady 99-100% cpu.

I saw that warning. Is a bios update tricky for that board.? Assuming i download an image to a thumb drive and run the update from bios settings. Not sure if that can be done without installing a CPU first. Seems like a bios update would help with any other compatibility issues.

I'll check that out. I think my current CPU benchmark is around 500 and is single core. 4gb RAM. I would be surprised if it's choking up.

My unraid server is 10 yrs old and cpu is maxing out whenever I transfer files. Looking to build a basic server with good smb transfer rates. I currently have 6 hard drives. No VMs or dockers running. Just movie playback over home network and data backup. I will use my existing full atx case and 650w power supply. I don't really know what to look for, but after reading a bit I put this list together: Intel Core i3-13100 3.4 GHz Quad-Core Processor https://pcpartpicker.com/product/RdjBD3/intel-core-i3-13100-34-ghz-quad-core-processor-bx8071513100 Thermalright Peerless Assassin 120 SE 66.17 CFM CPU Cooler https://pcpartpicker.com/product/hYxRsY/thermalright-peerless-assassin-120-se-6617-cfm-cpu-cooler-pa120-se-d3 ASRock Z690 PG Riptide ATX LGA1700 Motherboard https://pcpartpicker.com/product/kYwypg/asrock-z690-pg-riptide-atx-lga1700-motherboard-z690-pg-riptide Crucial CT2K16G4DFRA32A 32 GB (2 x 16 GB) DDR4-3200 CL22 Memory https://pcpartpicker.com/product/P3TzK8/crucial-32-gb-2-x-16-gb-ddr4-3200-cl22-memory-ct2k16g4dfra32a Looks like this system will be 5-6x faster than my current, has 8 sata ports, and a 2.5gb ethernet. Does anyone see any issues with this or suggestions? I'm trying to keep the budget low. Would be nice to keep my power consumption low as well. Thanks in advance for any help!

I'm unable to keep an smb connection alive with smb shares. I have tried various settings. Current set to export-yes, security-private, users have rw access. The shares mount and stay active for a few hours and then they are disconnected. I am also experiences similar issue with high sierra. That computer seems to stay active for days then randomly disconnects the share. For the last 6 months I have been using Afp on the high sierra computer and that keeps it's connection alive, but also seems to share the connection with any computer on my network. Also afp rw is at least twice as fast as smb for me. I understand that afp has been removed by unraid, so I'm not going to be able to upgrade unraid until I figure out how to get smb working. I did some searching here, but don't see a solution. Any advice on how to keep smb alive. Thanks for any insight.

Preclear post read failed. Any suggestions here. I got a failure at the end of pre clear. This drive is connected via an onboard sata connector that I don't normally utilize. The WD red drive is running pretty hot as well 47-50C. log attached. preclear_disk_log.txt Jul 31 09:43:51 preclear_disk_VDHX6KUK_30153: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --notify 3 --frequency 1 --cycles 1 --no-prompt /dev/sdb Jul 31 09:43:51 preclear_disk_VDHX6KUK_30153: Preclear Disk Version: 1.0.16 Jul 31 09:43:52 preclear_disk_VDHX6KUK_30153: S.M.A.R.T. info type: default Jul 31 09:43:52 preclear_disk_VDHX6KUK_30153: S.M.A.R.T. attrs type: default Jul 31 09:43:52 preclear_disk_VDHX6KUK_30153: Disk size: 8001563222016 Jul 31 09:43:52 preclear_disk_VDHX6KUK_30153: Disk blocks: 1953506646 Jul 31 09:43:52 preclear_disk_VDHX6KUK_30153: Blocks (512 bytes): 15628053168 Jul 31 09:43:52 preclear_disk_VDHX6KUK_30153: Block size: 4096 Jul 31 09:43:52 preclear_disk_VDHX6KUK_30153: Start sector: 0 Jul 31 09:43:57 preclear_disk_VDHX6KUK_30153: Pre-Read: dd if=/dev/sdb of=/dev/null bs=2097152 skip=0 count=8001563222016 conv=notrunc,noerror iflag=nocache,count_bytes,skip_bytes Jul 31 10:53:15 preclear_disk_VDHX6KUK_30153: Pre-Read: progress - 10% read @ 188 MB/s Jul 31 12:03:47 preclear_disk_VDHX6KUK_30153: Pre-Read: progress - 20% read @ 181 MB/s Jul 31 13:16:54 preclear_disk_VDHX6KUK_30153: Pre-Read: progress - 30% read @ 174 MB/s Jul 31 14:33:20 preclear_disk_VDHX6KUK_30153: Pre-Read: progress - 40% read @ 167 MB/s Jul 31 15:53:54 preclear_disk_VDHX6KUK_30153: Pre-Read: progress - 50% read @ 161 MB/s Jul 31 17:19:43 preclear_disk_VDHX6KUK_30153: Pre-Read: progress - 60% read @ 146 MB/s Jul 31 18:52:27 preclear_disk_VDHX6KUK_30153: Pre-Read: progress - 70% read @ 138 MB/s Jul 31 20:34:15 preclear_disk_VDHX6KUK_30153: Pre-Read: progress - 80% read @ 121 MB/s Jul 31 22:29:41 preclear_disk_VDHX6KUK_30153: Pre-Read: progress - 90% read @ 104 MB/s Aug 01 00:45:46 preclear_disk_VDHX6KUK_30153: Pre-Read: dd - read 8001565319168 of 8001563222016. Aug 01 00:45:47 preclear_disk_VDHX6KUK_30153: Pre-Read: elapsed time - 15:01:47 Aug 01 00:45:47 preclear_disk_VDHX6KUK_30153: Pre-Read: dd exit code - 0 Aug 01 00:45:51 preclear_disk_VDHX6KUK_30153: Zeroing: emptying the MBR. Aug 01 00:45:51 preclear_disk_VDHX6KUK_30153: Zeroing: dd if=/dev/zero of=/dev/sdb bs=2097152 seek=2097152 count=8001561124864 conv=notrunc iflag=count_bytes,nocache,fullblock oflag=seek_bytes Aug 01 00:45:51 preclear_disk_VDHX6KUK_30153: Zeroing: dd pid [3609] Aug 01 02:49:23 preclear_disk_VDHX6KUK_30153: Zeroing: progress - 10% zeroed @ 111 MB/s Aug 01 04:35:33 preclear_disk_VDHX6KUK_30153: Zeroing: progress - 20% zeroed @ 146 MB/s Aug 01 06:13:56 preclear_disk_VDHX6KUK_30153: Zeroing: progress - 30% zeroed @ 127 MB/s Aug 01 07:57:00 preclear_disk_VDHX6KUK_30153: Zeroing: progress - 40% zeroed @ 113 MB/s Aug 01 09:56:06 preclear_disk_VDHX6KUK_30153: Zeroing: progress - 50% zeroed @ 110 MB/s Aug 01 11:51:07 preclear_disk_VDHX6KUK_30153: Zeroing: progress - 60% zeroed @ 117 MB/s Aug 01 13:41:27 preclear_disk_VDHX6KUK_30153: Zeroing: progress - 70% zeroed @ 130 MB/s Aug 01 15:19:57 preclear_disk_VDHX6KUK_30153: Zeroing: progress - 80% zeroed @ 136 MB/s Aug 01 17:07:26 preclear_disk_VDHX6KUK_30153: Zeroing: progress - 90% zeroed @ 113 MB/s Aug 01 19:13:15 preclear_disk_VDHX6KUK_30153: Zeroing: dd - wrote 8001563222016 of 8001563222016. Aug 01 19:13:16 preclear_disk_VDHX6KUK_30153: Zeroing: elapsed time - 18:27:23 Aug 01 19:13:17 preclear_disk_VDHX6KUK_30153: Zeroing: dd exit code - 0 Aug 01 19:13:18 preclear_disk_VDHX6KUK_30153: Writing signature: 0 0 2 0 0 255 255 255 1 0 0 0 255 255 255 255 Aug 01 19:13:22 preclear_disk_VDHX6KUK_30153: Post-Read: verifying the beggining of the disk. Aug 01 19:13:22 preclear_disk_VDHX6KUK_30153: Post-Read: cmp /tmp/.preclear/sdb/fifo /dev/zero Aug 01 19:13:22 preclear_disk_VDHX6KUK_30153: Post-Read: dd if=/dev/sdb of=/tmp/.preclear/sdb/fifo count=2096640 skip=512 conv=notrunc iflag=nocache,count_bytes,skip_bytes Aug 01 19:13:23 preclear_disk_VDHX6KUK_30153: Post-Read: verifying the rest of the disk. Aug 01 19:13:23 preclear_disk_VDHX6KUK_30153: Post-Read: cmp /tmp/.preclear/sdb/fifo /dev/zero Aug 01 19:13:23 preclear_disk_VDHX6KUK_30153: Post-Read: dd if=/dev/sdb of=/tmp/.preclear/sdb/fifo bs=2097152 skip=2097152 count=8001561124864 conv=notrunc iflag=nocache,count_bytes,skip_bytes Aug 01 20:34:20 preclear_disk_VDHX6KUK_30153: Post-Read: progress - 10% verified @ 169 MB/s Aug 01 21:46:45 preclear_disk_VDHX6KUK_30153: Post-Read: dd - read 1527356166144 of 8001563222016. Aug 01 21:46:45 preclear_disk_VDHX6KUK_30153: Post-Read: elapsed time - 2:33:21 Aug 01 21:46:45 preclear_disk_VDHX6KUK_30153: Post-Read: dd command failed, exit code [1]. Aug 01 21:46:45 preclear_disk_VDHX6KUK_30153: Post-Read: dd output: 1518178664448 bytes (1.5 TB, 1.4 TiB) copied, 9128.02 s, 166 MB/s Aug 01 21:46:45 preclear_disk_VDHX6KUK_30153: Post-Read: dd output: 725089+0 records in Aug 01 21:46:45 preclear_disk_VDHX6KUK_30153: Post-Read: dd output: 725088+0 records out Aug 01 21:46:45 preclear_disk_VDHX6KUK_30153: Post-Read: dd output: 1520619749376 bytes (1.5 TB, 1.4 TiB) copied, 9142.07 s, 166 MB/s Aug 01 21:46:45 preclear_disk_VDHX6KUK_30153: Post-Read: dd output: 726061+0 records in Aug 01 21:46:45 preclear_disk_VDHX6KUK_30153: Post-Read: dd output: 726060+0 records out Aug 01 21:46:45 preclear_disk_VDHX6KUK_30153: Post-Read: dd output: 1522658181120 bytes (1.5 TB, 1.4 TiB) copied, 9154.33 s, 166 MB/s Aug 01 21:46:45 preclear_disk_VDHX6KUK_30153: Post-Read: dd output: 727177+0 records in Aug 01 21:46:45 preclear_disk_VDHX6KUK_30153: Post-Read: dd output: 727176+0 records out Aug 01 21:46:45 preclear_disk_VDHX6KUK_30153: Post-Read: dd output: 1524998602752 bytes (1.5 TB, 1.4 TiB) copied, 9168.43 s, 166 MB/s Aug 01 21:46:45 preclear_disk_VDHX6KUK_30153: Post-Read: dd output: 728256+0 records in Aug 01 21:46:45 preclear_disk_VDHX6KUK_30153: Post-Read: dd output: 728255+0 records out Aug 01 21:46:45 preclear_disk_VDHX6KUK_30153: Post-Read: dd output: 1527261429760 bytes (1.5 TB, 1.4 TiB) copied, 9182.28 s, 166 MB/s Aug 01 21:46:45 preclear_disk_VDHX6KUK_30153: Post-Read: dd output: dd: error reading '/dev/sdb': Input/output error Aug 01 21:46:45 preclear_disk_VDHX6KUK_30153: Post-Read: dd output: 728299+1 records in Aug 01 21:46:45 preclear_disk_VDHX6KUK_30153: Post-Read: dd output: 728299+1 records out Aug 01 21:46:46 preclear_disk_VDHX6KUK_30153: Post-Read: dd output: 1527354068992 bytes (1.5 TB, 1.4 TiB) copied, 9198.16 s, 166 MB/s Aug 01 21:46:46 preclear_disk_VDHX6KUK_30153: Post-Read: dd output: 728299+1 records in Aug 01 21:46:46 preclear_disk_VDHX6KUK_30153: Post-Read: dd output: 728299+1 records out Aug 01 21:46:46 preclear_disk_VDHX6KUK_30153: Post-Read: dd output: 1527354068992 bytes (1.5 TB, 1.4 TiB) copied, 9198.16 s, 166 MB/s Aug 01 21:46:48 preclear_disk_VDHX6KUK_30153: ssmtp: Authorization failed (535 5.7.0 (#AUTH005) Too many bad auth attempts.) Aug 01 21:46:49 preclear_disk_VDHX6KUK_30153: S.M.A.R.T.: 5 Reallocated_Sector_Ct 6 Aug 01 21:46:49 preclear_disk_VDHX6KUK_30153: S.M.A.R.T.: 9 Power_On_Hours 77 Aug 01 21:46:49 preclear_disk_VDHX6KUK_30153: S.M.A.R.T.: 194 Temperature_Celsius 50 Aug 01 21:46:49 preclear_disk_VDHX6KUK_30153: S.M.A.R.T.: 196 Reallocated_Event_Count 6 Aug 01 21:46:49 preclear_disk_VDHX6KUK_30153: S.M.A.R.T.: 197 Current_Pending_Sector 16 Aug 01 21:46:49 preclear_disk_VDHX6KUK_30153: S.M.A.R.T.: 198 Offline_Uncorrectable 0 Aug 01 21:46:49 preclear_disk_VDHX6KUK_30153: S.M.A.R.T.: 199 UDMA_CRC_Error_Count 0 Aug 01 21:46:49 preclear_disk_VDHX6KUK_30153: error encountered, exiting...

I thought I had figured out this problem. I ran a parity check in troubleshoot mode and it worked with no errors. I then uninstalled all plugins..(appstore and fix common problems.) For the last 3 weekly parity checks everything was fine. Last night during parity check the system locked up again. No web access and when I try to download the the syslog at the console it gives me a response of " command terminated" I tried reboot command and it starts the process and then freezes. So I have no syslog info and am not sure where to start. This system has been rock solid for years, but seemed to start having issues after upgrading to 6.6.7 and larger disk drive.

I am running an Unraid server that had been functioning without errors for years. A couple months ago I upgraded to 6.6.7 from 5.0.6. Everything was fine and parity checked out with no errors. A couple of days later I upgraded a disk drive and the system froze while running a parity check. Console inaccessible and unable to reboot or shutdown from the head. It tries to force shutdown after a while, but can't. The parity check history shows parity check as complete each time this happens. I'm assuming there must be an issue with the new drive or cable. I'm running a smart test now to see if anything shows up there. If I decide to replace that new drive with another one, what would the process be? I'm concert that If is put a new drive in and it tries to rebuild the array, it might freeze in the process and I would lose my data, end up without parity. Any advice on how to proceed would be appreciated! Thanks!

Awesome plugin, but I am not able to figure out how to enable troubleshoot mode. In the tutorial video there is a troubleshoot button on the right side of the interface. Not seeing a button or link anywhere to troubleshoot. I'm sure I am missing something very simple. Thanks for any help!

Thank you Joe for the quick reply and solid advice! Just upgraded to 4.7 and drives showed up. Running parity check now. Looks like parity check is about twice as fast now with the new card.

I am running unraid 4.5.1 and am trying to upgrade my sata controller to an aoc-saslp-mv8. I can't seem to get unraid to see the drives and hope I am missing something simple. I definitely am using forward cables and am able to enter the sata controller bios. I do see the drives attached within the sata controller bios. I thought it might be a conflict with my video card being on a pci express port with my asus board so I installed a pci video card and set primary video device to pci. I also played around with asus bios settings and disabled anything not needed. The syslog seems to say that the drives are seen, but cannot be attached. Not sure if I am reading this correctly. Syslog is attached. Thanks for any ideas. syslog3_22_12.txt.zip

My old parity drive failed and I replaced it. On my first parity check I had 36 parity errors, 37 on second check and 38 on third. On each parity check, the only writes that occur are on the parity drive. The same number of writes as parity errors:36,37 then 38. I don't see any errors in the syslog(attached). Is it possible that the parity check is incorrectly trying to create parity? Is this a situation where I should do "trust array" to establish a parity baseline? unraid 4.5.1. syslog attached. syslog_3_10_12.txt.zip

I am running unraid 4.3 and had a parity drive that showed thousands of errors. I replaced the drive and then started getting bios beeps at startup indicating a failed video card. I replaced the video card and assigned the new parity drive, but I am getting a check rate of 2190 KB/sec. At this rate it will take a little over 7 days to run a parity check. Some of the drives are on a sata 1 bus. Previous parity checks took around a day and a half. Is this normal for a first parity check on a new drive to take this long? I do see some errors in the syslog, but don't know if they are significant. syslog3_7_12.txt.zip

That sounds like it would really help out with the troubleshooting process

Are you sure that you are mapping it as a network drive? There should be a checkbox for reconnect at login and the drive should be showing up with a letter name if mapped. Another thing that will automatically connect you to unraid is if you create a user in xp with the same username and password that you have set in unraid. That may be the easiest solution.

I actually planned on buying the 12 bay package originally, but the website has been showing it to be sold out for months. In terms of supported hardware list... I think a lot of people would be saved some headache if they are warned about problems with certain gigabit mb's, WD ears drives, etc. before they build their system. I think in terms of my own troubleshooting ability, the problem is in figuring out which drives/ports are experiencing problems. With no evidence in the syslog or smart report, I need another way to find out which drives are getting parity errors. It sounds like writing some data to individual drives and then doing md5 checks could answer that. I have not been able to figure out how to do that from the wiki or forum. Maybe I should start a new thread asking for a md5 check for each drive procedure. All in all, I really think unraid is great...I just need to figure out a way to approach troubleshooting more effectively. So far I have had problems with the usb drive, a bad sata cable and now a bad sata port. I have been planning to build a new unraid to backup my current one, so I guess that will be a good test for me.

I definitely won't not skimp on components in the future. What more can I do? I bought a recommended power supply, hard drives, highest quality sata cables, supported sata card and motherboard. All I can do at this point is pray. Is the goal of Lime-tech to appeal to non-I.T. consumers? If so, I think the main weakness is the lack of u.i. for troubleshooting. It would be very attractive to the lay person if there was an interface that gave you options such as: 1)Test memory and give results(run memtest) 2)Test drive health(smart tests) 3)Check that data is being written correctly to each drive(MD5 check...I think) It would also be helpful to create a more streamlined list of "Supported Hardware" This should be located on the lime-tech/support/unraid server installation, not buried. And for that matter a troubleshooting flow chart would be great.