argash

Members
  • Posts

    13
  • Joined

  • Last visited

Recent Profile Visitors

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

argash's Achievements

Newbie

Newbie (1/14)

3

Reputation

  1. I still haven't made any progress on this. I've ordered another card to try. However if anyone has any other suggestions I'm all ears. I think it's a software issue in unRAID but I can't confirm until the new card arrives.
  2. Got it set in the boot order. BIOS now sees it every time. Still not showing up in unraid and I have no idea why. I even edited my /boot/syslinux/syslinux.cfg as mentioned in another thread: default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label Unraid OS kernel /bzimage append pci=realloc=off initrd=/bzroot label Unraid OS GUI Mode menu default kernel /bzimage append initrd=/bzroot,/bzroot-gui label Unraid OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label Unraid OS GUI Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest
  3. Ok so I've made some progress. First I noticed that the firmware was off so I flashed that bad boy to get to here: Now I'm concerned that it doesn't have anything in it's boot order but it wouldn't let me change it. Now in safe mode when I run sas2flash -listall it only shows two of the cards though. Again I think it's the boot order. With out anything set for it I don't think it's actually booting that card. But again it wouldn't let me set it an order.
  4. Correct, at the moment nothing is assigned to parity because of the issues that I'm having. 9, 10, and 11 were the drives that failed before swapping out my sata cables and I still need to replace. How do I best check the LSI controllers though?
  5. I recently got my system back to stable after some bad sata cables caused several drives to fail simultaneously (thankfully no critical data lost!). After replacing the cables and returning things to stable I decided to upgrade my 2x 8TB parity drives to 2x 14TB drives after the recent BBY sale. After installing the drives and starting parity rebuild and preclear on the old 8's I came back the next day to find that parity was only building on one of the drives and the other was disabled. I decided to let parity continue building on the one and let the preclears finish. Once that was done I stopped the array and tried to re-add the "disabled" parity drive but it didn't show up... Strange. OK, well lets add the 8TBs to the array for now. That worked fine. Decided to restart the system to try adding the second parity drive. Same basic behavior. After a while it failed and disabled it self. I should also mention that during this time I've started to notice long boot times, however not every boot is long. Also sometimes the array takes forever to mount drives, but again, not always. I started to suspect more hardware issues so I monitored the boot sequence. But other than not always catching all 3 LSI screens (I have 3 LSI cards) I'm not seeing anything. Even when I don't see all three LSI screens during boot every drive is still showing up (except the 14's occasionally as stated). Now these are shucked drives, however I'm in a Storinator chassis so every drive bay is routed through molex power so that shouldn't be an issue. I did update my BIOS. I want to check the LSI BIOS but I'm not sure how. I'm attaching my diagnostics and looking through them myself but I'm hoping someone here can help me out. ETA: Oh, I've also tried moving them to other bays with no luck. tower-diagnostics-20220129-1754.zip
  6. They are still making major updates to the main bot. I have made templates for Redis and Galactus but have not yet gotten them to actually all work. Right now I'm waiting for the dev to hit a feature complete state so that I can work with him on creating a single docker image that we can use.
  7. My apologies for not responding faster, apparently I got unsubbed from the thread so I wasn't getting notifications. The developer has been releasing a flurry of new updates that have broken the bot on unraid at the moment. I am waiting for him to finish his slate of major updates before I work with him on fixing everything for unRAID. I will update this thread when that work is ready to commence.
  8. AutoMuteUs This is a Discord Bot to harness Among Us game data, and automatically mute/unmute players during the course of the game! Works in conjunction with amonguscapture. You will need to install the capture app locally to communicate with the bot. Instructions on getting the bot token(s) can be found here. It is reccomended that you create two bot tokens on discord (the docker bot app will accept and run both) if you play with a full 10 person lobby as the Discord API has a rate limit that can slow down the muting and unmuting with just a single token. Have any questions, concerns, bug reports, or just want to chat? Join the discord at https://discord.gg/ZkqZSWF! or reply to this thread.
  9. Oh I wasn't expecting you to. Just throwing it out there.
  10. So here's an interesting one. I setup reverse proxy with the LE/SWAG container and everything is working fine. However, when I go to generate new labels the QR codes are still pointing to the internal IP address. I've updated the App URL variable with the external URL and restarted the container but new codes still point to the internal IP not the URL.
  11. It's on my end, I finally noticed the second was my docker hub conversion. they looked identical at first.
  12. Interestingly they seem to be the same template, at least when I click through to them. And yes my SMTP settings work but I'm using gmail not yahoo.
  13. I just spent all day Friday pounding my head trying to make this work and failing. Thank you. I suspect I was failing due to trying to use the beta release but I can't confirm that. FYI apparently there is now TWO Snipe-IT templates in the app store so you may want to edit to update which one is yours. I used the first one and it worked like a charm.