kbrutlag

Members
  • Posts

    21
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

kbrutlag's Achievements

Noob

Noob (1/14)

0

Reputation

  1. I appreciate the assistance, but I needed to get things going again so attached a 8TB 3.5" eSATA drive.
  2. No, all are 2.5" internal SATA drives. I just did a drive listing (dmesg | grep blocks) and all are reporting the same size (4.00 TB/3.64 TiB).
  3. I have reset the configuration and am still unable to assign any new 4TB drive I have (6 others all same MFG and type as array) as a new parity drive, Unraid still reports them all as 'Parity slot not biggest'. I've attached each drive to a different computer and deleted the 1 partition they each had and I'm still getting the same message. Is there a way to find out why? Thanks for all your assistance.
  4. Guess I didn't retain the important part, I appreciate you pointing that section out. I'll have a go at it and let you know. Thanks again.
  5. That looks a little scary - like it'll remove all the existing data is what it sounds like, especially the 'you have been warned' part. Seriously though, the only way to tell the system to remove a bad/missing drive is to start a new config? Like most, I have a TON of data I don't want to loose, granted the VERY important stuff is backed up but the other TBs of data is still important.
  6. UNRAID masterminds.... So I had my single 8TB parity drive fail and all I had to replace it quickly is a 4TB drive. No problem I thought since all the data drives are 4TB - oh, but wait, UNRAID won't let me because it says the 8TB drive is missing and the 4TB drive is not the largest in the system because of it. How do I go about telling UNRAID to forget about the 8TB drive so I can get the 4TB as the parity drive? Thanks
  7. Thanks all. I decided to just let the check run. Don't like using up SSD cycles on a clear, but until UnRAID has a better way to handle all SSD arrays, guess we're stuck.
  8. If at all possible, I'd rather not 'clear' an SSD. Is there any way around that?
  9. Hi all, I moved all my drives over to SSD a while back and recently replaced an SSD partiy drive with a much larger HD. I've tried adding the SSD to the array in an open spot (1) left over from the original move to SSDs. I used the 'Unassigned Devices' to remove the old parity partition off the drive, now the drive shows as new (blue square) only. Not sure why it's not the green circle. Thanks for any assistance. unraid-1-syslog-20191214-2322.zip System log attached
  10. bonienl - thanks much! This got everything going again. Not sure what happened with the network settings during the update, but all good now.
  11. Updated yesterday from 6.6.7 and noticed tonight that none of my dockers were able to access the Internet. Started doing some digging, and found that it's not the dockers, but the system in general. I have storage/GUI access and can ping to my firewall, but when I try to go further (ping 1.1.1.1) I get an immediate 'ping: connect: Network is unreachable'. I have two network interfaces (10G and 1G) both with static IP/DNS/gateway settings. One thing I find odd is, when I shutdown the 1G interface I could still ping the IP, so I tested removing its network cable - still able to ping it. Looking for a little direction on this one. Thanks much unraid-1-diagnostics-20190517-0218.zip
  12. Hello all, I recently dropped an Intel 10GbE card in my rig and have been unable to successfully get around the following error. From my research, it sounds like the driver may be locked to a specific type of SFP module(s) - mine is generic. Looking for more knowledge than I have and if possible, a resolution. Thanks much Aug 20 16:46:02 unRAID-1 kernel: Intel(R) 10GbE PCI Express Linux Network Driver - version 5.3.6 Aug 20 16:46:02 unRAID-1 kernel: Copyright(c) 1999 - 2018 Intel Corporation. Aug 20 16:46:02 unRAID-1 kernel: ixgbe 0000:01:00.0: failed to load because an unsupported SFP+ or QSFP module type was detected. Aug 20 16:46:02 unRAID-1 kernel: ixgbe 0000:01:00.0: Reload the driver after installing a supported module.
  13. Thanks everyone - I have a new LSI based controller on order. I'll let you know how things go in a few days.
  14. Thanks trurl - started a new check and it ran at good speed for a little over 2 hours then dropped. I've added a new diagnostic data file. unraid-1-diagnostics-20180820-1533.zip
  15. Hello - I run a parity check monthly, but this last one was taking a very long time to finish. When I checked, it had been running for a little over 23 hrs and had over 500K errors. I've since tried it a few more times and each one starts off with good speed, then drops way down. All the the drives are not reporting any trouble and I've even tried stopping Docker thinking that may have something to do with it since I recently set it up. I recently moved to new hardware (second time in 8 years), and nothing stood out - no errors, etc. I did add a 10 GB network card, and the driver is throwing errors about the SPF module not being supported. I asked our Linux administrator about it and his guess was that it wasn't configured to support generic modules, but that should not affect a parity check. I appreciate any insight, and have attached a diagnostic log. Thanks Ken unraid-1-diagnostics-20180819-1348.zip