B1scu1T

Members
  • Posts

    46
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

B1scu1T's Achievements

Rookie

Rookie (2/14)

5

Reputation

  1. I just listened to the Podcast. Started the day with news that was driving me away, I now feel confident enough to buy an additional licence. Thanks guys.
  2. I appreciate the communication coming out now, but I think I speak for most of us when I say, I wish this had come before the software release. My only question is surrounding the guarantee Limetech are making towards future of "lifetime" (including existing basic/plus/pro) customers. Is there a genuine commitment towards existing customers retaining a perpetual license for all future Unraid versions, or is there a chance that Limetech have an expectation of a small upgrade fee in the case of major upgrades? I understand that you cannot talk from an absolute 100% basis, as who knows what the future will bring, but I would just like to make sure the foreseeable future has no plans for this, and if there is, that we are at least informed of it.
  3. I think this is the main thing we all want to know. Companies change direction, usually financial drivers behind it, I can respect that... and if they make the decision to go down the subscription route to grow the product then ok.... they might lose out on some referrals based on their (up-till-now) fair pricing model, but perhaps they will gain it back with investment into features, improved support level, and documentation. Perhaps they will also get more revenue from business customers.... I totally get and can respect all of that.... but... I'm certainly concerned by the prospect of the thing I bought being indirectly dis-honored in the ways we have seen companies treat similar situations elsewhere. The fact that: Is one of the lines that's been dug up certainly raises my eyebrow. It of course could mean nothing, Limetech could come out and say, "all existing licenses will be fully honored by the spirit they were sold", but there is enough in there, IMO, for us to speculate the worst case.
  4. I have had other "lifetime" software that has moved to a subscription model, and the way they manage it without breaking the terms they sold the software on is to just release the software under a new name or version. So for example, you have a lifetime version of Unraid 6 but next year they release Unraid 7. To get this upgrade you either have to pay the subscription, or pay an upgrade fee. I'm not totally opposed to this model if the fees are reasonable, the time between major upgrades is long, and the support level of the software reflects that, but I'm not paying $100s for software that remains largely community supported.
  5. Yeah it's a branded startech reverse SAS breakout and I suppose it has been in and out of a lot of builds. I'm going to perhaps try with a HBA and straight SAS cable before I buy anything, mostly because that's what I already own..
  6. I ran the extended test anyway just to be safe. It said it finished without error, and doesnt look like anything to be concerned about there. I'll change the cable but just a bit baffled that there would be an error without anything being touched. (correct me if wrong) tower-smart-20240214-1524.zip
  7. So although the system wouldn't stop, it did shut down safely. Now booted up and running an extended smart test on that drive but if anyone has any clue what went wrong, or how to find out what went wrong I would really appreciate it.
  8. The drive logs Now disconnected sdg: Feb 12 13:31:32 Tower emhttpd: read SMART /dev/sdg Feb 12 13:33:33 Tower kernel: sd 6:0:0:0: [sdg] Synchronizing SCSI cache Feb 12 14:01:09 Tower emhttpd: spinning down /dev/sdg Feb 12 14:01:09 Tower emhttpd: sdspin /dev/sdg down: 2 Feb 13 09:54:29 Tower emhttpd: error: hotplug_devices, 1713: No such file or directory (2): tagged device WDC_WUH721816ALE6L4_2BJ90ZUN was (sdg) is now (sdj) sdj in unassigned drives: Feb 9 19:28:49 Tower kernel: ata6: SATA max UDMA/133 abar m2048@0xfc400000 port 0xfc400180 irq 87 Feb 9 19:28:49 Tower kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Feb 9 19:28:49 Tower kernel: ata6.00: ATA-11: WDC WUH721816ALE6L4, PCGNW232, max UDMA/133 Feb 9 19:28:49 Tower kernel: ata6.00: 31251759104 sectors, multi 16: LBA48 NCQ (depth 32), AA Feb 9 19:28:49 Tower kernel: ata6.00: Features: NCQ-sndrcv NCQ-prio Feb 9 19:28:49 Tower kernel: ata6.00: configured for UDMA/133 Feb 12 13:31:23 Tower kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Feb 12 13:31:32 Tower kernel: ata6.00: configured for UDMA/133 Feb 12 13:33:13 Tower kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Feb 12 13:33:18 Tower kernel: ata6.00: qc timeout after 5000 msecs (cmd 0xec) Feb 12 13:33:18 Tower kernel: ata6.00: failed to IDENTIFY (I/O error, err_mask=0x4) Feb 12 13:33:18 Tower kernel: ata6.00: revalidation failed (errno=-5) Feb 12 13:33:23 Tower kernel: ata6: link is slow to respond, please be patient (ready=0) Feb 12 13:33:28 Tower kernel: ata6: found unknown device (class 0) Feb 12 13:33:28 Tower kernel: ata6: SATA link down (SStatus 1 SControl 300) Feb 12 13:33:28 Tower kernel: ata6: limiting SATA link speed to <unknown> Feb 12 13:33:30 Tower kernel: ata6: SATA link down (SStatus 1 SControl 3F0) Feb 12 13:33:30 Tower kernel: ata6.00: disable device Feb 12 13:33:33 Tower kernel: ata6: SATA link down (SStatus 1 SControl 300) Feb 12 13:33:33 Tower kernel: ata6.00: detaching (SCSI 6:0:0:0) Feb 12 13:33:35 Tower kernel: ata6: SATA link down (SStatus 1 SControl 300) Feb 12 13:33:35 Tower kernel: ata6: limiting SATA link speed to 1.5 Gbps Feb 12 13:33:37 Tower kernel: ata6: SATA link down (SStatus 1 SControl 310) Feb 12 13:33:37 Tower kernel: ata6: limiting SATA link speed to 1.5 Gbps Feb 12 13:33:39 Tower kernel: ata6: SATA link down (SStatus 1 SControl 310) Feb 12 13:33:39 Tower kernel: ata6: limiting SATA link speed to 1.5 Gbps Feb 12 13:33:41 Tower kernel: ata6: SATA link down (SStatus 1 SControl 310) Feb 12 13:33:41 Tower kernel: ata6: limiting SATA link speed to 1.5 Gbps Feb 12 13:33:42 Tower kernel: ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Feb 12 13:33:43 Tower kernel: ata6.00: ATA-11: WDC WUH721816ALE6L4, PCGNW232, max UDMA/133 Feb 12 13:33:43 Tower kernel: ata6.00: 31251759104 sectors, multi 16: LBA48 NCQ (depth 32), AA Feb 12 13:33:43 Tower kernel: ata6.00: Features: NCQ-sndrcv NCQ-prio Feb 12 13:33:43 Tower kernel: ata6.00: configured for UDMA/133 Feb 12 13:33:43 Tower kernel: sd 6:0:0:0: [sdj] 31251759104 512-byte logical blocks: (16.0 TB/14.6 TiB) Feb 12 13:33:43 Tower kernel: sd 6:0:0:0: [sdj] 4096-byte physical blocks Feb 12 13:33:43 Tower kernel: sd 6:0:0:0: [sdj] Write Protect is off Feb 12 13:33:43 Tower kernel: sd 6:0:0:0: [sdj] Mode Sense: 00 3a 00 00 Feb 12 13:33:43 Tower kernel: sd 6:0:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Feb 12 13:33:43 Tower kernel: sd 6:0:0:0: [sdj] Preferred minimum I/O size 4096 bytes Feb 12 13:33:43 Tower kernel: sdj: sdj1 Feb 12 13:33:43 Tower kernel: sd 6:0:0:0: [sdj] Attached SCSI disk Feb 12 13:33:43 Tower kernel: ata6.00: exception Emask 0x10 SAct 0x1f0 SErr 0x280100 action 0x6 frozen Feb 12 13:33:43 Tower kernel: ata6.00: irq_stat 0x08000000, interface fatal error Feb 12 13:33:43 Tower kernel: ata6: SError: { UnrecovData 10B8B BadCRC } Feb 12 13:33:43 Tower kernel: ata6.00: failed command: READ FPDMA QUEUED Feb 12 13:33:43 Tower kernel: ata6.00: cmd 60/70:20:00:fe:bf/00:00:46:07:00/40 tag 4 ncq dma 57344 in Feb 12 13:33:43 Tower kernel: ata6.00: status: { DRDY } Feb 12 13:33:43 Tower kernel: ata6.00: failed command: READ FPDMA QUEUED Feb 12 13:33:43 Tower kernel: ata6.00: cmd 60/80:28:78:fe:bf/00:00:46:07:00/40 tag 5 ncq dma 65536 in Feb 12 13:33:43 Tower kernel: ata6.00: status: { DRDY } Feb 12 13:33:43 Tower kernel: ata6.00: failed command: READ FPDMA QUEUED Feb 12 13:33:43 Tower kernel: ata6.00: cmd 60/78:30:08:ff:bf/00:00:46:07:00/40 tag 6 ncq dma 61440 in Feb 12 13:33:43 Tower kernel: ata6.00: status: { DRDY } Feb 12 13:33:43 Tower kernel: ata6.00: failed command: READ FPDMA QUEUED Feb 12 13:33:43 Tower kernel: ata6.00: cmd 60/38:38:88:ff:bf/00:00:46:07:00/40 tag 7 ncq dma 28672 in Feb 12 13:33:43 Tower kernel: ata6.00: status: { DRDY } Feb 12 13:33:43 Tower kernel: ata6.00: failed command: READ FPDMA QUEUED Feb 12 13:33:43 Tower kernel: ata6.00: cmd 60/28:40:c8:ff:bf/00:00:46:07:00/40 tag 8 ncq dma 20480 in Feb 12 13:33:43 Tower kernel: ata6.00: status: { DRDY } Feb 12 13:33:43 Tower kernel: ata6: hard resetting link Feb 12 13:33:43 Tower kernel: ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Feb 12 13:33:43 Tower kernel: ata6.00: configured for UDMA/133 Feb 12 13:33:43 Tower kernel: sd 6:0:0:0: [sdj] tag#4 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 12 13:33:43 Tower kernel: sd 6:0:0:0: [sdj] tag#4 Sense Key : 0x5 [current] Feb 12 13:33:43 Tower kernel: sd 6:0:0:0: [sdj] tag#4 ASC=0x21 ASCQ=0x4 Feb 12 13:33:43 Tower kernel: sd 6:0:0:0: [sdj] tag#4 CDB: opcode=0x88 88 00 00 00 00 07 46 bf fe 00 00 00 00 70 00 00 Feb 12 13:33:43 Tower kernel: I/O error, dev sdj, sector 31251758592 op 0x0:(READ) flags 0x80700 phys_seg 14 prio class 2 Feb 12 13:33:43 Tower kernel: sd 6:0:0:0: [sdj] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 12 13:33:43 Tower kernel: sd 6:0:0:0: [sdj] tag#5 Sense Key : 0x5 [current] Feb 12 13:33:43 Tower kernel: sd 6:0:0:0: [sdj] tag#5 ASC=0x21 ASCQ=0x4 Feb 12 13:33:43 Tower kernel: sd 6:0:0:0: [sdj] tag#5 CDB: opcode=0x88 88 00 00 00 00 07 46 bf fe 78 00 00 00 80 00 00 Feb 12 13:33:43 Tower kernel: I/O error, dev sdj, sector 31251758712 op 0x0:(READ) flags 0x80700 phys_seg 15 prio class 2 Feb 12 13:33:43 Tower kernel: sd 6:0:0:0: [sdj] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 12 13:33:43 Tower kernel: sd 6:0:0:0: [sdj] tag#6 Sense Key : 0x5 [current] Feb 12 13:33:43 Tower kernel: sd 6:0:0:0: [sdj] tag#6 ASC=0x21 ASCQ=0x4 Feb 12 13:33:43 Tower kernel: sd 6:0:0:0: [sdj] tag#6 CDB: opcode=0x88 88 00 00 00 00 07 46 bf ff 08 00 00 00 78 00 00 Feb 12 13:33:43 Tower kernel: I/O error, dev sdj, sector 31251758856 op 0x0:(READ) flags 0x80700 phys_seg 15 prio class 2 Feb 12 13:33:43 Tower kernel: sd 6:0:0:0: [sdj] tag#7 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 12 13:33:43 Tower kernel: sd 6:0:0:0: [sdj] tag#7 Sense Key : 0x5 [current] Feb 12 13:33:43 Tower kernel: sd 6:0:0:0: [sdj] tag#7 ASC=0x21 ASCQ=0x4 Feb 12 13:33:43 Tower kernel: sd 6:0:0:0: [sdj] tag#7 CDB: opcode=0x88 88 00 00 00 00 07 46 bf ff 88 00 00 00 38 00 00 Feb 12 13:33:43 Tower kernel: I/O error, dev sdj, sector 31251758984 op 0x0:(READ) flags 0x80700 phys_seg 7 prio class 2 Feb 12 13:33:43 Tower kernel: sd 6:0:0:0: [sdj] tag#8 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 12 13:33:43 Tower kernel: sd 6:0:0:0: [sdj] tag#8 Sense Key : 0x5 [current] Feb 12 13:33:43 Tower kernel: sd 6:0:0:0: [sdj] tag#8 ASC=0x21 ASCQ=0x4 Feb 12 13:33:43 Tower kernel: sd 6:0:0:0: [sdj] tag#8 CDB: opcode=0x88 88 00 00 00 00 07 46 bf ff c8 00 00 00 28 00 00 Feb 12 13:33:43 Tower kernel: I/O error, dev sdj, sector 31251759048 op 0x0:(READ) flags 0x80700 phys_seg 5 prio class 2 Feb 12 13:33:43 Tower kernel: ata6: EH complete Feb 12 13:33:45 Tower unassigned.devices: Partition '/dev/sdj1' does not have a file system and cannot be mounted. Feb 13 09:54:29 Tower emhttpd: error: hotplug_devices, 1713: No such file or directory (2): tagged device WDC_WUH721816ALE6L4_2BJ90ZUN was (sdg) is now (sdj) Feb 13 09:54:29 Tower emhttpd: read SMART /dev/sdj
  9. Hi All, I'm running Unraid 6.12.6 on an ASRock X570D4U with a 4650G Pro and 64GB ECC RAM. Sadly I woke up today to a disabled drive warning: I had a look in my syslog and found these errors: Feb 13 00:00:06 Tower Plugin Auto Update: Community Applications Plugin Auto Update finished Feb 13 04:00:26 Tower kernel: md: disk29 read error, sector=3907594640 Feb 13 04:00:26 Tower emhttpd: read SMART /dev/sdh Feb 13 04:00:26 Tower emhttpd: read SMART /dev/sdf Feb 13 04:00:38 Tower emhttpd: read SMART /dev/sdd Feb 13 04:00:38 Tower emhttpd: read SMART /dev/sde Feb 13 04:00:38 Tower emhttpd: read SMART /dev/sdb Feb 13 04:00:38 Tower emhttpd: read SMART /dev/sdc Feb 13 04:00:38 Tower emhttpd: read SMART /dev/sdi Feb 13 04:00:49 Tower kernel: md: disk29 write error, sector=3907594640 Feb 13 04:01:01 Tower sSMTP[12879]: Creating SSL connection to host Feb 13 04:01:01 Tower sSMTP[12879]: SSL connection using TLS_AES_256_GCM_SHA384 Feb 13 04:01:04 Tower sSMTP[12879]: Sent mail for [censored] (221 2.0.0 closing connection y12-20020a056000108c00b0033b40a3f92asm8358077wrw.25 - gsmtp) uid=0 username=root outbytes=770 Feb 13 04:02:26 Tower root: /etc/libvirt: 125.7 MiB (131817472 bytes) trimmed on /dev/loop3 Feb 13 04:02:26 Tower root: /var/lib/docker: 3.7 GiB (3952398336 bytes) trimmed on /dev/loop2 Feb 13 04:02:26 Tower root: /mnt/cache: 314.3 GiB (337479950336 bytes) trimmed on /dev/mapper/nvme1n1p1 Feb 13 04:30:39 Tower emhttpd: spinning down /dev/sdd Feb 13 04:30:39 Tower emhttpd: spinning down /dev/sde Feb 13 04:30:39 Tower emhttpd: spinning down /dev/sdb Feb 13 04:30:39 Tower emhttpd: spinning down /dev/sdc Feb 13 04:30:39 Tower emhttpd: spinning down /dev/sdi Feb 13 04:30:58 Tower emhttpd: spinning down /dev/sdh Feb 13 04:30:58 Tower emhttpd: spinning down /dev/sdf Feb 13 09:00:11 Tower emhttpd: read SMART /dev/sdh Feb 13 09:00:21 Tower emhttpd: read SMART /dev/sdd Feb 13 09:27:31 Tower emhttpd: read SMART /dev/sdc Feb 13 09:28:00 Tower emhttpd: read SMART /dev/sdi Feb 13 09:28:13 Tower emhttpd: read SMART /dev/sdb Feb 13 09:30:30 Tower emhttpd: spinning down /dev/sdh Feb 13 09:54:28 Tower webGUI: Successful login user root from 192.168.1.175 Feb 13 09:54:29 Tower emhttpd: error: hotplug_devices, 1713: No such file or directory (2): tagged device WDC_WUH721816ALE6L4_2BJ90ZUN was (sdg) is now (sdj) Feb 13 09:54:29 Tower emhttpd: read SMART /dev/sdj Feb 13 09:54:29 Tower kernel: emhttpd[6175]: segfault at 67c ip 000055776d0f197b sp 00007ffc12d22d60 error 4 in emhttpd[55776d0dc000+25000] likely on CPU 11 (core 6, socket 0) Feb 13 09:54:29 Tower kernel: Code: e0 44 01 00 48 89 45 f8 48 8d 05 05 32 01 00 48 89 45 f0 e9 79 01 00 00 8b 45 ec 89 c7 e8 eb 87 ff ff 48 89 45 d8 48 8b 45 d8 <8b> 80 7c 06 00 00 85 c0 0f 94 c0 0f b6 c0 89 45 d4 48 8b 45 e0 48 Nobody else in the house, so aside from the potential of some unwanted rodent guests (I hope not) there is nobody who could have touched the server. For some reason, I now can't stop the array. Diags attached, can anyone help me understand what's happened and/or what I need to do? Really hoping this isnt an actual drive fault as these suckers aint cheap. Thanks, tower-diagnostics-20240213-1002.zip
  10. I managed to get the board alive again through what seems to be nothing but sheer luck, however I didn't get to the bottom of why there is constant crashes. I just bit the bullet and bought new hardware. Now running Intel and Supermicro and it's been flawless. Despite the lack of Memtest reported failures, I'm inclined to lean towards it being a Memory issue, slight possibility there is something wrong with the 4650G CPU or UEFI settings.
  11. So on the one hand, I ran the 4 pass memtest with ECC polling enabled twice and no errors... so dont think it's that. On the other hand, the ASRock Rack support team supplied me with some SOC flash tools, but they don't recognise the BMC image to fix my IPMI.
  12. I got it to finally boot the Memtest USB drive but somehow in the process I have bricked my IPMI 😄 It's been like this since my last post pretty much Seriously f**k this motherboard.
  13. Man, no matter what I do, this motherboard will not boot from an EFI based USB image. Ended up having to clear my CMOS as I fiddled with so many things I eventually couldn't get it to post at all.
  14. I honestly cant remember how I tested it, but good shout. No harm in running it again.
  15. The PSU is pretty new, and its a decent unit (Corsair TX850M). I could swap in my older CS450M though, that ran for years without fault so it would at least one of the variables removed. IPMI is also of absolutely no help and isn't reporting any issues other than clock sync, but it also isn't dropping out when the sever drops out which probably suggests there isnt a significant power issue. I have grabbed the debug logs from there. Some errors around the same time as the reboot but they don't, IMO, point to anything useful... bit beyond my expertise at this point The issue with tracing the individual components is that I have fiddled with settings previously, thinking I had figured out the problem (e.g. RAM settings/voltage, CPU settings, GPU settings), and then had the system stable for literally months with no crashes or reboots, so then I presume it is ok until it randomly happens again. At the moment it appears to be totally borked at exactly the wrong moment. I'm at breaking point tbh, I need this server to run at some capacity. I think im going to pick up an v6 E3 Xeon and supporting board from Ebay then I can experiment with this X570 and get to the bottom of its issues as a separate project (yipee). Might even just sell the board on and/or discuss with the retailer if it looks like there is a problem with it. var.zip