wesker316

So I decided to update my server from 6.8.3 to the latest 6.9.2. The process seemed to work fine. When the server booted back on, the console was full of : Jul 10 21:12:39 Tower kernel: sas: ata11: end_device-5:0: dev error handler Jul 10 21:12:39 Tower kernel: ata11.00: qc timeout (cmd 0xec) Jul 10 21:12:39 Tower kernel: ata11.00: failed to IDENTIFY (I/O error, err_mask=0x4) Jul 10 21:12:39 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1415:mvs_I_T_nexus_reset for device[0]:rc= 0 Jul 10 21:12:39 Tower kernel: ata11.00: qc timeout (cmd 0xec) Jul 10 21:12:39 Tower kernel: ata11.00: failed to IDENTIFY (I/O error, err_mask=0x4) Jul 10 21:12:39 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1415:mvs_I_T_nexus_reset for device[0]:rc= 0 Jul 10 21:12:39 Tower kernel: ata11.00: qc timeout (cmd 0xec) Jul 10 21:12:39 Tower kernel: ata11.00: failed to IDENTIFY (I/O error, err_mask=0x4) After a LONG time, when I finally got into the web interface, 7 disks were missing. Im guessing they must be all connected to my Marvel Sata card? I know Marvel cards can cause problems but I never had any, for many many years. I reverted back to 6.8.3 and everything was back to normal. Any idea what's wrong? tower-diagnostics-20210710-2119.zip

I use this script to swicth VM from the desktop. I put the switchvm.sh file at the root of my flash drive, then, I use a .bat file to call putty : "C:\Program Files (x86)\PuTTY\plink.exe" -ssh -pw password root@tower "/boot/switchvm.sh VM-1 VM-2 > /dev/null &" You just need to change the user/password and the VM-1 VM-2 parameters switchvm.sh The script shuts down the first VM, waits for it to actually shut down, and the start the second VM.

My subscription to crashplan ends tomorrow, so yes, they gave me only 60 days to find a replacement

Try a different USB port for the link box, maybe a usb 2.0 port. Also, I wasn't able to get it working without passing a usb controller to my VM.

I had ghosting too when booting unraid in "OS GUI Mode" before stealing the gpu for a VM. I solved it by booting to the old console mode.

So I had to replace a failing disk. I first ran a parity check with 0 sync errors (and 6k read errors on the drive I'm replacing). Then I stopped the array, powered down, installed the new drive (old one was WD1.5TB green, new one is a WD2.0TB green) and powered back on. There was a disk missing message as expected, so I selected my new 2TB drive, checked the checkbox "yes I want to this" and started the data-rebuild. Since then I have not been able to access the webUI page. Unmenu is not responding either. But my array and my shares are accessible. Is there any way to tell what's going on? Usually my parity check takes about 15-16 hours, so I'm guessing the data-rebuild should take about the same amount of time? I'm using 5.0-rc12a and I checked the syslog using telnet but there are no messages since I started the data-rebuild