tamalero

Members
  • Posts

    14
  • Joined

  • Last visited

tamalero's Achievements

Noob

Noob (1/14)

1

Reputation

  1. I have run the command to locate the MCE_AMD file and its present. What needs to be done so I still do not get the error? If I have the AMD one present, why I am still seeing the error? @trurl: Were you able to check the logs?
  2. Here you go. cesnas-diagnostics-20220804-0415.zip And you were right, I see now the MCELOG error in the other diagnostics tab. Jul 30 17:18:28 CesNAS kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220) Jul 30 17:18:28 CesNAS kernel: floppy0: no floppy controllers found Jul 30 17:18:28 CesNAS kernel: ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B08 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B0F (\GSA1.SMBI) (20210730/utaddress-204) Jul 30 17:18:29 CesNAS mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead.
  3. Having this same issue as well. Now my Server refuses to fully shutdown. It hangs with a Kernel panic when shutting down/rebooting. Otherwise works correctly as long I do not shutdown/reboot. system: AMD Threadripper 3970X (24 core 48 thread) on an Gigabyte Aorus Pro WIFI TRX40. Any recommendation? And no, its not a MCELOG error.
  4. I'm having the exact same issue. I came from the older 6.8 branch. Updated to 6.9.2 thinking it might be safer to upgrade after the consistent errors of 6.9.0 and 6.9.1.. And I got the exact same error with the same codes Any recommendation to recover?
  5. Aaand done! Finally the cables and the new SAS card have been installed and seems to be working. This issue has been resolved.
  6. I only was getting these errors during WRITE operations, I was using that as parity drive. Hence when heavy usage, aka parity check = errors. Not a single error with parity with the Toshiba N300 I'm using right now. With the WD RED, it was consistent, every.. single.. time parity was at least 10%, it would hit the error from the screenshots. In the other hand, I think there seems to be a confusion here. I have NO ISSUE with the N300. The N300 is NOT a shingled drive as far I know. The WD NAS RED was. The issue was the WD NAS RED, not the Toshiba N300.
  7. Its been almost a month, no errors in the array with the N300 of Toshiba. Avoid WD RED with shingled recording tech. I'm still waiting for the cables as I had to cancel the first order that didn't ship in 15 days.
  8. UPDATE: Finally got my replacement drive. a N300 from Toshiba. And guess what.. NO ERROR during array rebuilding. The SHINGLED Western Digital drive was the problem Anyway, I got my SAS card, waiting for the cables to arrive.
  9. Card is still not here. but interestingly.. since I turned off the Parity check.. The UNRAID has not given ANY error of ANY kind for 4 days now. Even when doing read checks. No SMART errors or UDMA errors either.
  10. Wow, thats.. so confusing. As for ebay seller.. The guy had a good ratio of good vs bad. Very few defective and/or bad stuff. Still... He seems to sell way too many things and very varied stuff... Thanks for the reply btw! Its fascinating how much stuff you can learn from just browsing a forums and test up a small server.
  11. Well I'm having second thoughts.. I asked the vendor since it claimed to be a 9205 but with PCIE 3. Now we know there are some revisions that have a newer batch with the new PCIE3. But this guy claims it IS a 9205 with the 9207 BIOS IT mode. So I'm scratching my head. If this thing doesn't work.. I suppose I will just ask for a refund. As for videocard. Let's say that I want to make it 100% sure this thing(the server) works before removing the video card. Which.. well.. you need the video card to configure the bios..etc.. And thank you so much for your patience in answering me.
  12. Strangely it only shows featured items and some chassis. Cannot see the full list of cards. I bought this one https://www.ebay.com/itm/HP-H220-6Gbs-SAS-PCI-E-3-0-HBA-LSI-9205-8i-P20-IT-Mode-For-ZFS-FreeNAS-unRAID-US/143333684908 as I'm not in the USA (but still in NA) and the import/export company I use does not let me buy the theartofserver's one. I also had to buy a new video card to use the PCIX1 slot instead of a x16 to allow the LSI card fit. So many issues for so many little things phew.. *edit* I'm now worried that I might get a lemon. That seller made an account to act like it was american but its a Hong Kong dude and seems a few products have been defective. I hope I do not have any problem.
  13. Thanks brother, will check on this. (*edit* I cannot buy from your link, the controllers are invisible if I try to buy and they do not ship to my country) Do these work too? https://www.ebay.com/itm/HP-H220-6Gbs-SAS-PCI-E-3-0-HBA-LSI-9205-8i-P20-IT-Mode-For-ZFS-FreeNAS-unRAID-US/143333684908 Yeah, I always used the motherboard SATA ports until I had this issue. My Rocket card never had an issue in Windows. And I knew these ASMEDIA cards with 4 ports were too cheap to be real lol ( I got both of them for 5 USD and 10 USD respectively) Will check the LSI ones.
  14. FULL HARDWARE SPECS: UNRAID Version: 6.8.3 AMD Ryzen 3600 (Box with default heatsink fan, never gets above 55C) Asus B450 Plus PRIME Corsair DDR 4 2x16GB 3600Mhz Ryzen tested RAM. Basic ATI PCIE Card 1 x ASMEDIA 160 x4 SATA PCIE x1 card 1 x ROCKET (Marvel Based) x 2 SATA PCIEx1 Card (Removed, replaced with another ASMEDIA 160x4 SATA PCIE x1 Card. Same issue) 1 x SolarFlare SFN6122F SFP+ with DAC to 10Gbe Switch 2 x Seagate NAS 4TB drive 1 x Seagate NAS 3TB drive 3 x Seagate Greeen 4TB Drives 1 x WDC NAS RED Drive PARITY: 1 x WDC NAS RED PRO 6TB Drive CACHE: 1x Kingston 500GB NVME FLASH: Cheap old DT-101-G2 8GB (moving soon to a faster newer one) ALL HARD DISKS REPORT GREEN via SMART. "Fix Common Problems" finds no issues other than the Parity Drive not enabled. The Background: I bought a B-450 Plus motherboard With an AMD 3600, 32GB DDR4 3600 and 9 HDDs (including one NVME as cache). AsMEDIA x4 SATA controller (I had A ROCKET MARVEL x2 card and did the same issue) Before this I had another system who had zero issues with UNRAID and before that a Windows Server installation. Now the issues: UNRAID at random times will SPASM on different ways. Like.. I just wake up, boot my Win10 machine on my theadripper workstation and then notice that my NAS mounted directories are not visible. OR they are visible, but the services do not work ( PiHole, Torrent service, Emby and a WinServer2019 print server) Note that this happen consistently once PER WEEK. IT seems it HATES doing the parity check. When its not doing parity check everything works fine. (I'm suspecting that NAS shingled WD drive is utter crap) Anyway.. When entering the Unraid Interface.. sometimes two things happen The Unraid Interface is frozen solid and cannot be entered or the page will time out. (can still be pinged) The Unraid interface will load with all services down. Just to tell me that 4 or more hard disks have read errors, others will have UDMA errors, and the Parity did not check properly. When turning off the Array, it will SOMETIMES work properly and will unmount the array. If I have bad luck, it will get stuck. All cores will go to 100%, the GUI will froze later on and the array will NOT UNMOUNTED CORRECTLY. Forcing me to use a hard reboot. Note that the statistics start to spew BS data, like how the hell a drive that just booted up now has 24+ trillion reads and writes? I'm not expert in UNRAID, I just had bought the license recently and I never imagined this much trouble. Could my motherboard be defective (its brand new)?. What baffles me is... this error happens even with the default SATA ports of the motherboard as well (combined with any of the other SATA Cards). I already changed all the SATA cables a few times with brand new ones, and nope same issue. I do not think my SATA Hot Swap cages are the issue either. As I transferred tons of data back and fort with no errors. The error happens almost always when doing parity and only parity alone. Could be a driver issue? motherboard failing? could be overheating? (there is a 10GbE SFP+card that gets quite hot, its in a 4 U server with 8 fans). I even added an extra 120mm fans blowing at the 10Gbe Card and the SATA cards. *edit* Here is my best to write down the console's (physical from my vid card) before full freeze: NAS XFS metadata 1/o Error, in "xlog_oiodone_ at daddr 0xe8e84080len 64 error 5. XFS Md3 Log/io Error Detected. Shutting down filesystem. XFS MD3 Please umount the filesystem and rectify the problem. PHP-FPM Warning Pool www server reached max c_children setting (50) consider raising it) Most of the time the console will show nothing but the login and ip. *edit 2* Decided to destroy the data completely fro the 6TB Parity drive, re-formated remounted and its now building the parity. Well see if it throws error again.. so far ZERO errors in reading and the stats are correct. *edit 3* Error again. After mere 5-10%. The parity stops, the GUI slowly starts to freeze, Cores of the processor suddenly gets pegged to 100%. Cannot mount or unmount anymore nor do anything. Infact if I unmount it will freeze the entire GUI and I have to hard reboot. The log file also goes to 100%. (this is when I start to get ridiculous errors, write and reads stats that make no sense) Attaching diagnostics file. cesnas-diagnostics-20200614-2204.zip