• Posts

  • Joined

  • Last visited


  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

bcbgboy13's Achievements


Enthusiast (6/14)



  1. I am not sure where are you located - but it is best to retire the old AMD platform and replace it with an Intel one (even if old). Check Ebay, your local Kijiji or Craigslist boards - there are a lot of people selling used server grade hardware where you could probably find an used Supermicro MB, XEON CPU(s) and 4-8GB ECC memory for $100 or so. Check it out to see if it is stable - run memtest for a day, even install some old windows and run some of the software for stress test and if stable then upgrade. This is the one thing that will speed up you parity test or rebuilds and even leave some horsepower for other stuff that you are not presently using but may consider doing in the future. Reason for that - the newer Unraids are using newer Linux kernels, which are using newer instruction sets (AVX2) which are not available in these older AMD CPUs - Semprons, Athlons x2, x4 or Phenoms. If you keep your present system even with a new CPU (raw CPU speed is better than more cores) you will have a very long parity checks, especially if you update to the dual parity. There is no way around that.... https://en.wikipedia.org/wiki/Advanced_Vector_Extensions I personally loved these old AMD CPUs for basic Unraid functionality. The AMD CPUs were always ECC capable and ECC and a UPS is a must for me. Some of the motherboard manufacturers at the time (Asus, Biostar, ) actually routed all 72 tracks to the RAM slots and kept (or did not disable) the ECC functionality in the BIOS - so by using the slightly more expensive unbuffered ECC memory one could end with an energy-efficient "server-grade" system at very low cost compared to the price of the Intel Xeon stuff. However I started out with a dual core 4850e (45W TDP), once I migrated to 6.6.6 I upgraded it to a 4-core 610e (still 45W TDP) but it was still not powerful enough. Doing a parity check I was afraid to use anything else, even preclearing a new HD on the side as it was maxed out. But for basic Unraid functionality they were OK. If you decide to stay with the current system and just change the CPU - raw CPU speed is better for the parity speed than the number of cores.
  2. Your MB uses the earlier "F1" BIOS dated 11/25/2016 You should update to the latest one and try the controller again.
  3. I am not sure if you can mix SATA and SAS drives on the same breakout cable. They use a different signaling scheme, which also allows for much longer cables for the SAS drives. I believe that if you mix them on the same cable this will force the controller to use the SATA signaling and this may not be liked by the SAS drives The cable you are using is already 1m long anyway which is the max for a SATA cable. It is better to use a shorter regular SATA cable attached to one of the MB ports for the SATA drive and keep the SAS drives separate.
  4. You can have you wish here via user script from here:
  5. Most of your disks are also old and you are running them at very high temperature - above 50 and even 55 degC (and even higher in previous power cycles). Keep this in mind.
  6. Updating the BIOS should be your first resort. In fact every few weeks you should go to your board manufacturer site and check for new updates and pry to the computer gods that they keep releasing new updates.... Just RTFM first and then follow the procedures strictly - and make sure that if there is a jumper or switch to enable / disable the flashing you use it and then you disable it back, as the UEFI chip can be a desirable home for very nasty computer viruses/rootkits.
  7. Seagate has chosen to report some of the SMART attributes in a different way compared to the other HD manufacturers. In addition they report some attributes (with id# above 200) that no other manufacturer will report. So it is not direct apples to apples comparison and the RAW values that look crazy may and in your case are just normal. But if I was in your shoes I will also look at the max temperature a hard drive has run - it is usually way down in the SMART report. And in your case you have 5 HDs that were run at very high temperature at same time in the past - perhaps they shared 5in3 enclosure with a bad fan or a loose cable connection to the fan.... So here they are: sdq - 66 degC - ~69kh sdn - 65 - ~70.5kh sdc - 64 - ~59kh sdg - 59 - ~55.5kh sdk - 58 - ~50.5kh And when you replace a 2 or 3TB hard drive with 8TB one you will have spare 5-6 TB left - you can simply copy the content of 2 or 3 of these small aged drives, then zero them out and remove them from the array and you will end with more empty slots in your case (and perhaps save a tiny bit of electricity)
  8. Another thing to keep in mind is quality of the power grid where you live. If you live in an area with dirty power you may experience a multiple power glitches - they could be very short in duration so you cannot observe them in any way, but may cause a memory corruption here and there - and since Unraid runs from the memory you will end up with unexpected problems as the time passes by. Adding a UPS (even a small one) usually will fix that!
  9. Can you try inserting the flash drive at one of the USB ports at the back panel - sometimes weird things do happen
  10. I do not know if there is a Windows application to read the content of a XFS formatted drive, but you can simply download one of the many "live" Linux distros, bur it on a CD or USB drive, boot your windows computer from it, it will see the XFS partition and then you can copy the data to some place, even to your NTFS formatted disks if you have enough space there.... Your BIOS is 1.80, there is 1.90 which "improves the system performance"???? And regarding the high temperatures I am talking about your mechanical hard drives: For example - the 4TB Seagate (sdb) has the following: SCT Status Version: 3 SCT Version (vendor specific): 522 (0x020a) Device State: Active (0) Current Temperature: 24 Celsius Power Cycle Min/Max Temperature: 17/25 Celsius Lifetime Min/Max Temperature: 16/66 Celsius Seagate own specs calls for (just below in the SMART report) SCT Temperature History Version: 2 Temperature Sampling Period: 3 minutes Temperature Logging Interval: 59 minutes Min/Max recommended Temperature: 14/55 Celsius Min/Max Temperature Limit: 10/60 Celsius Temperature History Size (Index): 128 (50) The same with the other Seagate and three of the Toshibas (which BTW have 55 degC recommended/max temperature) For example the "new" disk Toshiba (sde - from your latest log) has Current Temperature: 28 Celsius Power Cycle Min/Max Temperature: 15/29 Celsius Lifetime Min/Max Temperature: 13/65 Celsius Under/Over Temperature Limit Count: 0/2348 Toshiba sampling/logging is 1 min and you have 2348 counts of over-temperature - this is at least 39 hours+ running at very high temperature in the past. Perhaps you had a bad fan or a disconnected cable for the fan....
  11. 2 things from me 1. There is a new BIOS (and a new BMC), released in 2018. 2. Some of your HDs have been subject to e very high temperatures in the past (above 60 degC and up to 66 degC ) - sdh, sdg, sde, sdb, sdc I am not sure when and how it happened ...
  12. OK then it is SOLVED. For a day I was young again remembering the glory days of manipulating manually the MBR, partitions, wiping the nasty viruses hiding in these unused 32kB...
  13. Perhaps you have "gremlins" in your hard disk which are manifesting now as we move to a newer kernels.... especially since you have this in your SMART report: ==> WARNING: A firmware update for this drive is available, see the following Seagate web pages: http://knowledge.seagate.com/articles/en_US/FAQ/207931en http://knowledge.seagate.com/articles/en_US/FAQ/223651en Plus this one: APM level is: 128 (minimum power consumption without standby) I still have a similar disk (mine is 3TB) with a very odd behavior - you can preclear that damn thing as many time as you wish and it will pass with nothing wrong in the SMART report but once added to the array and server reboots it gets kicked out as disabled. And I tried it recently with 6.6.6. - still the same!!! Here are the specs from Seagate: https://www.seagate.com/files/www-content/product-content/barracuda-fam/desktop-hdd/barracuda-7200-14/en-us/docs/100686584y.pdf
  14. Success!!!! After executing the command above with the proper disks "names": login as: root root@unraid's password: Linux 4.18.20-unRAID. root@unraid:~# dd if=/dev/zero of=/dev/sdi bs=1024 count=1 1+0 records in 1+0 records out 1024 bytes (1.0 kB, 1.0 KiB) copied, 0.000354388 s, 2.9 MB/s root@unraid:~# dd if=/dev/zero of=/dev/sdf bs=1024 count=1 1+0 records in 1+0 records out 1024 bytes (1.0 kB, 1.0 KiB) copied, 0.000304993 s, 3.4 MB/s root@unraid:~# dd if=/dev/zero of=/dev/sdc bs=1024 count=1 1+0 records in 1+0 records out 1024 bytes (1.0 kB, 1.0 KiB) copied, 0.000367164 s, 2.8 MB/s root@unraid:~# dd if=/dev/sdh of=/dev/sdi bs=512 count=1 1+0 records in 1+0 records out 512 bytes copied, 0.000388192 s, 1.3 MB/s root@unraid:~# dd if=/dev/sdh of=/dev/sdf bs=512 count=1 1+0 records in 1+0 records out 512 bytes copied, 0.000109879 s, 4.7 MB/s root@unraid:~# dd if=/dev/sdh of=/dev/sdc bs=512 count=1 1+0 records in 1+0 records out 512 bytes copied, 0.000107168 s, 4.8 MB/s root@unraid:~# this one was added at the very end of the syslog: Mar 12 10:06:13 unraid kernel: sdi: sdi1 Mar 12 10:07:50 unraid kernel: sdf: sdf1 Mar 12 10:08:43 unraid kernel: sdc: sdc1 After rebooting the server everything seems to be OK. The three disks are mounted with "MBR: 4K-aligned" and parity is valid!!!!! I will do a parity check just to be sure and will mark this "solved" in a day or two - waiting for someone to tell me that it is not a good idea to have four disks with identical volume identifiers...
  15. Hmm, I was thinking more of using these: 1. Zeroing the first two sectors of the 3 unmountable drives: dd if=/dev/zero of=/dev/sdX bs=1024 count=1 2. Copying the first sector (MBR - the partition info) from the good 2 TB hard drive into the first sector of the other 3 drives: dd if=/dev/sdX of=/dev/sdY bs=512 count=1 , where the sdX is the source with good MBR 3. Reboot This should set me with 4 hard drives having the same volume ID (in the Microsoft sense - 4 bytes starting at location 0x1B8), but I am not sure if Linux (Unraid) uses it. If not advisable, then I will have to manually remove the drive, attach it to my Windows computer and manually change one bit of this volume IDs - which will result in three parity errors, but I can live with that - unless there is some HEX utility editor that I can use with Unraid to manually modify a bit I just need need some Linux guru to confirm that the the commands above are good