Navyjoker

Members
  • Posts

    9
  • Joined

  • Last visited

Recent Profile Visitors

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

Navyjoker's Achievements

Noob

Noob (1/14)

0

Reputation

1

Community Answers

  1. Hi guys, I have two 6T Seagate Exos SAS drives that I have connected. I did purchase them from two different places on EBAY. One of my drives showed up perfectly and was able to be formatted. The other shows up in Unassigned Devices, the mount button is grayed out and it shows 0B for the size (see screenshot). I found in the logs where it says 512 - byte logical blocks, so I don't think it is that 520 size issue with SAS drives... I have attached the diagnostics if someone could please take a look at it and see if you can find what might be happening. Thanks! valhalla-diagnostics-20220214-2005.zip
  2. I found this card https://www.ebay.com/itm/313695041101?epid=27026538211&hash=item4909ae764d:g:rO8AAOSwwjlhUdOb what do you think? it is already in IT mode, is not a RAID controller, and has two mini SAS internal ports.
  3. Those are all SATA controllers. I need a SAS controller with mini SAS ports, not SATA ports...
  4. As far as I’ve researched, the M1015 is plug and play…
  5. Ok, so I have researched and if I purchase an M1015 SAS/SATA Controller (https://www.amazon.com/IBM-Serveraid-M1015-Controller-46M0831/dp/B0034DMSO6), I can just disconnect the mini SAS cable from the port on the motherboard and plug it into one of the two mini SAS ports on the card. This will instantly allow my SAS drives and SATA drives to work. This will also give me the capability of adding 4 more hard drives. My hesitation lies in the fact that I would have to remove my GPU card, which I purchased specifically for hardware transcoding in Plex. My other option is to purchase new SATA only hard drives and use those - but that's going to cost some $$. I know the onboard graphics card in the MicroServer Gen8 is not very good, but I wonder if it will still be ok for running my Plex server. Does anyone have any thoughts?
  6. I am trying to figure out what that is, and how to get it. Any ideas, or have you heard of that before?
  7. After reading more about this, I decided to start over and try a few things: 1. I made sure and stopped my array before shutting down 2. I downloaded and used the "Open Files" app to see what else I had opened 3. I stopped all Dockers 4. I followed the guide here to update the timers Then I did a shutdown, and it worked perfectly! I was unaware of just how easy it is to have an "Unclean shutdown", that then effects your booting back up!
  8. Greetings, I am trying to get my two 6TB Exos SAS drives to be recognized in unRAID. My other two drives (1 SSD, 1 1TB HDD), both SATA, are recognized and set up in my array. My SSD is my Cache drive, and the 1TB drive is just in my array. I need to have one of my 6TB drives set as my parity drive, and the other one in my array. I have 4 SAS bays in my case, and have my drives set as follows: 1: SSD SATA, 2: 1TB SATA, 3: 6TB SAS, 4: 6TB SAS. The first diagnostics file I uploaded (valhalla-diagnostics-20220130-1650) was with this setup. I tried changing to: 1: SSD SATA, 2: 6TB SAS, 3: 6TB SAS, 4: 1TB SATA. The second diagnostics file I uploaded (valhalla-diagnostics-20220130-1831) was with this setup. I have my SATA controller set up as HP Dynamic Smart Array B320i Raid Controller in the BIOS. I have also tried the other option as well (SATA AHCII Controller or something), but that didn't work either. I have read that I need an HP Smart Array SAS License Key installed to provide support for SAS Hard Drives? Any ProLiant MS Gen8 users out there that might be able to confirm and help me if this is true? Lastly, on bootup I receive a "SATA3: COMRESET failed (errno=-32)" error that retries like 6 times before moving on. I am thinking this error might possibly have something to do with why my SAS drives aren't showing up? My setup is in my signature. I also attached my syslog in case that might help as well. Any help would be much appreciated! Thanks! valhalla-diagnostics-20220130-1650.zip valhalla-diagnostics-20220130-1831.zip valhalla-syslog-20220130-2354.zip
  9. Hi everyone, I cannot boot into my Unraid server. It gets stuck at: Starting rsyslogd daemon: /usr/sbin/rsyslogd -i /var/run/rsyslogd.pid I have tried: - plugging flash into PC, make backup of my 'config' folder. Then reformatting the usb flash - volume labelling it UNRAID - then copying over release from zip file. Next clicking 'make_bootable' as administrator, and then dragging my 'config' file backup to the flash. - putting it in my windows pc and it finds a fault and it restores it. After that I ran the command chkdsk [drive] /f /r /x. - a different thumb drive - a different usb 2.0 port I can reformat the drive and unzip the Unraid file onto the thumb drive and everything without removing and replacing the config file and it will typically allow me to boot into Unraid, but then I have to set everything back up again. So I don't know if it has to do with my config file, or that I am shutting down improperly or what - but every single time I try to shut down or reboot, it goes back. Seeing as though if I use the new config file it works, I feel as if it has to do with something in my config file. I have researched other posts and can't find a clear answer as to: how I can boot in again with my current config folder (so I don't have to start over), and how I can prevent this from ever happening again Thank you in advance for any assistance provided!