rennige

Hi, I have had a similar experience with high IO errors before. One was using a pci sata expansion card that started going bad and the other has been due to old sata cables. Based on what you have said, did you use new sata cables with the new build? Not 100% on the process, but from memory once the drive became disabled the only way to restore was to remove it from the array, then readd and rebuild it from parity. Not sure if others have a better idea.

Hi, Interested in setting up my own hosted text chat & voice call server for family communications. Had a look at options available and one called RIOT.IM fits what I am looking for. While I have a few dockers installed already they all came from the CA community, so no real experience in creating one from scratch. Hoping someone here has already blazed the trail or could point me in the right direction. From what I can see I need a docker that has both the RIOT.IM application as well as the Matrix components installed together. thanks, Nigel.

Ok.. So end result is that I presume my network setup is too complicated with VLANS, Bridging, etc. The way I managed to get it working was to remove the static IP address assignment from my unraid box. I then assigned a static lease on my router (ubiquiti usg). This also seems to be now working for the VM.

Thanks ... I know I can edit the hosts file, but since I have a few windows machines it is a little onerous. Also read the Windows Issues sticky and tried the SMB Master settings. Annoying as it was actually all working as expected a while back, then stopped after I installed and setup the bridge mode and ran a Windows VM.

Hi, Have an issue where I cannot seem to be able to resolve the hostname of my unraidserver from other Windows machines on my network. I can ping and access via IP address but not the defined servername "unraidserver". From what I can see it would appear that this issue is related to the "Bridge Mode", and maybe the Metric value under network settings, but just don't understand enough to resolve. Hoping someone here can help. Interesting is when I do a ping -a it comes back with a docker name that is using the bridge. Pinging unifi [192.168.1.8] with 32 bytes of data: Reply from 192.168.1.8: bytes=32 time=9ms TTL=63 Reply from 192.168.1.8: bytes=32 time=14ms TTL=63 Reply from 192.168.1.8: bytes=32 time<1ms TTL=63 root@unraidserver:/boot/config# more network.cfg # Generated settings: IFNAME[0]="br0" BRNAME[0]="br0" BRSTP[0]="no" BRFD[0]="0" BRNICS[0]="eth0" DESCRIPTION[0]="unraidserver" PROTOCOL[0]="ipv4" USE_DHCP[0]="no" IPADDR[0]="192.168.1.8" NETMASK[0]="255.255.255.0" GATEWAY[0]="192.168.1.1" METRIC[0]="10" DNS_SERVER1="192.168.1.1" USE_DHCP6[0]="yes" DHCP6_KEEPRESOLV="no" VLANID[0,1]="10" DESCRIPTION[0,1]="unrestricted" PROTOCOL[0,1]="ipv4" METRIC[0,1]="242" VLANID[0,2]="20" DESCRIPTION[0,2]="sharedservices" PROTOCOL[0,2]="ipv4" METRIC[0,2]="213" VLANS[0]="3" SYSNICS="1" root@unraidserver:/boot/config# hostname unraidserver root@unraidserver:/boot/config# hostname -i 127.0.0.1

Thanks. Done this. Checking the network and docker settings I can't see any reference to 10.1.20.23 anymore, however when I try to ping "unraidserver" it still resolves to that. Same after a reboot. Is this setting stuck somewhere else? On a side note, I have also set static IP addresses for all the docker containers - Is there a way to set hostnames for these as well?

Hi, Not sure if this is the right spot to post. Been having a lot of challenges (fun) getting vlan and docker configuration working. Finally close to getting it all done, when I notice that I can no longer reach my unraid server via its name "unraidserver". Only via IP address. I have the server sitting on the default management vlan with a static IP of 192.168.1.8 and VLAN 10 and VLAN 20 configured as well. When I try to ping the server using its name it resolves to 10.1.20.23 (which unraid says is the IPv4 address of VLAN 20) The ping times out. I also setup an recurring ping on the servername and watched while the unraid server restarted, part way through the reboot process I did start to get a response from 10.1.20.23 (but then it dropped out again as the server finished its boot). Ultimately I want to be able to have "unraidserver" resolve to 192.168.1.8. Is this possible?

Hi, I have been reading a bit around how to setup a Windows 10 VM under unraid for gaming purposes. This looks like a great advancement, however I haven't got my head around the best method to access the VM. From what I have read and seen, you can access the VM's via a)RDS, b)VNC, c)direct connection to the server. Currently I have unraid installed on a server in the cupboard. If I am to keep it there, then are only options a) and b) available? and what is the performance of this? thanks.

Thanks for the feedback. From what I can see the array configurations are the same in the backup syslog and the recovered sys log. Backup Syslog config: Oct 13 22:03:03 unraidserver emhttp: Device inventory: Oct 13 22:03:03 unraidserver emhttp: shcmd (4): udevadm settle Oct 13 22:03:03 unraidserver emhttp: WDC_WD30EFRX-68EUZN0_WD-WCC4N2ZHNRE4 (sdb) 2930266584 Oct 13 22:03:03 unraidserver emhttp: WDC_WD30EFRX-68EUZN0_WD-WCC4N5PF98K5 (sdc) 2930266584 Oct 13 22:03:03 unraidserver emhttp: WDC_WD20EARX-008FB0_WD-WMAZA9765616 (sdd) 1953514584 Oct 13 22:03:03 unraidserver emhttp: WDC_WD20EZRX-00DC0B0_WD-WMC302173631 (sde) 1953514584 Oct 13 22:03:03 unraidserver emhttp: WDC_WD20EARX-00PASB0_WD-WMAZA5273483 (sdf) 1953514584 Oct 13 22:03:03 unraidserver emhttp: WDC_WD20EARX-00PASB0_WD-WCAZA8429186 (sdg) 1953514584 Oct 13 22:03:03 unraidserver kernel: mdcmd (1): import 0 8,32 2930266532 WDC_WD30EFRX-68EUZN0_WD-WCC4N5PF98K5 Oct 13 22:03:03 unraidserver kernel: md: import disk0: [8,32] (sdc) WDC_WD30EFRX-68EUZN0_WD-WCC4N5PF98K5 size: 2930266532 Oct 13 22:03:03 unraidserver kernel: mdcmd (2): import 1 8,96 1953514552 WDC_WD20EARX-00PASB0_WD-WCAZA8429186 Oct 13 22:03:03 unraidserver kernel: md: import disk1: [8,96] (sdg) WDC_WD20EARX-00PASB0_WD-WCAZA8429186 size: 1953514552 Oct 13 22:03:03 unraidserver kernel: mdcmd (3): import 2 8,80 1953514552 WDC_WD20EARX-00PASB0_WD-WMAZA5273483 Oct 13 22:03:03 unraidserver kernel: md: import disk2: [8,80] (sdf) WDC_WD20EARX-00PASB0_WD-WMAZA5273483 size: 1953514552 Oct 13 22:03:03 unraidserver kernel: mdcmd (4): import 3 8,16 2930266532 WDC_WD30EFRX-68EUZN0_WD-WCC4N2ZHNRE4 Oct 13 22:03:03 unraidserver kernel: md: import disk3: [8,16] (sdb) WDC_WD30EFRX-68EUZN0_WD-WCC4N2ZHNRE4 size: 2930266532 Oct 13 22:03:03 unraidserver kernel: mdcmd (5): import 4 8,64 1953514552 WDC_WD20EZRX-00DC0B0_WD-WMC302173631 Oct 13 22:03:03 unraidserver kernel: md: import disk4: [8,64] (sde) WDC_WD20EZRX-00DC0B0_WD-WMC302173631 size: 1953514552 Oct 13 22:03:03 unraidserver kernel: mdcmd (6): import 5 0,0 Oct 13 22:03:03 unraidserver kernel: mdcmd (7): import 6 0,0 Oct 13 22:03:03 unraidserver kernel: mdcmd (: import 7 0,0 Recovered syslog config: Dec 22 14:05:01 unraidserver emhttp: Device inventory: Dec 22 14:05:01 unraidserver emhttp: shcmd (5): udevadm settle Dec 22 14:05:01 unraidserver emhttp: WDC_WD30EFRX-68EUZN0_WD-WCC4N2ZHNRE4 (sdb) 2930266584 Dec 22 14:05:01 unraidserver emhttp: WDC_WD30EFRX-68EUZN0_WD-WCC4N5PF98K5 (sdc) 2930266584 Dec 22 14:05:01 unraidserver emhttp: WDC_WD20EARX-008FB0_WD-WMAZA9765616 (sdd) 1953514584 Dec 22 14:05:01 unraidserver emhttp: WDC_WD20EZRX-00DC0B0_WD-WMC302173631 (sde) 1953514584 Dec 22 14:05:01 unraidserver emhttp: WDC_WD20EARX-00PASB0_WD-WMAZA5273483 (sdf) 1953514584 Dec 22 14:05:01 unraidserver emhttp: WDC_WD20EARX-00PASB0_WD-WCAZA8429186 (sdg) 1953514584 Dec 22 14:05:01 unraidserver emhttp: array slots: 24 Dec 22 14:05:01 unraidserver emhttp: cache slots: 1 Dec 22 14:05:01 unraidserver kernel: mdcmd (1): import 0 8,32 2930266532 WDC_WD30EFRX-68EUZN0_WD-WCC4N5PF98K5 Dec 22 14:05:01 unraidserver kernel: md: import disk0: [8,32] (sdc) WDC_WD30EFRX-68EUZN0_WD-WCC4N5PF98K5 size: 2930266532 Dec 22 14:05:01 unraidserver kernel: mdcmd (2): import 1 8,96 1953514552 WDC_WD20EARX-00PASB0_WD-WCAZA8429186 Dec 22 14:05:01 unraidserver kernel: md: import disk1: [8,96] (sdg) WDC_WD20EARX-00PASB0_WD-WCAZA8429186 size: 1953514552 Dec 22 14:05:01 unraidserver kernel: mdcmd (3): import 2 8,80 1953514552 WDC_WD20EARX-00PASB0_WD-WMAZA5273483 Dec 22 14:05:01 unraidserver kernel: md: import disk2: [8,80] (sdf) WDC_WD20EARX-00PASB0_WD-WMAZA5273483 size: 1953514552 Dec 22 14:05:01 unraidserver kernel: mdcmd (4): import 3 8,16 2930266532 WDC_WD30EFRX-68EUZN0_WD-WCC4N2ZHNRE4 Dec 22 14:05:01 unraidserver kernel: md: import disk3: [8,16] (sdb) WDC_WD30EFRX-68EUZN0_WD-WCC4N2ZHNRE4 size: 2930266532 Dec 22 14:05:01 unraidserver kernel: mdcmd (5): import 4 8,64 1953514552 WDC_WD20EZRX-00DC0B0_WD-WMC302173631 Dec 22 14:05:01 unraidserver kernel: md: import disk4: [8,64] (sde) WDC_WD20EZRX-00DC0B0_WD-WMC302173631 size: 1953514552 Dec 22 14:05:01 unraidserver kernel: mdcmd (6): import 5 0,0 Dec 22 14:05:01 unraidserver kernel: mdcmd (7): import 6 0,0 Dec 22 14:05:01 unraidserver kernel: mdcmd (: import 7 0,0 Would be worthwhile if someone could double check this for me. Also, is there a setting that I can change to stop the array from starting automatically? thanks.

Ok. Based on the linux kernel versions referenced in the syslog files I suspect: Current corrupted version was at least v6.1.3. Backup version was v6.0-rc1.

Hi, I have just returned from a holiday, and when I went to power my unraid server up it failed. There was an error reading the USB boot drive. Checking the boot drive on my windows PC couldn't see any files, and after a chkdsk it created a FOUND.000 folder with a lot of FileXXX.CHK files. Using a utility I found on the net I happened to be able to recover the last "syslog" file from when it last shut down. No errors reported. So now I have a USB file which is blank expect for 200+ CHK files... not very helpful. Other things of note: 1. I have a backup of the flashdrive from October where the syslog says: "Oct 13 22:02:52 unraidserver kernel: Linux version 4.0.2-unRAID (root@develop64) (gcc version 4.8.2 (GCC) ) #2 SMP PREEMPT Sat May 9 08:47:40 PDT 2015" 2. I suspect I have since upgraded to a newer version as the recovered syslog says: "Dec 22 14:04:45 unraidserver kernel: Linux version 4.1.7-unRAID (root@develop64) (gcc version 4.8.2 (GCC) ) #3 SMP PREEMPT Sun Sep 20 12:57:02 PDT 2015" 3. I have checked the drive assignments between the recovered syslog file and the back up and they are the same From what I can gather my options are: 1. Re-format the USB key and copy over the old backup: Not sure how this goes since I suspect the backup is from an older version of unraid 2. Recreate the whole USB from scratch using the drive assignments that I can see from the recovered syslog file. Any recommendations or other avenues available to me? thanks, Nigel.