Jump to content

Parigot

Members
  • Posts

    48
  • Joined

  • Last visited

Posts posted by Parigot

  1. failed to load external entity "/boot/config/plugins/statistics.sender.plg"

     

    /boot/ is empty...doesn't sound good, does it?

     

    I did do a backup of what was on the flash drive though. If the flash drive itself is corrupted, can I just copy my backup to a new flash drive, swap them on the PC and boot?

  2. Dismiss just does nothing. Try Install and got an error now:

     

    plugin: installing: https://raw.githubusercontent.com/gfjardim/unRAID-plugins/master/plugins/statistics.sender.plg
    plugin: downloading https://raw.githubusercontent.com/gfjardim/unRAID-plugins/master/plugins/statistics.sender.plg
    plugin: downloading: https://raw.githubusercontent.com/gfjardim/unRAID-plugins/master/plugins/statistics.sender.plg ... done

    Warning: simplexml_load_file(): I/O warning : failed to load external entity "/boot/config/plugins/statistics.sender.plg" in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214
    plugin: xml parse error

  3. I keep receiving this email on a daily basis about some cron job error. I'm running 6.2.4. Does anyone know what it is related to?

     

     

    Email subject:

    cron for user root /usr/bin/run-parts /etc/cron.daily 1> /dev/null

     

    Email body:

    error: Ignoring tor because of bad file mode - must be 0644 or 0444.

    error: skipping "/var/log/apcupsd.events" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.

    error: skipping "/var/log/docker.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.

    error: skipping "/var/log/syslog" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.

    error: skipping "/var/log/vsftpd.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.

    error: skipping "/var/log/wtmp" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.

    error: skipping "/var/log/btmp" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.

  4. Looking to get your thoughts/ideas on this one.

    Planning to replace my aging Core2Duo 3.0Ghz machine by a refurbished XEON server in a rack form factor (2U-4U).

     

    There's obviously a lot of choice on ebay. But I was wondering what you guys would suggest I should get for around $500.

     

    In term of specs, I'm looking for 1 or 2 Xeon 4, 6 or 8 core each, 32gb ram and some expandability since I'd like to add a sata card. It can be diskless as I already have my current disks available (4-6 disks).

     

    Planning to run plex (1-2 stream), crashplan and owncloud.

     

    Thanks in advance!

  5. Sorry if this has already been mentioned. But I can't find any info to help me.

    Does anydoby have some doc explaining how to enable https for owncloud?

    I did some research here and there but can't find the right info.

     

    Any help would be greatly appreciated.

     

    Thanks

  6. Thanks RobJ

     

    I'm currently running a preclear using a new sata cable and using a different sata port on the motherboard. Will see how it goes.

    I'll try the SMART report right after.

     

    As for the parity drive, the 3TB RED will replace it. I made this build with parts I had laying around. The 3TB RED is the only brand new part. But more new parts will come around to improve it.

     

    After changing cable and port, running Preclear worked this time. Took long but it seems ok. Thx for the help everyone.

     

    ================================================================== 1.15
    =                unRAID server Pre-Clear disk /dev/sdb
    =               cycle 1 of 1, partition start on sector 1
    = 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: 36C, Elapsed Time:  32:38:55
    ========================================================================1.15
    == WDCWD30EFRX-68EUZN0   WD-WCC4N5YF2774
    == Disk /dev/sdb has been successfully precleared
    == with a starting sector of 1
    ============================================================================
    ** Changed attributes in files: /tmp/smart_start_sdb  /tmp/smart_finish_sdb
                    ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
          Temperature_Celsius =   114     123            0        ok          36
    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.
    

  7. To add to this issue, I checked the System Logs and found the following for my drive. Wondering more and more if my drive is DOA...

     

    Apr  7 16:57:09 r2d2 kernel: Buffer I/O error on dev sdb, logical block 603280139, lost async page write
    Apr  7 16:57:09 r2d2 kernel: Buffer I/O error on dev sdb, logical block 603280140, lost async page write
    Apr  7 16:57:09 r2d2 kernel: Buffer I/O error on dev sdb, logical block 603280141, lost async page write
    Apr  7 16:57:09 r2d2 kernel: Buffer I/O error on dev sdb, logical block 603280142, lost async page write
    Apr  7 16:57:09 r2d2 kernel: Buffer I/O error on dev sdb, logical block 603280143, lost async page write
    Apr  7 16:57:09 r2d2 kernel: Buffer I/O error on dev sdb, logical block 603280144, lost async page write
    Apr  7 16:57:09 r2d2 kernel: Buffer I/O error on dev sdb, logical block 603280145, lost async page write
    Apr  7 16:57:09 r2d2 kernel: Buffer I/O error on dev sdb, logical block 603280146, lost async page write
    Apr  7 16:57:09 r2d2 kernel: Buffer I/O error on dev sdb, logical block 603280147, lost async page write
    Apr  7 16:57:09 r2d2 kernel: Buffer I/O error on dev sdb, logical block 603280148, lost async page write
    

  8. I just received a WD RED 3TB drive that I will use to replace my 1TB parity drive.

    I ran a preclear on it twice and got the same result. But I don't know what is the issue (if it is one). Any help would be greatly appreciated.

    Thanks

     

    ================================================================== 1.15
    =                unRAID server Pre-Clear disk /dev/sdb
    =               cycle 1 of 1, partition start on sector 1
    =
    = 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
    =
    Elapsed Time:  5:39:04
    ========================================================================1.15
    ==
    == SORRY: Disk /dev/sdb MBR could NOT be precleared
    ==
    == out4= 00000
    == out5= 00000
    ============================================================================
    0000000
    

    I got that when I needed to update the firmware of my SAS Expander.  But I think it could be almost anything.  Maybe someone else has more ideas.  Attaching a Syslog (v5 unRAID) or Diagnostics (v6 unRAID) would help someone else as well.

     

    I attached the Diagnostics to this post.

    r2d2-diagnostics-20160407-2044.zip

  9. I just received a WD RED 3TB drive that I will use to replace my 1TB parity drive.

    I ran a preclear on it twice and got the same result. But I don't know what is the issue (if it is one). Any help would be greatly appreciated.

    Thanks

     

    ================================================================== 1.15
    =                unRAID server Pre-Clear disk /dev/sdb
    =               cycle 1 of 1, partition start on sector 1
    =
    = 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
    =
    Elapsed Time:  5:39:04
    ========================================================================1.15
    ==
    == SORRY: Disk /dev/sdb MBR could NOT be precleared
    ==
    == out4= 00000
    == out5= 00000
    ============================================================================
    0000000
    

  10. Hi,

     

    New to unraid and docker. Trying to fix the 'You are accessing the server from an untrusted domain.' issue but can't find anything helping toward a solution.

    Has anyone found how to fix this?

     

    You are accessing the server from an untrusted domain.

    Please contact your administrator. If you are an administrator of this instance, configure the "trusted_domains" setting in config/config.php. An example configuration is provided in config/config.sample.php.

    Depending on your configuration, as an administrator you might also be able to use the button below to trust this domain.

     

    Thanks

×
×
  • Create New...