danith

I always thought it was weird to have both and finally decided to just check root@Dave-San:/mnt# ls cache/ disk1/ disk2/ disk3/ user/ user0/ root@Dave-San:/mnt# ls -al total 0 drwxr-xr-x 8 root root 160 Apr 14 19:51 ./ drwxrwxrwx 19 root root 400 Sep 28 2012 ../ drwxrwxrwx 4 nobody users 80 Apr 16 04:00 cache/ drwxrwxrwx 13 nobody users 304 Feb 26 22:34 disk1/ drwxrwxrwx 13 nobody users 304 Jun 24 2014 disk2/ drwxrwxrwx 3 nobody users 19 Apr 16 04:00 disk3/ drwxrwxrwx 1 nobody users 80 Apr 16 04:00 user/ drwxrwxrwx 1 nobody users 304 Apr 16 04:00 user0/ root@Dave-San:/mnt# mount -l tmpfs on /var/log type tmpfs (rw,size=128m,mode=0755) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) /dev/sda1 on /boot type vfat (rw,noatime,nodiratime,umask=0,shortname=mixed) [uNRAID] nfsd on /proc/fs/nfs type nfsd (rw) nfsd on /proc/fs/nfsd type nfsd (rw) /dev/md1 on /mnt/disk1 type reiserfs (rw,noatime,nodiratime,user_xattr,acl) /dev/md2 on /mnt/disk2 type reiserfs (rw,noatime,nodiratime,user_xattr,acl) /dev/md3 on /mnt/disk3 type xfs (rw,noatime,nodiratime) /dev/sdb1 on /mnt/cache type reiserfs (rw,noatime,nodiratime,user_xattr,acl) shfs on /mnt/user0 type fuse.shfs (rw,nosuid,nodev,noatime,allow_other) shfs on /mnt/user type fuse.shfs (rw,nosuid,nodev,noatime,allow_other) /mnt/disk1/docker/containers/docker on /var/lib/docker type btrfs (rw) root@Dave-San:/mnt# ls user0 Books/ Downloads/ Media/ Music/ TV/ backup/ docker/ movies/ vm_iso/ vm_store/ root@Dave-San:/mnt# ls user Books/ Downloads/ Media/ Music/ TV/ backup/ docker/ movies/ vm_iso/ vm_store/ root@Dave-San:/mnt# If user and user0 are both valid, what is the purpose of them as they seem to have the same directories

Ya, my UnRaid is on an ESXi box with an LSI flashed to IT mode passed through to it and I haven't had any issues. Although now with UnRaid 6 and Docker (and Xen) support I wonder if it would be better to run it bare metal

First totally new drive I've used so wanted to make sure about the raw_read stuff, I know the temps changed don't really matter (unless they go freakishly high). Thanks!

This is actually my first totally new disk for unRaid, and running pre-clear the below came up. Should I be worried? ========================================================================1.15 == invoked as: ./preclear_disk.sh /dev/sdf == ST3000DM001-1ER166 ZA500E03 == Disk /dev/sdf has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 1000448 Bytes == Last Cycle's Pre Read Time : 6:58:45 (119 MB/s) == Last Cycle's Zeroing time : 5:15:13 (158 MB/s) == Last Cycle's Post Read Time : 12:01:26 (69 MB/s) == Last Cycle's Total Time : 24:16:23 == == Total Elapsed Time 24:16:23 == == Disk Start Temperature: 25C == == Current Disk Temperature: 33C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 116 100 6 ok 109955480 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 68 75 45 near_thresh 32 Temperature_Celsius = 32 25 0 ok 32 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================