steenbag

Hi all, I have an Ubuntu VM running my unifi controller, which is set to auto start. When I rebooted after the upgrading to 6.12, my browser wouldn't load the GUI, so I thought there was an issue, and hard power cycled (it turns out Firefox had "conveniently" redirected me to https). In any case, I'm thinking that the hard power cycle did something to the vdisk for the VM. In the VNC console, I see a bunch of fairly standard looking output, and then it starts complaining about waiting for local filesystem, and a repeated "madm: No arrays found in config file" error. And then it dumps me to a budybod initramfs terminal. In the VM, the command ls /dev/disk/by-id displays only the QEMU DVD drive. I've tried using ddrescue and qemu-img convert to repair the disk, but to no avail. I've attached a screenshot of end state of the terminal window of the VM logs. Any advice would be welcome. unifi logs.rtf

Hi, Last night I force shutdown Unraid instance because the web UI was unavailable (I have another bug where if my windows VM crashes it brings down the web UI). Typically when I have to do this, it comes right back up. However this time it is coming back up with a self-assigned IP address on 169.254.63.249. I've tried re-plugging the network cable, and switching to a new network cable with no success. The link and traffic lights are on for both the NIC and switch. I've tried the typical sudo dhclient – r but get an invalid command error. Additionally using ifconfig to try and set a static IP on br0 or eth0 doesn't seem to have any effect. I've done a few reboots expecting it to randomly come up, but no success. Does anyone have any clues what could be up? I've attached the diagnostics zip from this morning. Thanks! tower-diagnostics-20201201-0918.zip

Decided to go ahead and play it safe and get new cables. Updated diagnostic is attached. The data and parity drives are attached to the hotswap bays in my Corsair 800D; is it possible that the backplane in this is failing? It's pretty old. Thanks! tower-diagnostics-20200626-1822.zip

Here is the diagnostic export. Thanks, Andrew tower-diagnostics-20200620-2027.zip

Hi, several weeks ago I was having issues with high error rates and SMART failures on one of my data drives, as well as my parity drive. In order to fix the problem, I replaced them with two new HGST Ultrastar He10 8TB disks. The parity and data rebuilds went fine and I have been using the system since then. Suddenly again today I'm seeing errors on my parity disk, and the data drive is reporting as Unmountable: No file system. I've been trying to do an array shutdown to get into maintenance mode, but I'm not sure if the system is frozen, as it's been "stopping services" for about 20 minutes. I've attached the sys log for reference. Could this be a controller problem since it is the same disks that were replaced that now have the issues? What can I do to try to recover the array? Any advice is welcome. Thanks, Andrew tower-syslog-20200620-2204.zip

So the extended test passed with no errors, and the disk shows as "healthy" on the dashboard. On the main array screen, the disk has 257 reported errors. Additionally, I get an hourly warning when the array status notification comes in saying "Disk 2 - HITACHI_HUS724040ALE640_PAG3LDWT (sdf) - active 44 C (disk has read errors) [NOK]"

Hi, I've recently began receiving disk read errors on one of my array disks (4TB HGST HUS724040ALE640). The array has been pretty stable for a while, but within the last few days, I've been seeing unhealthy array notifications, with the errors reported on disk 2. SMART reports the disk is healthy, with some temperature anomalies (it gets pretty hot, up to 49C during parity checks). I've attached the latest smart report, and the syslog; I'm halfway through the extended self test. Do I need to replace this drive? Or is there something I can do to fix the issue? Thanks! tower-smart-20200408-0830.zip tower-syslog-20200408-1230.zip

Not noticably. It's a brand new corsair drive, so I hope it's not going this soon.

Hi, I've tried pretty much every port on the system, 2.0, 3.0, back panel, internal headers. Behavior seems pretty consistent between them.

Hi all, I've been running the Unraid trial on version 6.7.0-rc4 for a couple weeks now with no issues. I have a handful of Docker containers, an Ubuntu VM, and a Windows 10 VM on a passthrough disk. This afternoon I tried to setup a Fedora VM. The machine created fine, but it hung almost immediately after starting. Upon noticing that it was hung, I tried to force stop it in the GUI. That spun for a while, at which point I refreshed the browser only to find that the web gui service appeared to have crashed since it would not reload. At this point I decided I couldn't do anything but hard reset. Once I rebooted is when everything went weird. As I said above, the system has been stable for several weeks and has gone through its share of reboots (mostly clean through the UI, one power outage). This time however, rather than rebooting into Unraid, it rebooted directly in the Windows system on the passthrough drive (it's never done this before). I restarted a couple more times, and each time it went into the Windows system. I unplugged the SSD that Windows is installed on, and rebooted again. This time I get an error to insert a bootable disk. I'm finally able to get into the BIOS, at which point I see that the system isn't seeing the UNRAID drive at all. I checked the drive using my MacBook Pro, and it was able to read normally and everything seemed to be in the correct place. Over the course of several reboots, I noticed several things: The BIOS would occasionally recognize the flash drive, but more often it wouldn't. I moved the drive around to several ports, and it was a crap shoot on whether BIOS would recognize it. Even when BIOS wouldn't recognize it, Windows would boot, and Windows can see the flash drive. On the occasions that BIOS would recognize it, I was able to set it as the boot device. However on restart I would get the no boot device error. Going back into BIOS the device is no longer showing up. I created a new flash drive on my Mac, but that isn't recognized either. I was able to get Unraid to boot once (I had all of the SATA drives disconnected, not sure if that is just a coincidence), however it hung on a message saying "waiting for /dev/disk/by-label/UNRAID" for a while. It ultimately still booted, but didn't work. After shutting down to reconnect the SATA drives I get the boot device error. I also tried several BIOS fixes including restoring defaults, rolling back to earlier versions, and upgrading. If anyone has any ideas of additional troubleshooting steps to take I'd greatly appreciate it. - Steenbag Full Specs: Mobo: ASUS Sabertooth X79 RAM: 48GB DDR3 Proc: 2.7 Xeon E5-2697 12 core Array: 3x-4TB HGST Ultra Stars (2+1 Parity) Cache: 2x-256GB Samsung EVO SSDs Passthrough: 1TB Samsung PRO SSD