dlandon

Several things: - Be sure you have all browsers closed that may be accessing your unRAID webgui. A preclear still open in another computer? - Your flash has had some errors. Check it in a Windows computer and be sure there are no problems with the flash. /boot total 158352 drwxrwxrwx 3 root root 8192 Jan 12 20:23 EFI- -rwxrwxrwx 1 root root 8192 Dec 31 1979 FSCK0000.REC -rwxrwxrwx 1 root root 8192 Dec 31 1979 FSCK0001.REC -rwxrwxrwx 1 root root 8192 Dec 31 1979 FSCK0002.REC -rwxrwxrwx 1 root root 8192 Dec 31 1979 FSCK0003.REC -rwxrwxrwx 1 root root 8192 Dec 31 1979 FSCK0004.REC -rwxrwxrwx 1 root root 8192 Dec 31 1979 FSCK0005.REC -rwxrwxrwx 1 root root 8192 Dec 31 1979 FSCK0006.REC -rwxrwxrwx 1 root root 8192 Dec 31 1979 FSCK0007.REC -rwxrwxrwx 1 root root 8192 Dec 31 1979 FSCK0008.REC -rwxrwxrwx 1 root root 8192 Dec 31 1979 FSCK0009.REC -rwxrwxrwx 1 root root 434176 Dec 31 1979 FSCK0010.REC -rwxrwxrwx 1 root root 8192 Dec 31 1979 FSCK0011.REC

unRAID does not show in Windows 10 'Network'.

Will do.

No it doesn't. What version of unRAID are you using? If 6.4 then post in that forum. Look at this post for help:

For a while now I have not been able to see my unRAID server in the 'Network' with Windows 10 computers. If I set the SMB1.0/CIFS client on in the Windows 10 features, I can then see the unRAID server in Network and browse it. When I mount a remote SMB share with UD to my backup server, it will mount as SMB3, so I know the unRAID shares will mount as SMB3. What is it with Windows 10 that it won't see unRAID in the Network browse without SMB1.0/CIFS being turned on? EDIT: The Windows 10 setting for this is at Control Panel->Programs and Features->Turn Windows features on or off

Reboot your server.

Click on the mount point name when the share is not mounted and change the name. Press enter to accept.

What is your problem with the QNAP share?

Mounting a samba share shouldn't make any difference to the rsync command from local to local share mount. There is probably a permissions issue on the remote samba share that confuses rsync with regards to dates. Where is the remote samba share? What type of server? Could you rsync directly to that share?

There have been reports of a NIC hang when NIC offload is enabled. I ran into this issue myself. For some reason a while back I re-enabled NIC offload and then began to get NIC hang call traces in the later 6.4rc releases. I have two NICs bonded and used tlb (transmit load balance) . When I switched to alb (active load balance) and disabled NIC offload, the NIC hangs stopped. Just one more reason to keep the NIC offload disabled.

No. This is a viable solution. No problem if you do the copy correctly.

UD does not recognize the file system on the drives. Were the drives in a raid array?

Update to 2018.01.09b. It should format the disk now.

This is what I am trying to figure out. UD has been doing it this way without specifying the partition for a long time. Jan 9 11:21:50 BackupServer unassigned.devices: Format disk '/dev/sdg' with 'xfs' filesystem result: meta-data=/dev/sdg1 isize=512 agcount=4, agsize=19535700 blks = sectsz=512 attr=2, projid32bit=1 = crc=1 finobt=1, sparse=0, rmapbt=0, reflink=0 data = bsize=4096 blocks=78142798, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=38155, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 Jan 9 11:21:53 BackupServer unassigned.devices: Reloading disk '/dev/sdg' partition table. Jan 9 11:21:53 BackupServer kernel: sdg: sdg1 Jan 9 11:21:53 BackupServer unassigned.devices: Reload partition table result: /dev/sdg: re-reading partition table Ok. I stand corrected. The log message shows the drive and not the partition. It is actually formatting /dev/sdg1. This tells me what is wrong with the nvme format command now. It needs the partition as nvne0n1p1. Fix is now coming.

It looks like the USB device that you are using for the 6TB drives is not giving the proper information for UD to recognize the drives. If I am reading this right, you are using USB drives for parity? I wouldn't do that. Get an add in sata disk controller.

There's only one partition. That should work.

Go to a command line and execute the following command and post the results: /sbin/mkfs.xfs -f /dev/nvme0n1 This should show the reason it won't format.

Not only is this statement not totally true, it is rather annoying. Didn't you get the 'Format' button that you didn't see before and get farther along than you did before? The format was not successful, but we are farther along that before. Wouldn't it be more productive to let me know what happened differently than just give me the blanket it didn't work? I don't have a nvme disk and I will not invest in one just to test. I have to do the best I can looking at the logs and diagnostics.

You are showing me the stuff inside the Krusader docker. You need to get to an unRAID command line and show me the command: ls -l /dev/disk/by-id/

Update to the 2018.01.09a version. I made a change that may fix this issue.

I don't see anything that would be causing your USB device to not be seen. Try another USB port?

It looks like there is an issue with UD thinking the partition is /dev/nvme0n1p when it is really /dev/nvme0n1p1. That's why you are getting the blockdev errors. I don't know how this is happening, but I'll take a look at the code and see if I can see an issue. Without a disk to reproduce the issue, chances are I won't be able to find it.

Works fine for me. It looks like you may have an older installation of ownCloud already in the appdata. Be sure there is no ownCloud directory in appdata.

Are you running unRAID in a virtual environment?

UD thinks it has an Xfs file system. Post a screen shot of the disk in question after you click the + sign so we can see all the partitions. Also post diagnostics.