jakeslominski

Members
  • Posts

    15
  • Joined

  • Last visited

Recent Profile Visitors

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

jakeslominski's Achievements

Noob

Noob (1/14)

1

Reputation

  1. Working on adding two new 18TB drives into my array. One worked perfectly fine and just added right in. Stuck fighting with the second one now. Disk shows up in unassigned devices with a green dot for spun up. Format fails every time and logs attached. Copied out the biggest/most relevant looking chunk: One odd thing that I noticed between the two new 18TB drives (both ironwolf pros purchased at the same time) is that one shows the PN in the drive identifier and other does not. Have reseated and swapped all cables with no change noticeable. "Bad" drive also shows no SMART errors so I am lost at this point. [GOOD DRIVE] ST18000NE000-2YY101_ZR5CJW9B - 18 TB (sdg) [BAD DRIVE] ST18000NE000_ZR5CF3H0 (sdf) h
  2. I want to keep all the data. Not sure if its best to remove and let parity rebuild the missing drives or another way. I dont have backups, but its nothing that I can't get back easily enough. Just some movies and TV. Yes, the old parity and new 18tb will be in slots 3 and 4.
  3. Hello Folks, I have a list of things that I need to do to my server this week before the holidays and I need help knowing what order to do everything in correctly. Attached below is my array devices as well for reference. The list is below in what im assuming might be the correct order: install new Seagate IronWolf Pro 18TB NAS Hard Drive into parity slot move current 8tb parity disk to array remove disk 3 due to errors remove disk 4 for use elsewhere install new other Seagate IronWolf Pro 18TB NAS Hard Drive into array update unraid from 6.10.3 to 6.11.5 I welcome any help, articles, or videos that you can share!
  4. thank you this seems to have worked. wonder how it worked like that for months and decided to stop now.... but im back in action finally!
  5. diagnostic file attached. hope this helps unserv-diagnostics-20220801-1449.zip
  6. Recently had to restart my server that was up for months without issue. After restart, I am unable to access the web GUI at localhost:9080 like I used to be (port number I set). All of my docker services (plex, sonarr, radarr, sabnzbd) are still working just fine and I can access those. Tried booting safe mode with no luck. Also tried booting in gui (firefox automatically opened and tried to open localhost:9080) to no avail. Hoping there is something simple that I am missing here.
  7. Will check on this today and see if it helps out! I let it run for a full 24 hours and didn't come up with any errors so hopefully good on the memory front.
  8. I was hoping it was an issue. Ever since I booted up the server, it crashes every 2-3 hours and I have to hard restart it. Unresponsive from GUI or SSH. Is there anything in my diagnostics otherwise that could explain those crashes?
  9. Ran fix common problems on my server today and got the error Machine Check Events detected on your server: Your server has detected hardware errors. You should install mcelog via the NerdPack plugin, post your diagnostics and ask for assistance on the unRaid forums. The output of mcelog (if installed) has been logged. I think its something about CPU but don't fully understand what I'm looking at. Diagnostics attached and would really appreciate if someone could take a look for me! unserv-diagnostics-20220120-0125.zip
  10. Former unraid user trying to return after a year away. Trying install unraid on a new server and am getting stuck at the very beginning. Followed tutorials from unraid official documentation, spaceinvaderone and juanmtech. Able to flash the USB drive with the latest stable version available (both with the tool and manually) on a windows machine. Move over to the server, check all the correct BIOS settings (tried legacy and uefi boot, virtualization settings, iommu), and get boot the computer from the USB drive. It just gets stuck at a flashing white cursor on a black screen. Can't even get to the blue "normal boot, gui, safe, memtest" screen. Hoping someone can help me out so that I can come back to the fold soon!!
  11. Currently maxing out my tower chassis with 11 drives. Looking for a rackmount chassis to transplant to that wont break the bank. Need the future expandability for more drives. Budget is $300-400. Doesn't need to be new, but needs to be easily stocked because my husband is buying it for me for Christmas and doesn't have the skillset to scour ebay auctions. Wishlist: 4U with 7 full height expansion slots (GPUs and NICs currently full height) Accepts standard ATX motherboard (eatx expandability would be cool too) Accepts standard ATX PSU (just want to transplant my current system and cant afford a new/different form factor psu at the moment) 24-36 drive bays (can be front hotswap or top loaded, not picky on that) backplane (using a mix of sas and sata drives currently (prefer 12g but can work with 6g)
  12. Crucial Ballistix 2666 MHz DDR4 DRAM Desktop Gaming Memory Kit 32GB (16GBx2) CL16 BL2K16G26C16U4B (BLACK) So as far as I can tell, running at 2666 is within spec. Are you referring to how much RAM in terms of GB and if so, what would you recommend for my Ryzen 1700x.
  13. UPDATE: So wasn't able to run memtest last night because I didn't realize it needed BIOS and not UEFI, so that will be run tonight I guess. Left it sitting running a parity check since this server has gone through alot in the last couple days and wanted to be safe. Its at 0 errors for 1.5TB right now so I'm not sure if this is related to parity or something else, but I am seeing alot of BTRFS errors in my log this morning. They came in right after log in and was going to check share sizes just out of curiosity. Logs below because incase it has any more meaning. Looks like the cache drive if I'm not mistaken. May 5 08:28:01 MediaServ webGUI: Successful login user root from 192.168.50.51 May 5 08:30:15 MediaServ emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/share_size appdata ssz1 cache May 5 08:30:21 MediaServ kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=45910523904 parent_transid=218206 key expected=(7314709,12,281474984017009) has=(7314709,12,7306353) May 5 08:30:21 MediaServ kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=45910523904 parent_transid=218206 key expected=(7314709,12,281474984017009) has=(7314709,12,7306353) May 5 08:30:21 MediaServ kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=45910523904 parent_transid=218206 key expected=(7314709,12,281474984017009) has=(7314709,12,7306353) May 5 08:30:21 MediaServ kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=45910523904 parent_transid=218206 key expected=(7314709,12,281474984017009) has=(7314709,12,7306353) May 5 08:30:21 MediaServ kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=45910523904 parent_transid=218206 key expected=(7314709,12,281474984017009) has=(7314709,12,7306353) May 5 08:30:21 MediaServ kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=45910523904 parent_transid=218206 key expected=(7314709,12,281474984017009) has=(7314709,12,7306353) May 5 08:30:21 MediaServ kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=45910523904 parent_transid=218206 key expected=(7314709,12,281474984017009) has=(7314709,12,7306353) May 5 08:30:21 MediaServ kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=45910523904 parent_transid=218206 key expected=(7314709,12,281474984017009) has=(7314709,12,7306353) May 5 08:30:22 MediaServ kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=45910523904 parent_transid=218206 key expected=(7314709,12,281474984017009) has=(7314709,12,7306353) May 5 08:30:22 MediaServ kernel: BTRFS error (device nvme0n1p1): error loading props for ino 7314709 (root 5): -117 May 5 08:30:22 MediaServ kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=45910523904 parent_transid=218206 key expected=(7314709,12,281474984017009) has=(7314709,12,7306353) May 5 08:30:22 MediaServ kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=45910523904 parent_transid=218206 key expected=(7314709,12,281474984017009) has=(7314709,12,7306353) May 5 08:30:22 MediaServ kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=45910523904 parent_transid=218206 key expected=(7314709,12,281474984017009) has=(7314709,12,7306353) May 5 08:30:22 MediaServ kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=45910523904 parent_transid=218206 key expected=(7314709,12,281474984017009) has=(7314709,12,7306353) May 5 08:30:22 MediaServ kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=45910523904 parent_transid=218206 key expected=(7314709,12,281474984017009) has=(7314709,12,7306353) May 5 08:30:22 MediaServ kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=45910523904 parent_transid=218206 key expected=(7314709,12,281474984017009) has=(7314709,12,7306353)
  14. I ended up nuking my docker.img to start fresh wondering if it was one of my containers too. Seemed to fix things for awhile. Managed to reinstall plex till the server locked up again while scanning my libraries. Was planning on running memtest overnight/all day tomorrow since I work all day and won't need access to anything on their at the moment. Will update here with any results.
  15. Not sure what I've changed ( haven't updated/installed anything in about 3 days ) but all of a sudden I'm having immense difficulties accessing the Unraid UI. No issues loading Main, Shares, Users, Settings, Plugins (feels a bit slower than normal and cannot update plugins, script wont run when I hit the button), Apps, and Tools. The Dashboard won't load completely (screenshot below), VM (sometimes loads, sometimes won't) and Docker tabs (will not load anything below the navigation bar at all) are all causing me a major headache. If there are any other logs (sys log below) or diagnostics I can generate, please let me know. I have tried a server restart to no avail. Just want to get back to my data hording at this point!! syslog (2) mediaserv-diagnostics-20210504-1535.zip