Neostim

Members
  • Posts

    24
  • Joined

  • Last visited

Everything posted by Neostim

  1. Hi all, I'm running unRaid 6.9.2 and have selected "3ware" as my disk controller with twa0 as an additional parameter to get the SMART calls working. more details here: Each drive is showing it's SMART data correctly under it's own device page, one of those drives has failed SMART tests and is showing as an immediate failure however on the dashboard it shows as healthy, I suspect this is because the web ui isn't using the additional parameters set for the controller/disks under settings (same reason I don't see temperature on the dashboard but can see it on the drives device page). Is there any way around this, or a way to get email notifications for failures like this? P.S. I tried installing the latest RC of unRaid (as suggested on another post) however now the custom controller doesn't appear to work, I get an error running the smart command that worked in 6.9.2: smartctl -d 3ware,21 -a /dev/twa0 smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.14.15-Unraid] (local build) Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org No major number for /dev/twa listed in /proc/devices. Is the 3w-9xxx driver loaded? Smartctl open device: /dev/twa0 [3ware_disk_21] failed: setup_3ware_nodes("twa", "3w-9xxx") failed
  2. Thanks and yeah I was wrong on the 10TB being an SMR after looking closer -- I guess 9MB/sec will just have to do
  3. Hi all, I just bought 3 WD Red drives (WD40EFAX) and when I started the array they all started clearing at 8mb/sec, I stopped the array and removed 2 of them to see if just having one would go at 24mb/sec but it's currently clearing at 9mb/sec. This is the first time I'm adding new drives to the array with a valid parity so first time clearing but building the parity for the entire array (to a 10TB SMR drive) only took 3 days where as just clearing one of these 4TB drives is quoting 5 days. I I've attached my diagnostics file if anyone is willing to take a look and give me any suggestions to look at to find out why performance is so poor? Thanks! databank-diagnostics-20220101-0917.zip
  4. I thought so but couldn't find anything newer on the releases page, clearly I need to do some more googling, thank you!
  5. Old thread, but did you ever figure this out? I'm in the exact same boat.
  6. I'm running UnRaid 6.9.2 if that's what you mean. I'm able to pass through all the SMART details and can see the temperature in unRaid GUI under the SMART details (after updating the device to be twa0 and specifying a unit number, like this thread: but unfortunately the actual dashboard doesn't show it. It seems the dashboard doesn't seem to support the "twa0" and unit number when grabbing the temperature, at least from what I can see, even though it does pull it successfully under SMART
  7. I also couldn't login (it hung), logs said it couldn't connect to postgres ... I had to set the postgres user to photonix accidentally, had to delete the postgres docker, clear it's app data, re-install and then it was fine.
  8. I ended up downgrading and everything works fine again... I'll leave it like this for now
  9. I'm a bit late replying here, but thanks for offering to help! Here is the config: https://ibb.co/pvcFzgh I can navigate to it's page, so the local network is fine, but something in Unraid seems to be blocking it from accessing the internet.
  10. I upgraded to UnRaid 6.9.2 a couple days ago and now none of my dockers that us the br0 interface have internet connectivity, I can access them on my local network but they can't get out to the internet. I've been stumped on why this is, it's probably something simple but I haven't been able to figure it out My docker settings: https://ibb.co/Hq9mn8N My Interface settings: https://ibb.co/PQqH00K Does anyone have any suggestions?
  11. Yeah, I dropped down to half the RAM (16 from 32), haven't spent the time to figure out the slots I need to populate to gain some more yet as it's solely used as a NAS for my newer server, just happy it's online Thanks again.
  12. Success! I took out one of the CPU's and it finally booted, of course I tested everything else under the sun first, but server is now running
  13. Thanks Armed, I didn't make any changes, just noticed it powered down overnight. Good point on testing CPU/Dimms one-by-one, I'll do that today and return with the results.
  14. Firstly the hardware: Supermicro X8DTi motherboard 2 x Xeon E5530 CPU's 32GB Ram LSI 9650SE-24M8 Drive controller SAS846TQ Backblane It's been running fine for 2 years, yesterday I noticed it went down, hooked it up to a monitor and no output. When I power it on, the drives all spin up and fans come on, but no LED's on the system status (other then a consistent blinking green light for the NIC status on the front panel) and no output to the monitor. At first I thought maybe the onboard video output died, but it never comes online network-wise either. Any thoughts on where I should start troubleshooting? Thanks for any feedback!
  15. I have the exact same issue as you in trying it out just now... glad you submitted the issue at the Github page Edit: Only thing I can think of is if it wants you to use the hostname instead of IP, which in a docker doesn't really work... In the read me it does state: EDIT: For anyone who might run into this, it seems the newest build is broke, I used an older one and got it to run, change repository in the docker to: huginn/huginn:198f0126b8638a39091d4083b03bacd96fca1d1d
  16. Did you ever resolve this? I'm having the exact same issue.
  17. Thanks! That helped, I've dropped the "bad" disk from the array now, parity still at 8mb/sec currently
  18. Reading through this handy diagnostics file I see the following, maybe this is the cause of my issues, read errors on one of the data drives: Apr 14 17:00:44 Tower kernel: 3w-9xxx: scsi5: ERROR: (0x03:0x0202): Drive ECC error:port=19. Apr 14 17:00:44 Tower kernel: sd 5:0:7:0: [sdi] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Apr 14 17:00:44 Tower kernel: sd 5:0:7:0: [sdi] tag#0 Sense Key : 0x3 [current] Apr 14 17:00:44 Tower kernel: sd 5:0:7:0: [sdi] tag#0 ASC=0x11 ASCQ=0x0 Apr 14 17:00:44 Tower kernel: sd 5:0:7:0: [sdi] tag#0 CDB: opcode=0x28 28 00 02 a5 5e 40 00 01 00 00 Apr 14 17:00:44 Tower kernel: print_req_error: I/O error, dev sdi, sector 44392000 Apr 14 17:00:44 Tower kernel: md: disk6 read error, sector=44391936 I'll remove the drive from the array and try parity again to see if any improvements.
  19. Thanks, here they are! tower-diagnostics-20180414-1743.zip
  20. I'm on the trial of unRaid, I've got 6 data drives and 1 parity drive, all 2TB or 1TB in size, I'm seeing about 8-19MB/sec on parity creation, currently 2 days and 10 hours to finish. I can't seem to cancel parity to try swapping in a different 2TB drive in case it's the drive, is there any way I could sanity check this drive in unraid to eliminate that as a possibility? SMART status isn't exactly working with my 3Ware 9650SE-24M8 so even if it was having issues I'm not sure I would know.