Albin

Members
  • Posts

    114
  • Joined

  • Last visited

Posts posted by Albin

  1. This may or may not help.  I recently upgraded from 6.8.3 to 6.9.1 and windows was extremely slow.  I did the following:

     

    Opened Control Panel > Programs and Features > Turn Windows features on or off (upper left corner) (or just open windows and search for Features and it should show)

    Unchecked everything under "Hyper-V"  (I Run Unraid with VMs, but I do not Run  Unaid with VMs that Run VMs (nested VMs) so I do not need this feature)

    Checked the box "Windows Subsystem for Linux" I think this is referred to as WSL  I also hear people refer to WSL2 but I currently do not see that as an option

    I do have other boxes that I have checked when creating the VM a long time ago, but I do not think they are related to this issue.

     

    I then rebooted and The slowness that I was having and CPU usage issues went away (very snappy now).  Hope this helps.

     

    Be sure to back up your VM image before attempting this.

     

     

     

     

    • Like 1
  2. Ability to assign Alias Names to USB Devices, to allow for easier mapping or allocating of devices in VMS.

     

    If you have 2 or 3 keyboards, 2 or 3 mice, CD rive, USB security dongles, USB card readers, it can get a little confusing when you are trying to assign devices to VMS especially if some of them are made by the same manufacture.  With the ability to assign aliases, this process would be a lot easier.  If this already exists, I am not aware of it.

  3. I uninstalled and reinstalled the file activity plugin.

    I also made sure that flash\config\plugins\file.activity did not exist at the time of reinstall.

    After re-installation, I started file activity, but I do not see any logs or results, even after hitting refresh.

    Status shows as running.  

     

    I did adjust my inotify value (from 524288 to 2524288) with tips and tweaks (thanks for the tips and tweaks plugin!)

     

    I can't figure out why do not get results with file activity.  

     

    I attached the diagnostics.  Thanks for any insight into this.

    tower2-diagnostics-20190717-1617.zip

  4. I am having the same issue.  

    I have a share called "Main" that I created years ago and have had no problems accessing it until today.  

    I attempted a reboot of my windows 10 machine, then the server and the win10 machine, and neither helped.

    I thought it was a SMB issue, but after some trouble shooting I realized that I could access some child folders and but not all child folders but I could not drill down from parent to child:

    I could access Main\Downloads\folder1 (I had to type it out or use an existing shortcut to the location)

    I could access Main\Downloads\folder2 (I had to type it out or use an existing shortcut to the location)

    I could not access Main\Downloads\folder3

           (this folder has files on the cache drive folder1 and folder2 do not have files on cache drive)

    I cannot access Main\Downloads (I am guess it is because of folder3 having files on the cache drive)

    I can Main\ (which I would have thought I would not be able to because of folder3 having files on the cache drive)

     

    I invoked mover to see what this would do, but it did not seem to help.

    I installed the "Tips and Tweaks" Plugin and changed my "Max Watches 'fs.inotify.max_user_watches'" from 524288 to 2524288

       (just added a 2 to the front of the default value, and will play around with this value over time, if need be.)

       see Still not enough inotify watches?

    As soon as I adjusted the inotify value, I could access folder1, folder2 and any other problem folder I had.

     

    Not sure if these will help but I attached the diagnostics file before and after the inotify changes.

     

    Unfortunately I invoked mover and also adjusted the inotify value with in minutes of each other, so I am not certain which of the changes allowed access to the offending folders.

     

    Thanks dlandon for the plugin Tips and Tweaks !

     

     

    tower2-diagnostics-20190717-1617.zip tower2-diagnostics-20190717-1454.zip

  5. Very Helpful Squid!  Thanks.

     

    I first tried newperms on a particular share, but it did not seem to fix an issue I was having with some old backups that I am trying to purge.  I ended up using 

     

     

    chmod -R 0777 /mnt/user/SHARENAME

     

    There seems to be files that this does not work on.  I have not completely narrowed it down, but it seems it is either extremely long file names, file names with special characters, or folders with special characters that the command is not working on (I thought it also had to do with files or folders that had spaces in them but that does not seem to be the case.  Is there a command that can be added as a catch all for those type conditions?  OR is there a way to strip special characters from file names, or truncate long file names?

  6. Hey,

     

    I am struggling to get this going.  

     

    Here is what I have:

    1. Unraid 6.3.5
    2. Apache Web Server to serve up the VirtualBox GUI interface instead of using commandline
    3. phpVirtualBox  GUI for virtualbox
    4. Virtualbox

    Unraid

    • go script edited to change unraid GUI to port 81
    • /usr/local/sbin/emhttp -p 81 &
    •  Rebooted

    Apache is installed to /mnt/user/appdata/apache with

    • Host port 1 set to 80
    • Host port 2 set to 443

    phpVirtuabox

    • phpvirtualbox-5.0-5
    • dwonloaded and unzipped to /mnt/cache/appdata/apache/www/phpvb
    • changed config.php-example to config.php
    • removed  # commenting out line: var $noAuth = true;  (not really needed)

    Virtualbox

    • Virtualbox v5.1.22 local version and installed version
    • virtualbox extension v5.1.22 local version and installed version
    • virtualbox guest additions local version and NOT showing an installed version
    • virtualbox plugin v2017.05.19e
    • VirtualbBox symbolic link set to: /boot/custom/vbox  (Two things I do not see this folder on unraid and do I need to change this location so it is not on the flash drive?)   (I created the folder "custom" and then added the folder "vbox" to get /boot/custom/vbox .... not sure if this is needed)
    • vboxwebsrv host IP: 127.0.0.1
    • vboxwebsrv Port 18083
    • Vboxwebserver log file location /boot/config/plugins/virtualbox/vbox   (verbose mode YES) (just checked this location on the flash drive and there is no folder "vbox" under  /boot/config/plugins/virtualbox)   (I added the folder "vbox"  ..... not sure if this is needed)   (after doing the below and watching the folder, nothing appeared in vbox....)

     

    Starting VirtualBox plugin:

    • Went to Dockers and Started Apache
    • Went to Plugins and Clicked "Start vboxwebsrv"
    • Opened a New Chrome Tab and went to http:\\tower/phpvb/  or IP Address/phpvb
    • By the way I have no VM's running plenty of Ram and space, and once I start the above process, I have to use terminal to do a "PowerDown"  this process locks up the gui screen and I can not gain access to any part of gui from any computer or from the screen connected to the tower.  

    At the very bottom of the Virtualbox plugin tab it says: "/opt/VirtualBox/VBoxManage setproperty websrvauthlibrary null vboxwebsrv service started"

     

    I saw the phpVirtualbox GUI but it was light (still loading) after waiting five minutes or so I refreshed and then the light outline of the GUI shows for a second and then goes away and does not come back and I get the message:

    "An error occurred communicating with your vboxwebsrv. No more requests will be sent by phpVirtualBox until the error is corrected and this page is refreshed. The details of this connection error should be displayed in a subsequent dialog box."

    and the message:

    "Could not connect to host (http://127.0.0.1:18083/)[code]

    Exception Object
    (
        [message:protected] => Could not connect to host (http://127.0.0.1:18083/)
        [string:Exception:private] => 
        [code:protected] => 64
        [file:protected] => /config/www/phpvb/endpoints/lib/vboxconnector.php
        [line:protected] => 220
        [trace:Exception:private] => Array
            (
                [0] => Array
                    (
                        [file] => /config/www/phpvb/endpoints/lib/vboxconnector.php
                        [line] => 5763
                        [function] => connect
                        [class] => vboxconnector
                        [type] => ->
                        [args] => Array
                            (
                            )
                    )
                [1] => Array
                    (
                        [file] => /config/www/phpvb/endpoints/lib/vboxconnector.php
                        [line] => 951
                        [function] => remote_vboxGroupDefinitionsGet
                        [class] => vboxconnector
                        [type] => ->
                        [args] => Array
                            (
                                [0] => 
                            )
                    )
                [2] => Array
                    (
                        [file] => /config/www/phpvb/endpoints/api.php
                        [line] => 316
                        [function] => __call
                        [class] => vboxconnector
                        [type] => ->
                        [args] => Array
                            (
                                [0] => vboxGroupDefinitionsGet
                                [1] => Array
                                    (
                                        [0] => 
                                        [1] => Array
                                            (
                                                [0] => Array
                                                    (
                                                        [data] => Array
                                                            (
                                                                [responseData] => Array
                                                                    (
                                                                    )
                                                            )
                                                        [errors] => Array
                                                            (
                                                            )
                                                        [persist] => Array
                                                            (
                                                            )
                                                        [messages] => Array
                                                            (
                                                            )
                                                    )
                                            )
                                    )
                            )
                    )
                [3] => Array
                    (
                        [file] => /config/www/phpvb/endpoints/api.php
                        [line] => 316
                        [function] => vboxGroupDefinitionsGet
                        [class] => vboxconnector
                        [type] => ->
                        [args] => Array
                            (
                                [0] => 
                                [1] => Array
                                    (
                                        [0] => Array
                                            (
                                                [data] => Array
                                                    (
                                                        [responseData] => Array
                                                            (
                                                            )
                                                    )
                                                [errors] => Array
                                                    (
                                                    )
                                                [persist] => Array
                                                    (
                                                    )
                                                [messages] => Array
                                                    (
                                                    )
                                            )
                                    )
                            )
                    )
            )
        [previous:Exception:private] => 
    )
    
    Location:http://127.0.0.1:18083/

    [/code]

     

     

    Here is the first several lines of my vboxwebsrv.log file:

     

    VirtualBox web service 5.1.22 r115126 linux.amd64 (Apr 28 2017 16:59:05) release log
    00:00:00.001416 main     Log opened 2017-08-27T11:56:00.979746000Z
    00:00:00.001419 main     Build Type: release
    00:00:00.001422 main     OS Product: Linux
    00:00:00.001423 main     OS Release: 4.9.30-unRAID
    00:00:00.001424 main     OS Version: #1 SMP PREEMPT Fri May 26 13:56:36 PDT 2017
    00:00:00.001467 main     DMI Product Name: CYPRESS11      
    00:00:00.001477 main     DMI Product Version: 1.0 
    00:00:00.001551 main     Host RAM: 128913MB (125.8GB) total, 107021MB (104.5GB) available
    00:00:00.001556 main     Executable: /opt/VirtualBox/vboxwebsrv
    00:00:00.001557 main     Process ID: 83003
    00:00:00.001558 main     Package type: LINUX_64BITS_GENERIC
    00:00:00.006024 main     IPC socket path: /tmp/.vbox-root-ipc/ipcd
    00:00:00.014135 main     Pumping COM event queue
    00:00:00.014159 main     Pumping COM event queue
    00:00:00.014250 Watchdog Watchdog thread started
    00:00:00.014262 Watchdog Watchdog: sleeping 5 seconds
    00:00:00.014963 SQPmp    Socket connection successful: host = 127.0.0.1, port = 18083, master socket = 12
    00:00:05.014420 Watchdog Watchdog: checking 0 websessions
    00:00:05.014458 Watchdog Statistics: 0 websessions, 0 references
    00:00:05.014474 Watchdog Watchdog: sleeping 5 seconds
    00:00:10.014603 Watchdog Watchdog: checking 0 websessions
    00:00:10.014656 Watchdog Watchdog: sleeping 5 seconds
    00:00:15.014332 main     Pumping COM event queue
    00:00:15.014747 Watchdog Watchdog: checking 0 websessions
    00:00:15.014772 Watchdog Watchdog: sleeping 5 seconds

    It just repeats from here on out  (checking and sleeping)

     

    I feel I am close, but I just can't get it working.  Any pointers would be greatly appreciated.

    I am looking forward to using this!

     

    EDIT:  The VirtualBox Plugin page finally gave me the option (buttons) to Restart or shutdown virtualbox (but it took forever)

     

    Thanks,

    Albin

  7. I cannot seem to get CrashPlan-Desktop to install.

     

    When I first added the container I was thinking that I needed to do volume mapping.  Then I saw ljm42 post

     

    I don't think there is a one-size-fits-all configuration for CrashPlan server or desktop.  I guess that is what makes troubleshooting the problem a bit different for everyone.  Some combination of the solutions mentioned is this thread will likely help most, but, there does not seem to be one config to rule them all. 

     

    My config is working fine without the disks mapping but needed the .ui_info fix:

     

    Remove the volume mapping for /config -> /mnt/cache/appdata/crashplan-desktop.  that conflicts with  --volumes-from CrashPlan

     

    After removing the container and the image I tried again.

     

    This time I I did not change anything after hitting add.  I left the volume mapping empty I left the port mapping the way it was (Container 3389 > host 3389) and I had left the --volumes-from CrashPlan in the Extra Parameters section.

     

    After hitting add I get the following:

    Command:

    root@localhost:# /usr/bin/docker run -d --name="CrashPlan-Desktop" --net="bridge" -e TZ="America/New_York" -p 3389:3389/tcp --volumes-from CrashPlan gfjardim/crashplan-desktop

    time="2015-07-30T17:01:23-04:00" level=fatal msg="Error response from daemon: Could not apply volumes of non-existent container "CrashPlan"."

     

    The command failed.

     

    I am not sure what I am doing wrong.  Are there unRaid settings that I need to change.

     

    I am running 6.0.1

    This is a fresh install of 6.0.1

    My docker image is at the root of my cache drive mnt/cache/docker.img

    I have my appdata on the cache drive as a cache only share mnt/usr/appdata

    I deleted any share that I created specifically for crash plan during my first attempts.

     

    Thanks for any advice.

     

    Albin

     

    Have you installed the CrashPlan docker (Not the Desktop version) You need both, CrashPlan is the service and the Desktop is just a conduit to configuring the CrashPlan docker.

     

    Thanks for pointing me in the correct direction.  I installed the crashplan service.  Looks like things are working now.  Thanks for your help!

  8. I cannot seem to get CrashPlan-Desktop to install.

     

    When I first added the container I was thinking that I needed to do volume mapping.  Then I saw ljm42 post

     

    I don't think there is a one-size-fits-all configuration for CrashPlan server or desktop.  I guess that is what makes troubleshooting the problem a bit different for everyone.  Some combination of the solutions mentioned is this thread will likely help most, but, there does not seem to be one config to rule them all. 

     

    My config is working fine without the disks mapping but needed the .ui_info fix:

     

    Remove the volume mapping for /config -> /mnt/cache/appdata/crashplan-desktop.  that conflicts with  --volumes-from CrashPlan

     

    After removing the container and the image I tried again.

     

    This time I I did not change anything after hitting add.  I left the volume mapping empty I left the port mapping the way it was (Container 3389 > host 3389) and I had left the --volumes-from CrashPlan in the Extra Parameters section.

     

    After hitting add I get the following:

    Command:

    root@localhost:# /usr/bin/docker run -d --name="CrashPlan-Desktop" --net="bridge" -e TZ="America/New_York" -p 3389:3389/tcp --volumes-from CrashPlan gfjardim/crashplan-desktop

    time="2015-07-30T17:01:23-04:00" level=fatal msg="Error response from daemon: Could not apply volumes of non-existent container "CrashPlan"."

     

    The command failed.

     

    I am not sure what I am doing wrong.  Are there unRaid settings that I need to change.

     

    I am running 6.0.1

    This is a fresh install of 6.0.1

    My docker image is at the root of my cache drive mnt/cache/docker.img

    I have my appdata on the cache drive as a cache only share mnt/usr/appdata

    I deleted any share that I created specifically for crash plan during my first attempts.

     

    Thanks for any advice.

     

    Albin

     

  9. I decided to do a fresh install of unRAID.  I figured I would move my data off the server and preclear all the drives.  I was hoping for some input as to which drives I should consider retiring.  I did preclear most of these at the same time.  Any input wold be greatly appreciated.

     

    Thanks,

    Albin

     

    I took at look at your smart reports and you can see my comments below.

     

    The drive sizes of the drives included are as follows:

    sda - 750G

    sdb - 500G

    sdd - 500G

    sde - 750G

    sdf - 1T

    sdh - 500G

     

    Honestly, expect the 1T drive, I'd recommend retiring the lot of them and replacing with a new 3T that can be had for less than $100. These are all getting rather old, and with so much larger drives available economically, it may be something to consider.

     

    But that is me. If these drive sizes are working for you, I do believe at least some of them have some life left.

     

    Many of the values of smart reports are not terribly useful, but the three I look at very closely are reallocated sectors, pending sectors, and temperature.

     

    reallocated sectors are small parts of the disk surface that the drive has decided are incapable of reliably storing data. Once reallocated, it will never be un-reallocated. Drives should have 0 of these. Occasionally a small number can develop and not increase in number. This is fine. But if the value is trickling upward, this is a sign the drive is failing.

     

    pending sectors are similar, except the jury is not out yet. They may get reallocated, or the drive may decide they are ok after all. Pending sectors are dangerous in that they can cause problems if rebuilding a failed disk. You didn't have any, but if you had, the recommendation would be to run more preclear cycles in an effort to get them to either reallocate or be marked good. Limbo is a bad place to be.

     

    temperature is the only one you have control of. I don't like to see temps go above 42 or 43, but preclearing is a pretty stressful activity, and you might expect that this will be the max temp the drive will see in your array. Your temps on some drives are approaching but just under temps that I would highlight, but I am not marking that as an issue. If we were seeing temps over 45, and certainly if they got to 50, I'd be much more concerned.

     

    The other attributes you are really looking at the "VALUE" column (on the preclear output you see it as "NEW_VAL") and comparing it to the "FAILURE_THRESHOLD" column. If the value is lower than the threshold, the drive will report "FAILING NOW" in the "STATUS" column. You don't have any of these, but they are bad. If the drive manufacturer, that is warrantying the drives, says it is failing, I never question it and get my data off it as fast as possible.

     

    If you seen "near_thresh" in the status column, that is worth looking at. Means the attribute is getting close to the threshold. But there are some attributes that a certain value is normal, and dropping even one lower is failure. So if you see a value of 100 (which is a typical normal good "value" for an attribute), and a threshold of 99, I interpret that to mean it should always be 100, and not to be concerned unless it drops to 99. But if I see a value of 22, and a threshold of 21, or a value of 1 and a threshold of 0, I would be much more concerned.

     

    Let me know if any questions on the information below:

     

    1 sda

    == ST3750330NS   9QK0D9WY
    == Disk /dev/sda has been successfully precleared
    == with a starting sector of 63
    ============================================================================
    ** Changed attributes in files: /tmp/smart_start_sda  /tmp/smart_finish_sda
                    ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
          Raw_Read_Error_Rate =   117     119            6        ok          120090706
             Spin_Retry_Count =   100     100           97        near_thresh 8
             End-to-End_Error =   100     100           99        near_thresh 0
      Airflow_Temperature_Cel =    60      64           45        near_thresh 40
          Temperature_Celsius =    40      36            0        ok          40
       Hardware_ECC_Recovered =    45      34            0        ok          120090706
    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.
    1 sector had been re-allocated before the start of the preclear.
    4 sectors are re-allocated at the end of the preclear,
        a change of 3 in the number of sectors re-allocated.
    =======================================================================
    

    This drive has picked up 3 reallocated sectors during the preclear. Although 4 reallocated sectors is not itself a problem, often INCREASES in the reallocated sectors is a sign the drive is failing. I'd recommend doing a couple more preclear cycles. If the numbers hold steady for three preclears in a row, you are probably fine. But if the numbers trickle up every preclear or two, and you can't get to three in a row with the same value even after 5 or 6 preclears, I'd retire the drive or use it for non-critical purposes (like storing backup data you already store on your array).

     

    2 sdb

    == ST3500630NS   5QG1HKD0
    == Disk /dev/sdb has been successfully precleared
    == with a starting sector of 63
    ============================================================================
    ** Changed attributes in files: /tmp/smart_start_sdb  /tmp/smart_finish_sdb
                    ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
             Spin_Retry_Count =   100     100           97        near_thresh 0
      Airflow_Temperature_Cel =    66      68           45        near_thresh 34
          Temperature_Celsius =    34      32            0        ok          34
       Hardware_ECC_Recovered =    57      71            0        ok          8218259
    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.
    1 sector had been re-allocated before the start of the preclear.
    1 sector is re-allocated at the end of the preclear,
        the number of sectors re-allocated did not change.
    =======================================================================

    This drive has 1 reallocated sector. This might have been like this for a very long time, or the 1 reallocation may have happened shortly before the preclear. Similar to sda above, I'd run a couple more preclears. If the 1 doesn't increase or you can get 3 preclears in a row where the number holds steady, keep it. Otherwise backup duty.

     

    3 sdd

    == ST3500630AS   9QG0GA2R
    == Disk /dev/sdd has been successfully precleared
    == with a starting sector of 63
    ============================================================================
    ** Changed attributes in files: /tmp/smart_start_sdd  /tmp/smart_finish_sdd
                    ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
             Spin_Retry_Count =   100     100           97        near_thresh 0
      Airflow_Temperature_Cel =    56      62           45        near_thresh 44
          Temperature_Celsius =    44      38            0        ok          44
       Hardware_ECC_Recovered =    53      65            0        ok          7699123
    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.
    114 sectors had been re-allocated before the start of the preclear.
    114 sectors are re-allocated at the end of the preclear,
        the number of sectors re-allocated did not change.
    =======================================================================
    

    Same as sdb. 114, although a bit large, its not a big deal if the reallocations don't increase. It is surprising (but good) that it went a whole preclear cycle with no new ones.

     

    4 sde

    == ST3750640NS   5QD0ELXR
    == Disk /dev/sde has been successfully precleared
    == with a starting sector of 63
    ============================================================================
    ** Changed attributes in files: /tmp/smart_start_sde  /tmp/smart_finish_sde
                    ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
             Spin_Retry_Count =   100     100           97        near_thresh 0
      Airflow_Temperature_Cel =    55      58           45        near_thresh 45
          Temperature_Celsius =    45      42            0        ok          45
       Hardware_ECC_Recovered =    62      65            0        ok          64838030
    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.
    =======================================================================
    

    No signs of failure.

     

    5 sdf

    == ST31000340AS   9QJ1VHF6
    == Disk /dev/sdf has been successfully precleared
    == with a starting sector of 63
    ============================================================================
    ** 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 =   118     110            6        ok          183656712
             Spin_Retry_Count =   100     100           97        near_thresh 0
             End-to-End_Error =   100     100           99        near_thresh 0
      Airflow_Temperature_Cel =    61      62           45        near_thresh 39
          Temperature_Celsius =    39      38            0        ok          39
       Hardware_ECC_Recovered =    50      36            0        ok          183656712
    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.
    =======================================================================
    

    No signs of failure.

     

    6 sdh

    == SAMSUNGHD502IJ   S1PZJDWQ669795
    == Disk /dev/sdh has been successfully precleared
    == with a starting sector of 63
    ============================================================================
    ** Changed attributes in files: /tmp/smart_start_sdh  /tmp/smart_finish_sdh
                    ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
             End-to-End_Error =   100     100           99        near_thresh 0
      Airflow_Temperature_Cel =    74      77            0        ok          26
          Temperature_Celsius =    74      76            0        ok          26
    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.
    =======================================================================

    No signs of failure.

     

    I ran 3 more cycles on sda sdb and sdd.  There were no changes to the sectors re-allocated for these drives.  (the numbers held steady)!  I attached results for cycle 3 and 4.

    1_sda_ST3750330NS___9QK0D9WY_Pass_3_and_4_no_new.txt

    3_sdd_ST3500630AS___9QG0GA2R_pass_3_and_4_no_new.txt

    2_sdb_ST3500630NS___5QG1HKD0_pass_3_and_4_no_new.txt

  10. Thanks Bjp999

     

    I appreciate you taking the time to reply.  The information you provided was very helpful. 

    I am going to run more preclears on the drives you suggested.  I will let you know what happens.

     

    Thanks,

     

    Albin

     

     

    I took at look at your smart reports and you can see my comments below.

     

    The drive sizes of the drives included are as follows:

    sda - 750G

    sdb - 500G

    sdd - 500G

    sde - 750G

    sdf - 1T

    sdh - 500G

     

    Honestly, expect the 1T drive, I'd recommend retiring the lot of them and replacing with a new 3T that can be had for less than $100. These are all getting rather old, and with so much larger drives available economically, it may be something to consider.

     

    But that is me. If these drive sizes are working for you, I do believe at least some of them have some life left.

     

    Many of the values of smart reports are not terribly useful, but the three I look at very closely are reallocated sectors, pending sectors, and temperature.

     

    reallocated sectors are small parts of the disk surface that the drive has decided are incapable of reliably storing data. Once reallocated, it will never be un-reallocated. Drives should have 0 of these. Occasionally a small number can develop and not increase in number. This is fine. But if the value is trickling upward, this is a sign the drive is failing.

     

    pending sectors are similar, except the jury is not out yet. They may get reallocated, or the drive may decide they are ok after all. Pending sectors are dangerous in that they can cause problems if rebuilding a failed disk. You didn't have any, but if you had, the recommendation would be to run more preclear cycles in an effort to get them to either reallocate or be marked good. Limbo is a bad place to be.

     

    temperature is the only one you have control of. I don't like to see temps go above 42 or 43, but preclearing is a pretty stressful activity, and you might expect that this will be the max temp the drive will see in your array. Your temps on some drives are approaching but just under temps that I would highlight, but I am not marking that as an issue. If we were seeing temps over 45, and certainly if they got to 50, I'd be much more concerned.

     

    The other attributes you are really looking at the "VALUE" column (on the preclear output you see it as "NEW_VAL") and comparing it to the "FAILURE_THRESHOLD" column. If the value is lower than the threshold, the drive will report "FAILING NOW" in the "STATUS" column. You don't have any of these, but they are bad. If the drive manufacturer, that is warrantying the drives, says it is failing, I never question it and get my data off it as fast as possible.

     

    If you seen "near_thresh" in the status column, that is worth looking at. Means the attribute is getting close to the threshold. But there are some attributes that a certain value is normal, and dropping even one lower is failure. So if you see a value of 100 (which is a typical normal good "value" for an attribute), and a threshold of 99, I interpret that to mean it should always be 100, and not to be concerned unless it drops to 99. But if I see a value of 22, and a threshold of 21, or a value of 1 and a threshold of 0, I would be much more concerned.

     

    Let me know if any questions on the information below:

     

    1 sda

    == ST3750330NS   9QK0D9WY
    == Disk /dev/sda has been successfully precleared
    == with a starting sector of 63
    ============================================================================
    ** Changed attributes in files: /tmp/smart_start_sda  /tmp/smart_finish_sda
                    ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
          Raw_Read_Error_Rate =   117     119            6        ok          120090706
             Spin_Retry_Count =   100     100           97        near_thresh 8
             End-to-End_Error =   100     100           99        near_thresh 0
      Airflow_Temperature_Cel =    60      64           45        near_thresh 40
          Temperature_Celsius =    40      36            0        ok          40
       Hardware_ECC_Recovered =    45      34            0        ok          120090706
    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.
    1 sector had been re-allocated before the start of the preclear.
    4 sectors are re-allocated at the end of the preclear,
        a change of 3 in the number of sectors re-allocated.
    =======================================================================
    

    This drive has picked up 3 reallocated sectors during the preclear. Although 4 reallocated sectors is not itself a problem, often INCREASES in the reallocated sectors is a sign the drive is failing. I'd recommend doing a couple more preclear cycles. If the numbers hold steady for three preclears in a row, you are probably fine. But if the numbers trickle up every preclear or two, and you can't get to three in a row with the same value even after 5 or 6 preclears, I'd retire the drive or use it for non-critical purposes (like storing backup data you already store on your array).

     

    2 sdb

    == ST3500630NS   5QG1HKD0
    == Disk /dev/sdb has been successfully precleared
    == with a starting sector of 63
    ============================================================================
    ** Changed attributes in files: /tmp/smart_start_sdb  /tmp/smart_finish_sdb
                    ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
             Spin_Retry_Count =   100     100           97        near_thresh 0
      Airflow_Temperature_Cel =    66      68           45        near_thresh 34
          Temperature_Celsius =    34      32            0        ok          34
       Hardware_ECC_Recovered =    57      71            0        ok          8218259
    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.
    1 sector had been re-allocated before the start of the preclear.
    1 sector is re-allocated at the end of the preclear,
        the number of sectors re-allocated did not change.
    =======================================================================

    This drive has 1 reallocated sector. This might have been like this for a very long time, or the 1 reallocation may have happened shortly before the preclear. Similar to sda above, I'd run a couple more preclears. If the 1 doesn't increase or you can get 3 preclears in a row where the number holds steady, keep it. Otherwise backup duty.

     

    3 sdd

    == ST3500630AS   9QG0GA2R
    == Disk /dev/sdd has been successfully precleared
    == with a starting sector of 63
    ============================================================================
    ** Changed attributes in files: /tmp/smart_start_sdd  /tmp/smart_finish_sdd
                    ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
             Spin_Retry_Count =   100     100           97        near_thresh 0
      Airflow_Temperature_Cel =    56      62           45        near_thresh 44
          Temperature_Celsius =    44      38            0        ok          44
       Hardware_ECC_Recovered =    53      65            0        ok          7699123
    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.
    114 sectors had been re-allocated before the start of the preclear.
    114 sectors are re-allocated at the end of the preclear,
        the number of sectors re-allocated did not change.
    =======================================================================
    

    Same as sdb. 114, although a bit large, its not a big deal if the reallocations don't increase. It is surprising (but good) that it went a whole preclear cycle with no new ones.

     

    4 sde

    == ST3750640NS   5QD0ELXR
    == Disk /dev/sde has been successfully precleared
    == with a starting sector of 63
    ============================================================================
    ** Changed attributes in files: /tmp/smart_start_sde  /tmp/smart_finish_sde
                    ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
             Spin_Retry_Count =   100     100           97        near_thresh 0
      Airflow_Temperature_Cel =    55      58           45        near_thresh 45
          Temperature_Celsius =    45      42            0        ok          45
       Hardware_ECC_Recovered =    62      65            0        ok          64838030
    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.
    =======================================================================
    

    No signs of failure.

     

    5 sdf

    == ST31000340AS   9QJ1VHF6
    == Disk /dev/sdf has been successfully precleared
    == with a starting sector of 63
    ============================================================================
    ** 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 =   118     110            6        ok          183656712
             Spin_Retry_Count =   100     100           97        near_thresh 0
             End-to-End_Error =   100     100           99        near_thresh 0
      Airflow_Temperature_Cel =    61      62           45        near_thresh 39
          Temperature_Celsius =    39      38            0        ok          39
       Hardware_ECC_Recovered =    50      36            0        ok          183656712
    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.
    =======================================================================
    

    No signs of failure.

     

    6 sdh

    == SAMSUNGHD502IJ   S1PZJDWQ669795
    == Disk /dev/sdh has been successfully precleared
    == with a starting sector of 63
    ============================================================================
    ** Changed attributes in files: /tmp/smart_start_sdh  /tmp/smart_finish_sdh
                    ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
             End-to-End_Error =   100     100           99        near_thresh 0
      Airflow_Temperature_Cel =    74      77            0        ok          26
          Temperature_Celsius =    74      76            0        ok          26
    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.
    =======================================================================

    No signs of failure.

  11. I decided to do a fresh install of unRAID.  I figured I would move my data off the server and preclear all the drives.  I was hoping for some input as to which drives I should consider retiring.  I did preclear most of these at the same time.  Any input wold be greatly appreciated.

     

    Thanks,

    Albin

     

    1 sda
    ================================================================== 1.15
    =                unRAID server Pre-Clear disk /dev/sda
    =               cycle 1 of 1, partition start on sector 63
    = Disk Pre-Clear-Read completed                                 DONE
    = Step 1 of 10 - Copying zeros to first 2048k bytes             DONE
    = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE
    = Step 3 of 10 - Disk is now cleared from MBR onward.           DONE
    = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4       DONE
    = Step 5 of 10 - Clearing MBR code area                         DONE
    = Step 6 of 10 - Setting MBR signature bytes                    DONE
    = Step 7 of 10 - Setting partition 1 to precleared state        DONE
    = Step 8 of 10 - Notifying kernel we changed the partitioning   DONE
    = Step 9 of 10 - Creating the /dev/disk/by* entries             DONE
    = Step 10 of 10 - Verifying if the MBR is cleared.              DONE
    = Disk Post-Clear-Read completed                                DONE
    
    Disk Temperature: 40C, Elapsed Time:  19:01:52
    ========================================================================1.15
    == ST3750330NS   9QK0D9WY
    == Disk /dev/sda has been successfully precleared
    == with a starting sector of 63
    ============================================================================
    ** Changed attributes in files: /tmp/smart_start_sda  /tmp/smart_finish_sda
                    ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
          Raw_Read_Error_Rate =   117     119            6        ok          120090706
             Spin_Retry_Count =   100     100           97        near_thresh 8
             End-to-End_Error =   100     100           99        near_thresh 0
      Airflow_Temperature_Cel =    60      64           45        near_thresh 40
          Temperature_Celsius =    40      36            0        ok          40
       Hardware_ECC_Recovered =    45      34            0        ok          120090706
    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.
    1 sector had been re-allocated before the start of the preclear.
    4 sectors are re-allocated at the end of the preclear,
        a change of 3 in the number of sectors re-allocated.
    =======================================================================END sda
    2 sdb
    ================================================================== 1.15
    =                unRAID server Pre-Clear disk /dev/sdb
    =               cycle 1 of 1, partition start on sector 63
    = Disk Pre-Clear-Read completed                                 DONE
    = Step 1 of 10 - Copying zeros to first 2048k bytes             DONE
    = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE
    = Step 3 of 10 - Disk is now cleared from MBR onward.           DONE
    = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4       DONE
    = Step 5 of 10 - Clearing MBR code area                         DONE
    = Step 6 of 10 - Setting MBR signature bytes                    DONE
    = Step 7 of 10 - Setting partition 1 to precleared state        DONE
    = Step 8 of 10 - Notifying kernel we changed the partitioning   DONE
    = Step 9 of 10 - Creating the /dev/disk/by* entries             DONE
    = Step 10 of 10 - Verifying if the MBR is cleared.              DONE
    = Disk Post-Clear-Read completed                                DONE
    Disk Temperature: 34C, Elapsed Time:  14:16:15
    ========================================================================1.15
    == ST3500630NS   5QG1HKD0
    == Disk /dev/sdb has been successfully precleared
    == with a starting sector of 63
    ============================================================================
    ** Changed attributes in files: /tmp/smart_start_sdb  /tmp/smart_finish_sdb
                    ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
             Spin_Retry_Count =   100     100           97        near_thresh 0
      Airflow_Temperature_Cel =    66      68           45        near_thresh 34
          Temperature_Celsius =    34      32            0        ok          34
       Hardware_ECC_Recovered =    57      71            0        ok          8218259
    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.
    1 sector had been re-allocated before the start of the preclear.
    1 sector is re-allocated at the end of the preclear,
        the number of sectors re-allocated did not change.
    =======================================================================END sdb
    3 sdd
    ================================================================== 1.15
    =                unRAID server Pre-Clear disk /dev/sdd
    =               cycle 1 of 1, partition start on sector 63
    = Disk Pre-Clear-Read completed                                 DONE
    = Step 1 of 10 - Copying zeros to first 2048k bytes             DONE
    = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE
    = Step 3 of 10 - Disk is now cleared from MBR onward.           DONE
    = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4       DONE
    = Step 5 of 10 - Clearing MBR code area                         DONE
    = Step 6 of 10 - Setting MBR signature bytes                    DONE
    = Step 7 of 10 - Setting partition 1 to precleared state        DONE
    = Step 8 of 10 - Notifying kernel we changed the partitioning   DONE
    = Step 9 of 10 - Creating the /dev/disk/by* entries             DONE
    = Step 10 of 10 - Verifying if the MBR is cleared.              DONE
    = Disk Post-Clear-Read completed                                DONE
    Disk Temperature: 44C, Elapsed Time:  14:09:42
    ========================================================================1.15
    == ST3500630AS   9QG0GA2R
    == Disk /dev/sdd has been successfully precleared
    == with a starting sector of 63
    ============================================================================
    ** Changed attributes in files: /tmp/smart_start_sdd  /tmp/smart_finish_sdd
                    ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
             Spin_Retry_Count =   100     100           97        near_thresh 0
      Airflow_Temperature_Cel =    56      62           45        near_thresh 44
          Temperature_Celsius =    44      38            0        ok          44
       Hardware_ECC_Recovered =    53      65            0        ok          7699123
    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.
    114 sectors had been re-allocated before the start of the preclear.
    114 sectors are re-allocated at the end of the preclear,
        the number of sectors re-allocated did not change.
    =======================================================================END sdd
    4 sde
    ================================================================== 1.15
    =                unRAID server Pre-Clear disk /dev/sde
    =               cycle 1 of 1, partition start on sector 63
    = Disk Pre-Clear-Read completed                                 DONE
    = Step 1 of 10 - Copying zeros to first 2048k bytes             DONE
    = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE
    = Step 3 of 10 - Disk is now cleared from MBR onward.           DONE
    = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4       DONE
    = Step 5 of 10 - Clearing MBR code area                         DONE
    = Step 6 of 10 - Setting MBR signature bytes                    DONE
    = Step 7 of 10 - Setting partition 1 to precleared state        DONE
    = Step 8 of 10 - Notifying kernel we changed the partitioning   DONE
    = Step 9 of 10 - Creating the /dev/disk/by* entries             DONE
    = Step 10 of 10 - Verifying if the MBR is cleared.              DONE
    = Disk Post-Clear-Read completed                                DONE
    Disk Temperature: 45C, Elapsed Time:  18:32:23
    ========================================================================1.15
    == ST3750640NS   5QD0ELXR
    == Disk /dev/sde has been successfully precleared
    == with a starting sector of 63
    ============================================================================
    ** Changed attributes in files: /tmp/smart_start_sde  /tmp/smart_finish_sde
                    ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
             Spin_Retry_Count =   100     100           97        near_thresh 0
      Airflow_Temperature_Cel =    55      58           45        near_thresh 45
          Temperature_Celsius =    45      42            0        ok          45
       Hardware_ECC_Recovered =    62      65            0        ok          64838030
    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.
    =======================================================================END sde
    5 sdf
    ================================================================== 1.15
    =                unRAID server Pre-Clear disk /dev/sdf
    =               cycle 1 of 1, partition start on sector 63
    = Disk Pre-Clear-Read completed                                 DONE
    = Step 1 of 10 - Copying zeros to first 2048k bytes             DONE
    = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE
    = Step 3 of 10 - Disk is now cleared from MBR onward.           DONE
    = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4       DONE
    = Step 5 of 10 - Clearing MBR code area                         DONE
    = Step 6 of 10 - Setting MBR signature bytes                    DONE
    = Step 7 of 10 - Setting partition 1 to precleared state        DONE
    = Step 8 of 10 - Notifying kernel we changed the partitioning   DONE
    = Step 9 of 10 - Creating the /dev/disk/by* entries             DONE
    = Step 10 of 10 - Verifying if the MBR is cleared.              DONE
    = Disk Post-Clear-Read completed                                DONE
    Disk Temperature: 39C, Elapsed Time:  22:37:55
    ========================================================================1.15
    == ST31000340AS   9QJ1VHF6
    == Disk /dev/sdf has been successfully precleared
    == with a starting sector of 63
    ============================================================================
    ** 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 =   118     110            6        ok          183656712
             Spin_Retry_Count =   100     100           97        near_thresh 0
             End-to-End_Error =   100     100           99        near_thresh 0
      Airflow_Temperature_Cel =    61      62           45        near_thresh 39
          Temperature_Celsius =    39      38            0        ok          39
       Hardware_ECC_Recovered =    50      36            0        ok          183656712
    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.
    =======================================================================END sdf
    6 sdh
    ================================================================== 1.15
    =                unRAID server Pre-Clear disk /dev/sdh
    =               cycle 1 of 1, partition start on sector 63
    = Disk Pre-Clear-Read completed                                 DONE
    = Step 1 of 10 - Copying zeros to first 2048k bytes             DONE
    = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE
    = Step 3 of 10 - Disk is now cleared from MBR onward.           DONE
    = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4       DONE
    = Step 5 of 10 - Clearing MBR code area                         DONE
    = Step 6 of 10 - Setting MBR signature bytes                    DONE
    = Step 7 of 10 - Setting partition 1 to precleared state        DONE
    = Step 8 of 10 - Notifying kernel we changed the partitioning   DONE
    = Step 9 of 10 - Creating the /dev/disk/by* entries             DONE
    = Step 10 of 10 - Verifying if the MBR is cleared.              DONE
    = Disk Post-Clear-Read completed                                DONE
    Disk Temperature: 26C, Elapsed Time:  16:30:41
    ========================================================================1.15
    == SAMSUNGHD502IJ   S1PZJDWQ669795
    == Disk /dev/sdh has been successfully precleared
    == with a starting sector of 63
    ============================================================================
    ** Changed attributes in files: /tmp/smart_start_sdh  /tmp/smart_finish_sdh
                    ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
             End-to-End_Error =   100     100           99        near_thresh 0
      Airflow_Temperature_Cel =    74      77            0        ok          26
          Temperature_Celsius =    74      76            0        ok          26
    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.
    =======================================================================END sdh

    drives_1_thru_6_.txt

  12. I've seen some reports that a VPN could mess it up or that you may also need to manually specify a DNS address in network settings.

     

    Very Help! Thanks.  I just upgraded from 5.0 to 6.0.1 and tried to install the Community Applications Plugin and got the following:

     

    plugin: installing: https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg
    plugin: downloading https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg
    plugin: downloading: https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg ... done
    
    Warning: simplexml_load_file(): /tmp/plugins/community.applications.plg:1: parser error : Document is empty in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193
    
    Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193
    
    Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193
    
    Warning: simplexml_load_file(): /tmp/plugins/community.applications.plg:1: parser error : Start tag expected, '<' not found in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193
    
    Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193
    
    Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193
    plugin: xml parse error

     

    I then stopped the array then went to settings>system settings>network settings and changed my DNS1 to my gateway IP address which is 192.168.2.2  (this is what I had in my DNS settings for my unraid 5.0 box) .  After saving the settings and starting the array, I attempted to install the plugin and I had no issues with the installation process.

     

    I was not sure if my gateway IP address is or would be the best setting for this.  (I am guess my gateway router redirects dns lookups to the DNS1 and DNS2 records that it has on file.)  I wanted to try Googles Public DNS Lookup and compare the results of the plugin installation log.  So to do this I uninstalled the plugin first.

     

    Then I went to settings>system settings>network settings and changed my DNS settings to Googles Public DNS.  So for DNS1 I set it to 8.8.8.8 and DNS2 I set it to 8.8.4.4

    After saving the settings and starting the array, I attempted to install the plugin and I had no issues with the installation process.  There was no difference in speed or in the log between the two plugin installations.

     

    Log from Installation was the same for both network settings:

    plugin: installing: https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg
    plugin: downloading https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg
    plugin: downloading: https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg ... done
    plugin: downloading: https://raw.github.com/Squidly271/community.applications/master/archive/community.applications-2015.07.08.txz ... done
    
    +==============================================================================
    | Installing new package /boot/config/plugins/community.applications/community.applications-2015.07.08.txz
    +==============================================================================
    
    Verifying package community.applications-2015.07.08.txz.
    Installing package community.applications-2015.07.08.txz:
    PACKAGE DESCRIPTION:
    Package community.applications-2015.07.08.txz installed.
    
    
    
    ----------------------------------------------------
    community.applications has been installed.
    Copyright 2015, Squid, gfjardim, bergware
    Version: 2015.07.08
    ----------------------------------------------------
    
    plugin: installed
    

     

    I am not sure it matters but, I do have a VPN for a remote office, but the VPN internet traffic is not routed over the VPN.  The gateway which is also the hardware that has my VPN configurations, uses google public dns records also.

     

    At some point along the way (in the past) I changed from using my gateway ip address to using my isp DNS servers settings for DNS1 and DNS2.  I am guessing their lookup was having issues or something.  I am going to leave it set to 8.8.8.8 and 8.8.4.4 and leave DNS3 empty unless someone else has a better suggestion?

     

    Thanks again,

     

    Albin


  13. I am attempting to use Intel's CPU Feature list to narrow down the list of CPUs that would be most optimal for UNRAID 6 and unRAID 6.0-beta15 and potentially future releases. 

     

    Some of the listed Features are confusing.  I am not sure if they are needed or need to be avoided for an unraid build.  My goal is take advantage of UnRaids support of KVM QEMU and OVMF/UEFI.

    I see some sites talk about needing to disable TXT or Trusted Execution Technology.  In the Intel features selection criteria you can select YES or No for TXT.  This is just one of the features that I really do not know if I need or want to avoid.

     

    Also it is not clear to me if, YES for some of these give an indication the CPU has that feature, or that one can disable that option, or does it mean it has it and you cannot disable it.  For the time that I have spent trying to figure things out, it appears that having the ability to disable certain things, is important to the success of ones unraid build.

     

    Description of TXT

    • Intel® Trusted Execution Technology for safer computing is a versatile set of hardware extensions to Intel® processors and chipsets that enhance the digital office platform with security capabilities such as measured launch and protected execution. It enables an environment where applications can run within their own space, protected from all other software on the system.

     

    I also see some chips that have Execute Disable Bit.  This does not seem to be a filter option but is listed under the cpu description section Intel® Platform Protection Technology

     

    Execute Disable Bit

    • is a hardware-based security feature that can reduce exposure to viruses and malicious-code attacks and prevent harmful software from executing and propagating on the server or network.
       

    There are other options that can be selected but it is unclear to me what items should be set to YES, which ones should be set to NO, and which ones don't matter.

     

    • Technologies
    • Intel Turbo Boost Technology (options are 1, 2, NO)
    • Intel Hyper-Threading Technology (YES or NO)
    • Intel Wireless Display (YES or NO)
    • Intel Quick Sync Video (YES or NO)
    • Intel Virtualization Technology (VT-x) (YES or NO)
    • Intel VT-x with Extended Page Tables (EPT) (YES or NO)
    • Intel Virtualization Technology for Directed I/O (VT-d) (I have this set to YES)
    • AES New Instructions (YES or NO)
    • Enhanced Intel SpeedStep® Technology (YES or NO)
    • Intel Demand Based Switching (YES or NO)
    • Trusted Execution Technology (also called TXT) (YES or NO)
    • Intel 64 (I have this set to YES)
    • Intel vPro Technology (YES or NO)

     

    I am guessing VT-d which has IOMMU DMA remapping would be most ideal.

     

    Should I select YES for any of the other features to get a list of the most compatible CPUs?

    Should I select NO for some to be sure to avoid them?

     

    Here is my understanding of what one may want in a CPU to get the most out of visualization (I understand that some may have specific wants based on their current build, but this is specific to virtualization, and unless there is a strong recommendation it is not for filtering socket type, speed, cache size, core count, ....:

     

    • VT-d with IOMMU support (I am not sure if VT-d that do not support IOMMU, but definitely want IOMMU)
    • needs to support OVMF/UEFI  (I am not sure if this is somehow the same as IOMMU or is an additional feature needed)
    • Not sure if there should be other must or must nots for a CPU

     

     

    If anyone has used Intel's Feature filter to find the best cpu, and give me some pointers I would greatly appreciate it.

    A Good, Better, Best list of CPU's would be awesome. 

     

    Thanks,

     

    Albin

  14. I went through the following steps (in order):

    [*]re-ran the "New Permissions" (waited for it to complete)

    [*]stopped the dropbox plugin

    [*]powered down Unraid

    [*]brought up a dos prompt and ran "net use * /delete"

    [*]powered down windows

    [*]powered up windows

    [*]powered up Unraid

    [*]started the array and dropbox

    [*]browsed to \\tower2\Dropbox

    [*]entered my login credentials

     

    and NOW I have read / write access to \\tower2\Dropbox

     

    Just out of curiosity, at a telnet prompt I ran

    ls -la /mnt/disk1/Dropbox
    ls -la /mnt/disk1/.dropbox

     

    total 232

    drwxrwxrwx  7 nobody users    248      2013-02-08 13:20 ./

    drwxrwxrwx 11 nobody users    312      2013-02-07 14:25 ../

    -rw-rw-rw-    1 nobody users    29        2013-02-08 13:19 .dropbox

    drwxrwxrwx  2 nobody users    48        2013-02-07 14:28 .dropbox.cache/

    -rw-rw-rw-    1 nobody users    230783 2011-07-20 08:44 Getting\ Started1.pdf

    drwxrwxrwx  4 nobody users    264      2013-02-07 14:28 NBCC/

    drwxrwxrwx  2 nobody users    72        2011-07-25 14:47 NBCC\ Video/

    drwxrwxrwx  3 nobody users    128      2013-02-07 14:27 Photos/

    drwxrwxrwx  2 nobody users    264      2013-02-07 14:27 Public/

     

    total 416

    drwx------      3 nobody users    464    2013-02-08 13:21 ./

    drwxrwxrwx 11 nobody users    312    2013-02-07 14:25 ../

    srw-------        1 nobody users      0      2013-02-08 13:19 command_socket=

    -rw-rw-rw-    1 nobody users  3072  2013-02-07 14:26 config.db

    -rw-rw-rw-    1 nobody users  12288  2013-02-08 13:21 config.dbx

    -rw-rw-rw-    1 nobody users  6144  2013-02-07 14:27 deleted.dbx

    -rw-rw-rw-    1 nobody users      4      2013-02-08 13:19 dropbox.pid

    -rw-rw-rw-    1 nobody users  41984  2013-02-08 13:21 filecache.dbx

    -rw-r--r--        1 nobody users    77    2013-02-08 13:19 host.db

    -rw-rw-rw-    1 nobody users    209    2013-02-08 13:19 host.dbx

    -rw-rw-rw-    1 nobody users    81    2013-02-07 14:26 hostkeys

    srw-------      1 nobody users      0      2013-02-08 13:19 iface_socket=

    drwxrwxrwx  2 nobody users    48    2013-02-07 14:26 l/

    -rw-rw-rw-    1 nobody users  13312  2013-02-08 13:21 photo.dbx

    -rw-rw-rw-    1 nobody users 316416 2013-02-07 14:28 sigstore.dbx

    -rw-r--r--      1 nobody users    200    2013-02-08 13:19 unlink.db

     

    The only change I see is the renaming of "Started.pdf" to "Started1.pdf"

    (that was to verify read write access)

     

    Just thinking out loud here.... if the above is the same as before running "New Permissions" why do I now have read / write access to \\tower2\Dropbox , where as before I did not.

     

    So it may be fixed, but I am not sure what part of the above actually fixed it.

  15. Location of the data files: /mnt/disk1/Dropbox

    Location of Database Directory: /mnt/disk1/.dropbox

     

    Albin, I'm trying to replicate the problem here.  Can you send me the output of ...

     

    I'm not completely sure where the issue is yet, but I suspect it's permission based.  Did some tests here and noticed that on initial dropbox plugin installation but prior to starting dropbox, the above locations have these permissions:

     

    This is not the plugin.  This is dropbox itself changing the permissions for .dropbox directory.  I need to test further, but it could be useful to see what your permissions are for these directories.

     

     

    Regards,

    overbyrn

     

     

    I hope the below is what you were looking for.  I first got the info when dropbox was idle, then I stopped dropbox and got the other info.  (I am not showing them in the order executed, rather in an order to help for visual comparison.  Does not look like there is any difference. 

     

    Dropbox Status = IDLE:

    ls -la /mnt/disk1/Dropbox

    total 232

    drwx------      7 nobody users    248    2013-02-07 15:16 ./

    drwxrwxrwx 11 nobody users    312    2013-02-07 14:25 ../

    -rw-r--r--        1 nobody users    29    2013-02-07 15:16 .dropbox

    drwxr-xr-x      2 nobody users    48    2013-02-07 14:28 .dropbox.cache/

    -rw-r--r--        1 nobody users 230783 2011-07-20 08:44 Getting\ Started.pdf

    drwxr-xr-x      4 nobody users    264    2013-02-07 14:28 NBCC/

    drwxr-xr-x      2 nobody users    72    2011-07-25 14:47 NBCC\ Video/

    drwxr-xr-x      3 nobody users    128    2013-02-07 14:27 Photos/

    drwxr-xr-x      2 nobody users    264    2013-02-07 14:27 Public/

     

    Dropbox Status = Dropbox isn't running!

    ls -la /mnt/disk1/Dropbox

    total 232

    drwx------      7 nobody users    248    2013-02-07 15:16 ./

    drwxrwxrwx 11 nobody users    312    2013-02-07 14:25 ../

    -rw-r--r--        1 nobody users    29    2013-02-07 15:16 .dropbox

    drwxr-xr-x      2 nobody users    48    2013-02-07 14:28 .dropbox.cache/

    -rw-r--r--        1 nobody users 230783 2011-07-20 08:44 Getting\ Started.pdf

    drwxr-xr-x      4 nobody users    264    2013-02-07 14:28 NBCC/

    drwxr-xr-x      2 nobody users    72    2011-07-25 14:47 NBCC\ Video/

    drwxr-xr-x      3 nobody users    128    2013-02-07 14:27 Photos/

    drwxr-xr-x      2 nobody users    264    2013-02-07 14:27 Public/

     

    Dropbox Status = IDLE:

    ls -la /mnt/disk1/.dropbox

    total 416

    drwx------      3 nobody users    464  2013-02-07 15:16 ./

    drwxrwxrwx 11 nobody users    312  2013-02-07 14:25 ../

    srw-------        1 nobody users      0    2013-02-07 15:16 command_socket=

    -rw-------        1 nobody users  3072  2013-02-07 14:26 config.db

    -rw-------        1 nobody users  12288 2013-02-07 15:16 config.dbx

    -rw-r--r--        1 nobody users  6144  2013-02-07 14:27 deleted.dbx

    -rw-r--r--        1 nobody users      4    2013-02-07 15:16 dropbox.pid

    -rw-r--r--        1 nobody users  41984 2013-02-07 15:16 filecache.dbx

    -rw-r--r--        1 nobody users    77    2013-02-07 15:16 host.db

    -rw-r--r--        1 nobody users    209  2013-02-07 15:16 host.dbx

    -rw-r--r--        1 nobody users    81    2013-02-07 14:26 hostkeys

    srw-------      1 nobody users      0    2013-02-07 15:16 iface_socket=

    drwxr-xr-x    2 nobody users    48    2013-02-07 14:26 l/

    -rw-r--r--      1 nobody users  13312  2013-02-07 15:16 photo.dbx

    -rw-r--r--      1 nobody users 316416 2013-02-07 14:28 sigstore.dbx

    -rw-r--r--      1 nobody users    200    2013-02-07 15:16 unlink.db

     

     

    Dropbox Status = Dropbox isn't running!

    ls -la /mnt/disk1/.dropbox

    total 416

    drwx------      3 nobody users    464  2013-02-07 15:16 ./

    drwxrwxrwx 11 nobody users    312  2013-02-07 14:25 ../

    srw-------        1 nobody users      0    2013-02-07 15:16 command_socket=

    -rw-------        1 nobody users  3072  2013-02-07 14:26 config.db

    -rw-------        1 nobody users  12288 2013-02-07 15:16 config.dbx

    -rw-r--r--        1 nobody users  6144  2013-02-07 14:27 deleted.dbx

    -rw-r--r--        1 nobody users      4    2013-02-07 15:16 dropbox.pid

    -rw-r--r--        1 nobody users  41984 2013-02-07 15:16 filecache.dbx

    -rw-r--r--        1 nobody users    77    2013-02-07 15:16 host.db

    -rw-r--r--        1 nobody users    209  2013-02-07 15:16 host.dbx

    -rw-r--r--        1 nobody users    81    2013-02-07 14:26 hostkeys

    srw-------      1 nobody users      0      2013-02-07 15:16 iface_socket=

    drwxr-xr-x    2 nobody users    48    2013-02-07 14:26 l/

    -rw-r--r--      1 nobody users  13312  2013-02-07 15:16 photo.dbx

    -rw-r--r--      1 nobody users 316416 2013-02-07 14:28 sigstore.dbx

    -rw-r--r--      1 nobody users    200    2013-02-07 15:16 unlink.db

     

    Let me know if you need anything more, and thanks for looking into it.

     

    Albin

  16. Running 5.0-rc11

     

    I can't access \\tower2\Dropbox from windows vista

    I have my share settings set to Private, and one user with read/write permissions

    (I am getting access denied)

    I have all my shares set up the same way and can access all of my shares fine except for Dropbox

     

    I just idownloaded dropbox-0.4-i468-1atv.plg and placed it in my flash\config\plugins

     

    Everything seems to be running fine:

     

    root@Tower2:~# /etc/rc.d/rc.dropbox status

    Idle

     

    sudo -u nobody HOME=/usr/local/dropbox /usr/local/sbin/dropbox.py start

    Result = needed link

     

    Following the link "this computer is already linked"

     

    Location of the data files: /mnt/disk1/Dropbox

    Location of Database Directory: /mnt/disk1/.dropbox

     

    Python version

    python --version

    Python 2.6.6

     

    One thing I may have done wrong was, I did not create the share called Dropbox, the installation process created the share.  should I have created the share myself prior to installing the dropbox plugin?

     

    I did have to set the share to private and adjust the users from no access to read/write.

     

    I rebooted both windows and unraid at the same time, which did not help.

     

    If I go to http://tower2/Shares/Browse?dir=/mnt/user/Dropbox

    I can see that Dropbox / cloud has sync'ed with /mnt/user/Dropbox

     

    I am attaching the installation prompts and a syslog

     

    Do I need to run new permissions again?

     

    Thanks for any help on gaining read/write access to \\tower2\Dropbox

     

    Albin

     

    syslog_after_dropbox_plugin1.txt

    drop_box_install_prompts1.txt

  17. Both 4.7 logs do not detect the link. It's as if there's no Ethernet cable connected to the eth0 port. rc8 is getting an error when try to configure the interface. Use rc11.

     

    If the board has multiple Ethernet ports, the port designated Eth0 may change when going between version 4.7 and version 5.

     

    What does ifconfig and "ethtool eth0" show?

     

    Thanks for the tips....

     

    With the Onboard eth0 port (no ide card)

    or

    With the IDE Card and the Onboard port off

    I got the same results

     

    ifconfig

     

    Results:

    Link encap:Local Loopback

    inet addr:127.0.0.1  Mask:255.0.0.0

    UP LOOPBACK RUNNING  MTU:16436  Metric:1

    RX packets:8 errors:0 dropped:0 overruns:0 frame:0

    TX packets:8 errors:0 dropped:0 overruns:0 carrier:0

    collisions:0 txqueuelen:0

    RX bytes:560 (560.0 B)  TX bytes:0 (560.0 B)

     

    ethtool -S

    cannot get driver information no such device

     

    ethtool -t

    cannot get driver information no such device

     

    Tried rebooting which seemed to help Pucker, but that did not help:

    Turns out the router needed to be rebooted. Thanks to all those who looked into this.

     

    Pulled and reset all the RAM (did not help)

    Pulled the Cmos battery (did not help)

     

    Not sure what else to do?

     

    Albin

     

     

  18. I have a test tower, that was running, and had an IP address.  I now do not have an IP address. 

     

    The tower is a Dell Dimension 8250

    To boot to the URAID flash drive I use a CD with "Plop Boot Manager" on it which works great. (the bios for this tower does not seem to support USB booting)

    I do not have PLOP installed to any part of any drive (it is on a CD, so I have my bios to boot to a CD then when PLOP comes up I tell it to boot to the USB)  (Eventually I would like to see if I can install PLOP to a drive outside the array so this process is more automated)

     

    Please keep in mind, I had 5.0-rc8 working on this machine.

     

    Just so you have the whole story: I have a separate test tower for installing other linux distros.  This other machine can not boot to USB either, so one day I grabbed the plop cd from the dell and used it in the other test system.  The next day I (by accident )grabbed the wrong cd (the one with the a linux distro on it) and put it in the dell tower.  On the next reboot ( I was upgrading from rc8 to rc11), the distro started installing on to the test unraid system.  (I am not concerned about the system or the data, but do want to continue to use this system as a test system).  (so PLOP is great, but it does mean your system is at risk if you do something stupid like I did... all the better reason to get plop to a hard drive outside the unraid array, and disable booting from a cd)

     

    I did a backup of the flash when going from rc8 to rc11 just before this happened.  Once I realized what happened I stopped the install, pulled the cd and put the proper cd in (PLOP).

     

    UNRAID did boot, but I had no access to the system through //tower/ or the IP address

     

    I did a

    ifconfg

    and there was no IP address

     

    I thought that maybe the UNRAID files were corrupt, so I restored to the backup, but still no IP address

    I tried 4.7 and not IP address

    I tried disabling the on board ethernet, and installing a ide card linksys lne100tx version 4.1, and no IP address

    I did a fresh install to a different usb drive rc8 and no IP address

    I disconnected all the clobbered hard drives and booted ... no IP address

    I connected 1 fresh hard drive (no others connected) no ..... IP address

    I tested and tried two different cables

    I tested and tried two different wall outlets (Ethernet outlets)

     

     

    I am attaching the syslog from my 4.7 (built in ethernet) attempt and my rc8 attempt (I also tried rc11 but did not get a syslog), also attaching 4.7 with ide card.

     

    I did notice that ETH0 is showing in the 4.7 syslog but not in the rc8 syslog.... not sure what that means.

     

    Also noticed that when using the on board ethernet, I am getting an "EEPROM Corrupted"  (not getting this when using an IDE card with the on board disabled)

     

    I did notice that when I was powerdown the server, I saw "mount can't find / in /etc/fstab or /etc/mtab" on the screen (not sure if that is part of the problem or a separate problem)

     

    Thanks for any help with this.

     

    Albin

     

    syslog-4-7.txt

    syslog-rc8.txt

    syslog-4-7-ide-card.txt

  19. Can someone move this Topic and related replies to:

     

    Lime Technology - unRAID Server Community » General » General Support

     

    With a Subject of: "Understanding Permissions and Using Windows Credentials to Log into Network Shares" (or some appropriate subject) Thanks

     

     

    All users are intended to have read access to a Secure share. This is the difference between Secure and Private. The system is working correctly. Examine the share setup.

     

    Sorry about that I incorrectly assumed what public, secure, private stood for.  I found the following which straightened me out:

     

     

    Public means that no user account is needed on the server for someone to access the share.  This means you won't see the login box pop up when accessing the share.  It also means that anyone can read/write/create/delete any file or directory on the share.  This is the default setting when a new share is created.  This is also the default setting if a share is created by creating it on a disk share.  When a file is created it will be be owned on the linux-side by the 'nobody' user of the users group (uid/gid = 99/100).

     

    Secure means that no user account is necessary on the server in order to access the share, and no login box will pop up.  But in this mode you can select users than can have read/write access to the share, all other users will have read-only access.  Since no login box will appear, in order to get this to work, this must be true:

    - Whatever username you used to log in to your windows PC must also be a user name on the server.  The 'case' of the user name does not matter (actually you must enter all lower-case on server side).

    - The password you set on the server must match exactly the password used for your windows logon.  The password IS case-sensitive.

     

    Private means that you specify the exact set of users that can either have readonly or read/write access to the share.  If you try to connect to the server you may or may not get a login box.  If the username/password of your windows login matches one of the usernames defined on the server side, and that username has either readonly or read/write access (ie, not 'no access), then no login box will appear and you will be be logged into the share with the access rights specified.  But if either your windows username is unknown on the server, or your windows password does not match, then windows will present a login box prompting for a username/password.  Using this box you can then login to the share using one of the other username/passwords on the server.

     

    Note that once you login to the server using some other username than your windows username, windows will use that username to access all shares on the server.

     

    It appears that I do not have to enter log in credentials if my User Name and password that I use for logging into windows vista match the user name and password for an existing user on the unraid network shares.

     

    I am interested in using this feature.  I adjust my Vista user name from "Firstname Lastname" to "firstnamelastname" (I guess I could have used "firstname_lastname" or some other combo.  The password stayed the same.  To make sure windows was not logged into any network share I did the following:

     

    1.  Creating a Fresh Windows Connection

    net use * /delete

    2.  Rebooted Unraid

    3.  Rebooted Windows

    4.  logged into windows "firstnamelastname" "password"

     

    I expected that I could browse to the network share and gain access to a private share that "firstnamelastname" has read/write access to, but I was prompted for a user name and password.  Before putting in credentials I went to a command window and did :

    net use

    and got the following response:

    New connections will not be remembered.

    There are no entries in the list.

     

    Just to clarify:

    I am trying to gain access to Network Share \\tower2\CDMedia

    Network share Export is set to "YES"

    Network share is set to Private

    USER firstnamelastname has read/write access

     

    Results for telnet session:

    Type (replacing 'Media' with the share name--Capitalization is IMPORTANT):        ls -al ../mnt/user/Media

     

    ls -al ../mnt/user/CDMedia

     

    Tower2 login: root

    Linux 3.4.26-unRAID.

    root@Tower2:~# ls -al ../mnt/user/CDMedia

    total 3047

    drwxrwxrwx 1 nobody users    112 2013-02-06 08:44 ./

    drwxrwxrwx 1 nobody users      80 2013-02-06 03:40 ../

    -rw-rw-rw- 1 nobody users    6148 2010-01-15 16:23 .DS_Store

    -rw-rw-rw- 1 nobody users 3104804 2005-12-22 11:15 _7A_00220.jpg

    root@Tower2:~#

    (currently only two files in this test directory)

     

    Am I missing a step?  What else is needed to get my windows Vista credentials to work for my unraid user credentials?

     

    Thanks

     

    Albin

  20. I was not going to place this in this topic, but after working through it, I feel it may very well be version related.  Could be that it is something that many are already aware of, but I could not find it laid out like this.

     

    I am running 5.0-rc11 and the "new permissions" utility was completed.

    Note: I have another tower on the same network running 4.7 (not sure if this plays into things, but felt I should mention it seeing that I access that tower from my windows computer with different user credentials)

     

    General Topic (Public users have read access to secure shares, and users with read/write access, can't write to secure shares, but can read and write to private shares)

     

    I am struggling to access Exported Shares set to "YES" that have Security Set to "Secure".

    Seems I have read/write access to public shares. (public share are working properly)

     

    As I am trouble shooting I am changing the password of a  user, or changing a user from read only to read/write on a  particular share, I am wondering if each one of these changes should be instant, or do I need to reboot UnRAID between each change, or do I need to reboot windows (the computer associated with the edited user settings), or do I need to do both, or is there some other less time consuming option (stopping and restarting the array, or stopping and starting some service on windows).  (I answer this question below)

     

    Test-1

    changing a share from secure to public, and then (no reboots) trying to change the name of a file in the share from my computer did not work.  I get the "Destination Folder Access Denied" / "You need permission to perform this action" (options "try again" "cancel").  (I am accessing these through \\tower\folder\file and not as a mapped network drive )

     

    Test-2

    changed a different network share to public, then went to settings>share settings and changes "Enable User Shares:" to "NO" and then applied this setting, then changed "Enable User Shares:" back to "YES" and then applied this setting.  I then went to the share \\tower\folder2\file and I had read/write access.

     

    So simply turning off the shares and then turning it back on seems to help with getting the changes to take effect.

     

    Test-3

    (note: I just rebooted my computer, I have not reconnected to any network drives, and there are no user credentials stored in the user credentials (except for windows live, which I have read you can delete it but it will just keep coming back, unles you uninstall windows live)

    I can browse to a network share that is set to secure, and see the files and folders of that share even though I have not entered any credentials.

    (I would think that if I have not logged in as a user I should not have read access to a network share that is set to secure

     

    Test-4

    changed a network share from secure to private (all users were set to "No Access") (disabled and then renabled shares to get the settings to take effect), then

    browse to the network share, and I could not see or gain access to the share (this is what I would expect to happen)

     

    Test-5

    changed a network share from secure to private (set one user to read/write access) (disabled and then renabled shares to get the settings to take effect), then browse to the network share, and I could not see or gain access to the share, but I could read and write to the network share after entering the proper user credentials. (this is what I would expect to happen)

     

    Conclusion:

    Public Shares seem to work correctly

    Secure Shares do not seem to be working correctly (public users have read access)

    Private Shares seem to work correctly

     

    Related links / Topics that may help others:

     

    Create a file in the 'config' directory on your flash called 'smb-extra.conf'.  Inside this file, put this line:

     

    acl check permissions = No

     

    Then Stop array and Start array.  Now let me know if this problem persists.

     

    I am entering the user with the the following guidelines:

     

    User names can not contain capital letters.  Here are the rules:

     

    - First character of a username must be a lower-case letter, or the underscore '_' character.

    - Subsequent characters of a username may be lower-case letters, underscore, or dash '-' character.

    - The very last character of a username is permitted to be a dollar sign '$'

    - Maximum total length is 32 characters

     

    Put another way (straight from the code of 'useradd' linux utility):

     

    User/group names must match [a-z_][a-z0-9_-]*[$]

     

    Thanks

     

    Albin

  21. you need to run

    reiserfsck --rebuild-tree /dev/md1

    as it suggests to fix the corruption.

     

    You may need to run the permissions script once more afterwords, as the first could not traverse the full file system because of the corruption.

     

    Joe, Thanks for confirming the steps on this.  I did run

    reiserfsck --rebuild-tree /dev/md1

     

    Last few lines of out put:

    Flushing..finished

            Objects without names 810

            Dirs linked to /lost+found: 12

                    Dirs without stat data found 1

            Files linked to /lost+found 798

    Pass 4 - finished      done 1, 0 /sec

            Deleted unreachable items 1

    Flushing..finished

    Syncing..finished

    ###########

    reiserfsck finished at Mon Feb  4 10:04:43 2013

     

    Full copy attached

     

    I see where it suggest replacing the bad drive.  Is it safe to assume that md1 always equals data disk1 in the array or that

     

    data disk1=/dev/md1 (the disk I need to swap out)

    data disk2=/dev/md2

    data disk3=/dev/md3

    data disk4=/dev/md4

    data disk5=/dev/md5

     

    What would parity be /dev/???

    What woud the Cache drive be /dev/???

     

     

    I am running the "New Permissions" Utility now, then I will start a Parity-Check, and after knowing pariity is valid I will power down backup 'config/super.dat' and 'config/disk.cfg, replace the drive, reboot, and then rebuild the new drive.

     

    Thanks

     

    Albin

     

    reiserfsck_rebuildtree_logfile.txt