Jump to content

fmp4m

Members
  • Content Count

    324
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by fmp4m

  1. Hello - I am looking for either a Network Attached or SAS attached 2.5" RACK Mounted enclosure that is JBOD. I want to place SSD's in the chassis for use with the UnAssigned Devices plugin that I will be using as storage for SQL DB's and VM's that do not need protection. Just the storage accessible to Unraid servers I have. Any recommendations? I am looking for as cheap as reliably possible.
  2. Hi JorgeB That makes perfect sense for the 1tb build. I was trying to utilize the same knowledge in picking hardware for repairing my main rig, when I realized it was unfeasible to do. Sorry for any confusion. In my main rig, would you still advise a 8tb nvme or would 8tb 10k/15k sas be plenty?
  3. Revisiting this, as recent fluke timing - my motherboard lost died (PCIe + Sata channels died). I have to replace my main server - which is all SAS/SATA drives. I had stuck in my head NVME for cache not Parity - so I ordered a server grade mobo with two m.2 slots to put those in per this threads recommendations. Well, I come back to review and realize you said parity. If I have 8tb drives in my array, I would need 8tb parity drives. How the hell would one do that? The cheapest quality 8tb nvme is the Sabrent Rocket ($1400) and I would need two to protect my 27 drive (soon to grow to add more drives to fit in my 42 bay chassis). That would be $2400 in parity alone. I am reading you right that you recommend / use NVMe for Parity right? What size parity do you have?
  4. Im not exactly sure what happened, but when I upgraded to beta 30. I can only see 8 of my 27 drives. The rest appear as missing and I received a "Array Stopped - Stale Configuration" error. I rebooted, same, rolled back to Beta 29 and still have the issue. Im thinking either my expanders or one of my cards stopped responding, perhaps due to a driver change? Diags attached. Server unusable until resolved. All drives present and working prior to the update. arcanine-diagnostics-20201014-1627.zip
  5. Is there a different SSD you would recommend, or in your opinion, would I be better going a different route than full SSD? Im open to full suggestions and value your opinion JorgeB
  6. Samsung 860 EVO 1TB SSD 3-bit MLC V-NAND SATA III 6Gb/s No room for an NVME in this rack server. Ultimately, I am looking for consistent speed that is reliable for rapid-access data. The speed is from the read part of the server that I need, not the write.
  7. I am rebuilding a R420 server, with all SSD drives. (8 x 1TB SSD). My question is, what would be the optimal configuration, given it will be speedy (primary use is high-speed data needs on a 10GbE network). 7x Data 1x Parity and no Cache? 6x Data 1x Parity and 1x Cache? 5x Data 2x Parity and 1x Cache? 5x Data 1x Parity and 2x Cache? I have been weighing this and can't come to a conclusion. Please lend your advice and reasoning here?
  8. I was able to find the linux bash files - I stopped my array and was able to flash both 9300-8i cards to Firmware Version 16.00.10.00. I have not touched the expanders - I am not sure how. root@Arcanine:/mnt/user/isos/SAS3# sas3flash -list -c 0 Avago Technologies SAS3 Flash Utility Version 17.00.00.00 (2018.04.02) Copyright 2008-2018 Avago Technologies. All rights reserved. Adapter Selected is a Avago SAS: SAS3008(C0) Controller Number : 0 Controller : SAS3008(C0) PCI Address : 00:0a:00:00 SAS Address : 500605b-0-092f-6310 NVDATA Version (Default) : 0e.01.00.07 NVDATA Version (Persistent) : 0e.01.00.07 Firmware Product ID : 0x2221 (IT) Firmware Version : 16.00.10.00 NVDATA Vendor : LSI NVDATA Product ID : SAS9300-8i BIOS Version : 08.37.00.00 UEFI BSD Version : 18.00.00.00 FCODE Version : N/A Board Name : SAS9300-8i Board Assembly : H3-25573-00G Board Tracer Number : SV43226242 Finished Processing Commands Successfully. Exiting SAS3Flash. root@Arcanine:/mnt/user/isos/SAS3# sas3flash -list -c 1 Avago Technologies SAS3 Flash Utility Version 17.00.00.00 (2018.04.02) Copyright 2008-2018 Avago Technologies. All rights reserved. Adapter Selected is a Avago SAS: SAS3008(C0) Controller Number : 1 Controller : SAS3008(C0) PCI Address : 00:41:00:00 SAS Address : 500605b-0-0914-f930 NVDATA Version (Default) : 0e.01.00.07 NVDATA Version (Persistent) : 0e.01.00.07 Firmware Product ID : 0x2221 (IT) Firmware Version : 16.00.10.00 NVDATA Vendor : LSI NVDATA Product ID : SAS9300-8i BIOS Version : 08.37.00.00 UEFI BSD Version : 18.00.00.00 FCODE Version : N/A Board Name : SAS9300-8i Board Assembly : H3-25573-00G Board Tracer Number : SV42826505 Finished Processing Commands Successfully. Exiting SAS3Flash.
  9. The drive was corrupted beyond recovery for 90% of the data. I have now formatted the drive, checked it with pre-zero and the drive is healthy. I have reused it as my cache drive now. I am looking for the LSI flash files again and will make a DOS 6.22 / FreeDOS boot drive and try to update the cards. Do I need to update the expanders or just the two PCIe Cards.
  10. Hi Johnnie, You recommended updating the LSI firmware once before, I do not have access to a windows desktop for the flashing, and have not been able to find a Linux / Unraid way to flash them. If you have any insight on that, or can point me in the direction, I would love to update them. Booting to Live CD versions failed also. Is everything on the cache dead or can I safely copy whats on it off?
  11. Began receiving docker errors and was unable to correct them, so I rebooted my server, now I am receiving "Cache" is read-only. There is plenty of space on the cache drive, and data is readable but it is read-only. I can't seem to figure out why it went read-only or how to correct. Scrub/Balance cancels due to the RO status. arcanine-diagnostics-20200731-1336.zip
  12. I have been loving Plex transcoding with my P1000 card, until today. I rebooted my server and Plex docker will not start. It halts at the nvidia card startup portion. docker: Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused "process_linux.go:432: running prestart hook 0 caused \"error running hook: exit status 1, stdout: , stderr: nvidia-container-cli: initialization error: cuda error: no cuda-capable device is detected\\n\""": unknown. The command failed. I have reinstalled the kernel drivers, checked the GPU UUID and rebuilt the docker from scratch. It will not start.
  13. I have began having an odd problem where my Network Stats are not working. They say "vnstat service must berunning STARTED to view network stats." So I checked: /etc/rc.d/rc.vnstat start received: Error: Not enough free diskspace available in "/var/lib/vnstat/", exiting. My array/cache/ has plenty of space far beyond any need this would have so I checked: ls -l /var/lib/vnstat total 4 -rw-r--r-- 1 root root 0 Jul 29 16:49 vnstat.db Any ideas?
  14. Hi JonP sorry for the delay, I checked and no, I have over 2TB available. Cache was balanced and scrubbed. I have no idea why it can't be recreated. There may be something wrong with my setup - I've posted a couple issues that got worked through and a couple untouched in general, however I have had time-outs occur when updating dockers and dockers disappearing because of it, as well as really sluggish web gui responses in general. Can't seem to nail it down at this point - and generic posts tend to yield no results. Maybe its related to my system only?
  15. New ISO created out of the Media Creation Tool - Wanted to make sure it had all the latest patches. I don't keep a cached copy.
  16. I also vote for all the icons in this thread be added to the repo - this script is amazing and the icons are too!
  17. Using virtio instead of Sata did work for WIndows 10. Using raw with linux worked. Odd things, but I can confirm I am good now.
  18. Sorry, thought I mentioned in the post, Either raw or qcow does the same for me. On all 3 servers I tried. Two Intel, one amd.
  19. I have attempted to install Linux VMs and Windows VMs. When creating I set 120-240GB depending on which I want at the time. Loading the Client OS Installer, selecting the created virtual hard drive - it shows no space available or partitionable. Vdisk.img = 56kb in size. I believe that the VM Creation tool is not provisioning QCow or raw drives space correctly. Image from WIn10 install post-driver installation shows the drive with zero space for easier clarity.
  20. Occasionally the USB Logitech receiver for a mouse/keyboard, but during this event - nothing else.
  21. Update, The Exclamation Mark was my fault. I didn't put the USB in the same spot and it reverted boot order. After correcting the boot order to the USB - it booted just fine. the root=sda did infact fix the issue, however, This concerns me that it will be needed going forward - and why would it be needed now?
  22. Ok, Recreated the USB = Same issue Adding root=sda to the syslinux.cfg as suggested by Squid = new issue. Now I get a black screen with cursor and an Intimidating exclamation mark only.