irishjd

Are there any plans to add AVX2 support to VM's?

How do you create Influx tokens? According to the influx docs, this is done from the cli via the influxctl command, but that executable does not exist in the docker image. Is there an alternate way of generating tokens in this docker image?

Thanks for the info!

I have identified that plugin as the cause of the error as well. Thanks!

So I talked to the company that I bought the drive from, and their tech folks says its a firmware incompatibility between the drive and the disk controller. I guess it could be, but I have never run across that before.

I just started seeing the error “no such column: smart_reallocated_sector_count”. It is in red text just below the top menu bar.

That is the only thing I have not tried. I will go ahead and shut down the server, remove the drive, clean the contacts on the drive, re-insert, and then re-seat it. If that doesn’t work, it looks like I probably got a lemon.

I think the disk might be bad. I ran the blkdiscard command on it and didnt have any errors. However when I go to MAIN-UD i see the drive listed (sdm), but it says its size is 0. If I try to add it to my Cache Pool Devices, it is not listed as available.

Good point… Instead I am going try to “clear” the disk by wiping the MBR via a dd command. If it works, I will post the actual dd command here in case someone else ever has an issue like this.

I just purchased a "used" Samsung SSD for use on my Dell R820. When I plug it in, the server sees it, Preclear states "Cannot Preclear". The logs show this: { "sdm": { "ID_SCSI_SERIAL": "P0NA0H912234", "ID_SERIAL": "35002538a069d5590", "ID_SERIAL_SHORT": "5002538a069d5590", "ID_VENDOR": "SAMSUNG", "SERIAL_SHORT": "P0NA0H912234", "SERIAL": "35002538a069d5590", "BUS": "scsi", "FSTYPE": "", "SMART": "-d auto", "FAMILY": "SAMSUNG P1633N19 EMC1920", "MODEL": "SAMSUNG P1633N19 EMC1920 - Rev. EQPC", "FIRMWARE": "n\/a", "SIZE": 0, "SIZE_H": "0 B", "DEVICE": "\/dev\/sdm", "PARTS": [], "NAME": "sdm", "NAME_H": "sdm", "RUNNING": false, "TIMESTAMP": 0, "TEMP": "*", "SSD": true, "PRECLEAR": false } } Unraid is showing this: Feb 21 14:48:57 Unraid-1 kernel: sd 1:0:13:0: [sdm] Synchronizing SCSI cache Feb 21 14:48:57 Unraid-1 kernel: sd 1:0:13:0: [sdm] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK Feb 21 14:49:02 Unraid-1 kernel: sd 1:0:14:0: [sdm] Spinning up disk... Feb 21 14:49:29 Unraid-1 kernel: sd 1:0:14:0: [sdm] Unsupported sector size 520. Feb 21 14:49:29 Unraid-1 kernel: sd 1:0:14:0: [sdm] 0 512-byte logical blocks: (0 B/0 B) Feb 21 14:49:29 Unraid-1 kernel: sd 1:0:14:0: [sdm] 4160-byte physical blocks Feb 21 14:49:29 Unraid-1 kernel: sd 1:0:14:0: [sdm] Write Protect is off Feb 21 14:49:29 Unraid-1 kernel: sd 1:0:14:0: [sdm] Mode Sense: b7 00 10 08 Feb 21 14:49:29 Unraid-1 kernel: sd 1:0:14:0: [sdm] Write cache: enabled, read cache: enabled, supports DPO and FUA Feb 21 14:49:29 Unraid-1 kernel: sd 1:0:14:0: [sdm] Preferred minimum I/O size 8192 bytes Feb 21 14:49:29 Unraid-1 kernel: sd 1:0:14:0: [sdm] Optimal transfer size 8192 bytes Feb 21 14:49:29 Unraid-1 kernel: sd 1:0:14:0: [sdm] Attached SCSI disk Feb 21 14:49:32 Unraid-1 emhttpd: device /dev/sdm has size zero I stopped the array, and still no joy. Did I happen to get a bad drive, or is there a way to "wipe" the drive and make Unraid look at it again? v/r Jon

Thanks @JorgeB... when I get back in town, I will take another stab at this. At least now, I know that the NIC, the GBIC, and the fiber are all good.

So there is definitely something going on with the network config. The only way I could get access back to my server was to shut it down, remove the flash drive, remove all the settings for the fiber interface from the network.cfg file, and reboot. I am about to go out of town awhile for work, so I am not going to mess with this any more until I get back. @JorgeBdo you guys have any tools for parsing the diagnostics dumps that can be shared? I would like to be able to do some of the detective work myself without having to bother everyone, but there are a lot of files created and when I am not exactly sure what I am looking for, it makes it difficult to look at the right file.

Once I get the 10GB link working, I plan on disabling the copper 1GB link.

The switch is directly connected to the DHCP router. This being the fact, it sounds like I might have a UniFi issue. I will check with them. Any idea how I can reset the GBIC to auto negotiate? I tried using: root@Unraid-1:~# sudo ethtool –s eth4 autoneg on netlink error: no device matches name (offset 24) netlink error: No such device netlink error: no device matches name (offset 24) netlink error: No such device netlink error: no device matches name (offset 24) netlink error: No such device netlink error: no device matches name (offset 24) netlink error: No such device netlink error: no device matches name (offset 24) netlink error: No such device No data available

So, I just received the Intel SFP+'s that Intel states are compatible with the NIC. I replaced the Dell SFP+'s with the Intel, and plugged the fiber in. Both the NIC and the switch show a link, but the interface (eth4) is still not pulling an IP address.According to ethtool, the SFP+ has autonegotiate turned off, so I configured the switch to set the connection at 10GBPS FDX. This has not corrected the issue. According to the switch, 854 MB have been transfered over the link, but only 86 kb have been received. I am puzzeled as to what the issue is. I will drop the latest diag dump here in hopes that someone can tell me what I am doing wrong. unraid-1-diagnostics-20240131-1454.zip