EdgarWallace

Members
  • Content count

    758
  • Joined

  • Last visited

Community Reputation

2 Neutral

About EdgarWallace

  • Rank
    Advanced Member
  • Birthday 09/05/63

Converted

  • Gender
    Male
  • Location
    Germany
  1. I have a question related to the Dynamix File Integrity plugin: Is it possible to exclude an entire disk by adding e.g. /mnt/ disk1 into the Custom folders? Only disk2 is always complaining that Build & Export are not up-to-date. Any advise how to fix that? Thanks a lot.
  2. ...anyone having an idea? Do you see a similar behaviour of your VM?
  3. Not sure if that is the correct forum but I am having an issue with the NTP server. The time is always behind however the NTP process is running (“Set date & time automatically” is on): ps ax| grep ntp 10290 ?? Ss 0:00.02 /usr/sbin/ntpd -c /private/etc/ntp-restrict.conf -n -g -p /var/run/ntpd.pid -f /var/db/ntp.drift 10321 s002 S+ 0:00.00 grep ntp Is there anything I have overlooked?
  4. @dmacias, I was missing your script after having switched away from my ASROCK board and great to having it back :-) I have connected my CPU fan to FANA and FAN1-4 are all case fans. I chose settings according to this (see picture attached). CPU Fan is now running much lower than before (1.000rpm vs. 2.300). No changes yet on the FAN1-4 in terms of rpm as I just installed a dual parity drive and data-rebuild is running, hence the quite high disk temperature requires FAN1-4 to run high.
  5. Thanks a lot CHBMB that fixed the issue with the X-Frame-Options-Header. The webgui of Nextcloud stopped to report issues. Any thoughts what went wrong with my attempt to switch from https://server.com/nextcloud to https://nextcloud.server.com?
  6. CHBMB, thank you soooo much for your guide. I was able to upgrade Nextcloud to the version 12. However I was not able to switch from https://server.com/nextcloud to https://nextcloud.server.com and as result Nextcloud Security scan is showing me a Rating A rather than a Rating A+. There are two elements that the scan is complaining about, please see attached screen shot. appdata/letsencrypt/nginx/site-confs/default: server { listen 443 ssl; server_name dyndns-server.spdns.net; root /config/www; index index.html index.htm index.php; ###SSL Certificates ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ###Diffie–Hellman key exchange ### ssl_dhparam /config/nginx/dhparams.pem; ###SSL Ciphers ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA'; ###Extra Settings### ssl_prefer_server_ciphers on; ssl_session_cache shared:SSL:10m; ### Add HTTP Strict Transport Security ### add_header Strict-Transport-Security "max-age=63072000; includeSubdomains"; add_header Front-End-Https on; client_max_body_size 0; location / { proxy_pass https://192.168.1.28:444/; proxy_max_temp_file_size 2048m; include /config/nginx/proxy.conf; } } appdata/nextcloud/www/nextcloud/config/config.php: <?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => 'oc70mn6ljhz2', 'passwordsalt' => 'secretpassword', 'secret' => 'secretpassword', 'trusted_domains' => array ( 0 => '192.168.1.28:444', 1 => 'dyndns-server.spdns.net', ), 'overwrite.cli.url' => 'https://dyndns-server.spdns.net', 'overwritehost' => 'dyndns-server.spdns.net', 'overwriteprotocol' => 'https', 'dbtype' => 'mysql', 'version' => '12.0.0.29', 'dbname' => 'nextcloud', 'dbhost' => '192.168.1.28:3306', 'dbport' => '', 'dbtableprefix' => 'oc_', 'dbuser' => 'oc_root', 'dbpassword' => 'secretpassword', 'logtimezone' => 'UTC', 'installed' => true, 'default_language' => 'de', 'maintenance' => false, 'defaultapp' => 'files', 'knowledgebaseenabled' => true, 'enable_avatars' => true, 'allow_user_to_change_display_name' => false, 'loglevel' => 0, 'logfile' => '/config/nextcloud.log', 'appstoreenabled' => true, 'updater.release.channel' => 'stable', 'updater.secret' => 'secretpassword', 'theme' => '', ); Second issue is the warning about the X-FRAME-Options Header. Sorry for the german message. I can only get rid of that message by out commenting the parameter in appdata/nextcloud/www/nextcloud/.htaccess like so: <IfModule mod_env.c> # Add security and privacy related headers # Header set X-Frame-Options "SAMEORIGIN"
  7. Thanks a lot @johnnie.black. Meanwhile I have edit the initial post with the error messages that I found.
  8. I was building an unRAID server for my brother and it was running well until beginning of May. The amount of errors is even higher now and I don't know where to additionally look at. He checked the cabling and the memory test passed without issues. The diagnostic file is attached maybe someone is identifying the root cause. Here are errors: May 2 13:21:44 NAS kernel: md: recovery thread: PQ corrected, sector=1119946560 May 2 13:21:44 NAS kernel: md: recovery thread: PQ corrected, sector=1119946568 May 2 13:21:44 NAS kernel: md: recovery thread: PQ corrected, sector=1119946576 May 2 13:21:44 NAS kernel: md: recovery thread: PQ corrected, sector=1119946584 It is a ASROCK E3C224D4I-14S mobo with 2 controller: Intel C224 : 4 x SATA3 6.0 Gb/s (from mini SAS connector), 2 x SATA2 3.0 Gb/s, Support RAID 0, 1, 5, 10 and Intel® Rapid Storage LSI 2308: 8 x SAS2 6Gbps ( from 2x mini SAS 8087 connector Thanks a lot. nas-diagnostics-20170503-1658.zip
  9. I just discovered this really nice docker and it is running well. Only thing I discovered it an error message from "Fix Commun Problems" plugin: Docker application CrashPlan has volumes being passed that are mounted by Unassigned Devices, but they are not mounted with the slave option My USB drive is not attached right now, can this cause the message? I don#t know what the SLAVE option is....
  10. SUCCESS A second parity check after the xfs_repair /dev/md5 was showing 14 sync errors that were corrected. The final parity check reported 0 errors. I rate my issues with the removal of the AOC-SAS2LP-MV8 and the insert of a DELL PERC H200 as fixed. Good to rely on my backup server (again). Thanks to all who were helping, mainly @johnnie.black and @Fireball3
  11. @Joseph, this was at the start of the parity check, the average was about 90MB/s, which is about the same speed I was getting with my AOC-SAS2LP-MV8. @johnnie.black thanks a lot, see the outcome below....looks pretty good right? Parity Check ended with 24 errors. I am going to run a Parity Check once again with "Write corrections to parity" option. root@Tower2:~# xfs_repair /dev/md5 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 Metadata corruption detected at xfs_inode block 0x11c002b18/0x2000 - agno = 3 bad CRC for inode 6811791504 bad magic number 0x0 on inode 6811791504 bad version number 0x0 on inode 6811791504 bad CRC for inode 6811791504, will rewrite bad magic number 0x0 on inode 6811791504, resetting magic number bad version number 0x0 on inode 6811791504, resetting version number imap claims a free inode 6811791504 is in use, correcting imap and clearing inode cleared inode 6811791504 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 3 - agno = 1 - agno = 2 entry "ja.js" at block 0 offset 152 in directory inode 6642449595 references free inode 6811791504 clearing inode number in entry at offset 152... Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... bad hash table for directory inode 6642449595 (no data entry): rebuilding rebuilding directory inode 6642449595 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... done
  12. I have finally received my Dell Perc H200 and thanks to the HUGHE efforts of @Fireball3 my backup server is running it's first Parity Check. I have unchecked the "Write corrections to parity" option in order to see if the server will stay at 8 errors that came up with the AOC-SAS2LP-MV8 card. If everything's running well I will check again including the "write corrections" options and running a 3rd check finally. Cross fingers..... EDIT: 9 Sync Errors detected at 38,3% Parity Sync. What is making me nervous is this: Pastebin
  13. Thanks to the HUGHE efforts of @Fireball3 my Dell Perc H200 is running it's first Parity Check at an impressive speed at 168,4 MB/sec. Thank you VERY much.
  14. Meanwhile I was looking into this https://hardforum.com/threads/flashing-it-firmware-to-dell-h200-on-x9scm.1773245/ and this: https://forums.lime-technology.com/topic/25420-m1015-x9scm-f-usb-firmware-tools/ According to these links I was booting into the EFI Shell of my X9SCL-F board and copied the Toolset_PercH310 to LSI9211_P20.00.07.00_efimod to the flash drive. Here is the outcome: sas2flash -l Adapters.txt -listall Adapter Selected is a LSI SAS: SAS2008(B2) Controller is not operational. A firmware download is required. Enter firmware file name or quit to exit: Firmware fault occurred. Fault code: D04 Due to error remaining commands will not be executed. Unable to Process Commands. Exiting SAS2Flash. The boot menu of the adapter card is gone by the way....seems that 1.bat in a previous run did it's job. I will happily test your V2 as soon as it's uploaded. Thank you VERY much for your help.
  15. Sorry for confusion I caused. I meant that I am getting the same error messages that his screen shot showed. For further clarification I attached the IPMI screen shot
Copyright © 2005-2017 Lime Technology, Inc. unRAID® is a registered trademark of Lime Technology, Inc.