ahab666
-
Posts
77 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by ahab666
-
-
THX will do that - will i get slapped for cross-posting ?
-
Thx, I found a plethora of log files but most of them (and their entries) are referring to duplicate hash entries - from the time before I shrank my array to less but bigger physical disks.
Can I search for a specific string in all of that files that will point me to the defective files ?
And how do U get rid of the of duplicate entries ? Deleting the log files after I got rid of the corrupted ones ?
I am no nix expert - so I am not familiar with the grep command .... 😕
cheers - alex
-
Hello,
I am getting a "bunker" - warning about some md5 file corruptions, even though the most recent parity check ended with 0 errors.
What can I do now ? Is there is a log file, in which I can see the files listed that are corrupt, please tell me where to find it. Will a XFS file system check reveal the corrupt files and maybe even correct them ?
cheers alex
-
Thanks - it happened either during the initial parity run or slightly afterwards .... 😄
-
37 minutes ago, JorgeB said:
See the notification details, it should have more info, possibly a device temperature issue, if a device temp is above the set warning it will be considered a fail.
THX for that idea - but my server is in an unheated basement and its winter time ... even during summer HDD temperatures rarely reach 32 to 35 C ....
cheers
-
Sorry did not consider that .... 2nd try
-
After changing my parity drives - because the last ones i used produced read errors, even though they passed the full pre-clear routine.
With the factory-new drives I did a resynch without a preclear and it seemed to work, BUT now I am getting an error notification array health report = FAIL
Can anyone explain that to me please, attached 2 files and if you need additional dumps please name them including their location(s).
cheers
-
4 hours ago, binhex said:
You do not need to translate the file, it looks like the cert is inline so just drop this file into /config/openvpn/ and hopefully the magic will happen, check the log file /config/supervisord.log to track progress
Sent from my 22021211RG using Tapatalk
Hello Mr. Binhex,
thx for the very fast response
....
now i am really confused - copied the file, and edited the deluge settings from within the gui.
starting the docker seems to work but starting the the gui brings up the notorious error msg
website cannot be reached (sorry ger->eng) , check firwall and proxy settings
ERR_CONNECTION_REFUSED
can i delete the supervisord.log file without breaking delugevpn - just asking because it is allready 200 KiB in size and i dont wanna post such a monster here in the forum .....
-
Hello,
as a newby to docker and vpn use and after a moot 45 minute chat session with their so called support i have
a very odd question for all you unraid / *.nix wizards : how can one translate my VPN providers ovpn files to use it with delugevpn ?
example :
**************************** start ********************************
client
remote nl2.jumptoserver.com 4443
proto udp
dev tun
auth-user-pass
tls-client
resolv-retry infinite
remote-random
nobind
tun-mtu 1500
tun-mtu-extra 32
mssfix 1450
persist-key
persist-tun
ping 15
ping-restart 0
ping-timer-rem
reneg-sec 0
comp-lzo
cipher AES-256-CBC
auth SHA256
<ca>
-----BEGIN CERTIFICATE-----
MIIFQjCCAyqgAwIBAgIIUfxepT+rr8owDQYJKoZIhvcNAQEMBQAwPzELMAkGA1UE
BhMCS1kxEzARBgNVBAoTCkZhc3Rlc3RWUE4xGzAZBgNVBAMTEkZhc3Rlc3RWUE4g
Um9vdCBDQTAeFw0xNzA5MTYwMDAxNDZaFw0yNzA5MTQwMDAxNDZaMD8xCzAJBgNV
BAYTAktZMRMwEQYDVQQKEwpGYXN0ZXN0VlBOMRswGQYDVQQDExJGYXN0ZXN0VlBO
IFJvb3QgQ0EwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAwggIKAoICAQC1Xj+WfPTo
zFynFqc+c3CVrggIllaXEl5bY5VgFynXkqCTM6lSrfC4pNjGXUbqWe6RnGJbM4/6
kUn+lQDjFSQV1rzP2eDS8+r5+X2WXh4AoeNRUWhvSG+HiHD/B2EFK+Nd5BRSdUjp
KWAtsCmT2bBt7nT0jN1OdeNrLJeyF8siAqv/oQzKznF9aIe/N01b2M8ZOFTzoXi2
fZAckgGWui8NB/lzkVIJqSkAPRL8qiJLuRCPVOX1PFD8vV//R8/QumtfbcYBMo6v
Ck2HmWdrh5OQHPxb3KJtbtG+Z1j8x6HGEAe17djYepBiRMyCEQvYgfD6tvFylc4I
quhqE9yaP60PJod5TxpWnRQ6HIGSeBm+S+rYSMalTZ8+pUqOOA+IQCYpfpx6EKIJ
L/VsW2C7cXdvudxDhXPI5lR/QidCb9Ohq3WkfxXaYwzrngdg2avmNqId9R4KESuM
9GoHW0dszfyBCh5wYfeaffMElfDam3B92NUwyhZwtIiv623WVXY9PPz+EDjSJsIA
u2Vi1vdJyA4nD4k9Lwmx/1zTc/UaYVLsiBqL2WdfvFTeoWoV+dNxQXSEPhB8gwi8
x4O4lZW0cwVy/6fa8KMY8gZbcbSTr7U5bRERfW8l+jY+mYKQ/M/ccgpxaHiw1/+4
LWfbJQ7VhJJrTyN0C36FQzY1URkSXg+53wIDAQABo0IwQDAPBgNVHRMBAf8EBTAD
AQH/MA4GA1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQUmVEL4x6xdCqiqu2OBLs27EA8
xGYwDQYJKoZIhvcNAQEMBQADggIBABCpITvO1+R4T9v2+onHiFxU5JjtCZ0zkXqR
CMp/Z0UIYbeo1p07pZCPAUjBfGPCkAaR++OiG9sysALdJf8Y6HQKcyuAcWUqQnaI
hoZ2JcAP7EKq7uCqsMhcYZD/j3O/3RPtSW5UOx6ItDU+Ua0t9Edho9whNw0VQXmo
1JjYoP3FzPjuKoDWTSO1q5eYlZfwcTcs55O2shNkFafPg/6cCm5j6v9nyHrM3sk4
LjkrBPUXVx2m/aoz219t8O9Ha9/CdMKXsPO/8gTUzpgnzSgPnGnBmi5xr1nspVN8
X4E2f3D+DKqBim3YgslD68NcuFQvJ0/BxZzWVbrr+QXoyzaiCgXuogpIDc2bB6oR
XqFnHNz36d4QJmJdWdSaijiS/peQ6EOPgOZ1GuObLWlDCBZLNeQ+N6QaiJxVO4XU
j/s22i1IRtwdz84TRHrbWiIpEymsqmb/Ep5r4xV5d6+791axclfOTH7tQrY/SbPt
TJI4OEgNekI8YfadQifpelF82MsFFEZuaQn0lj+fvLGtE/zKh3OdLTxRc5TAgBB+
0T81+JQosygNr2aFFG0hxar1eyw/gLeG8H+7Ie50pyPvXO4OgB6Key8rSExpilQX
lvAT1qX0qS3/K1i/9QkSE9ftIPT6vtwLV2sVQzfyanI4IZgWC6ryhvNLsRn0NFnQ
clor0+aq
-----END CERTIFICATE-----
</ca>
key-direction 1
<tls-auth>
-----BEGIN OpenVPN Static key V1-----
697fe793b32cb5091d30f2326d5d124a
9412e93d0a44ef7361395d76528fcbfc
82c3859dccea70a93cfa8fae409709bf
f75f844cf5ff0c237f426d0c20969233
db0e706edb6bdf195ec3dc11b3f76bc8
07a77e74662d9a800c8cd1144ebb67b7
f0d3f1281d1baf522bfe03b7c3f963b1
364fc0769400e413b61ca7b43ab19fac
9e0f77e41efd4bda7fd77b1de2d7d785
5cbbe3e620cecceac72c21a825b243e6
51f44d90e290e09c3ad650de8fca99c8
58bc7caad584bc69b11e5c9fd9381c69
c505ec487a65912c672d83ed0113b5a7
4ddfbd3ab33b3683cec593557520a72c
4d6cce46111f56f3396cc3ce7183edce
553c68ea0796cf6c4375fad00aaa2a42
-----END OpenVPN Static key V1-----
</tls-auth>**************************** end *********************************
I watched space invaders videos - where he just put 3 files to the deluge config directory ....
Can the *.cert and *.pem file be created from the above file - are there changes to be made etc.
cheers and thx upfront
-
Hello, i use a combination of different array disks all check out well with smart self testing.
As parity drives i use 2 18TB Seagate Exos drives - both checked out fine during the pre clear run.
The SATA/SAS Conrtoller is from LSI - SAS2116.
here is some of its specs :
---------------------
<node id="storage" claimed="true" class="storage" handle="PCI:0000:01:00.0">
<description>Serial Attached SCSI controller</description>
<product>SAS2116 PCI-Express Fusion-MPT SAS-2 [Meteor]</product>
<vendor>Broadcom / LSI</vendor>
<physid>0</physid>
<businfo>pci@0000:01:00.0</businfo>
<logicalname>scsi1</logicalname>
<version>02</version>
<width units="bits">64</width>
<clock units="Hz">33000000</clock>
<configuration>
<setting id="driver" value="mpt3sas" />
<setting id="latency" value="0" />
</configuration>
<capabilities>---------------------
Are there any issues known with that drive/controller combination ?
Are there any HDD tune or controller or global tweaks that might help ?
i will preaclear the both Parity drives once again so you can take your time (about 48 to 60 hours)
with any answers or solutions.
Feel fre to asl for any log or diagnostic files - and please tell me where to find them.
cheers ahab666
-
Hello,
besides the "work-around" with a login with the servername and the ip address is there any other solution besides the optional windows unix/nfs feature ?
cheers aleX
-
So far unbalance did a great job - but since the hard coded and preferred https:// connection requirement is in most main stream browsers things got a bit inconvenient to say the least.
Only solution for me so far :
1 run the Unraid-Gui and Unbalance in two separate browser tabs in the browsers private mode by right click the UNB button in the Unraid-Gui or
2 use a bookmark for the UNB part.
In both cases one needs to click twice for the browser to use the "unsafe" web page ... as it is in private mode one needs to to this in every "new" browser session.
Bug or feature in UNB ? The elapsed time starts always with some 8 to 12 hours offset rather than with 0:00:00
At the moment i am "rescuing" a failing 3 TB disk and I observed another strange phenomenon in the Unraid Main view :
Take a look at the reads and writes for the 2 parity disks, then the read and writes for disk 10 (source) and disk 01 (target) and all the other disks.
In a perfect world all drives but 10 and 01 should be and stay spun down and the transfer speeds should be between 120 and 180 MByte per second rather than 30-50 MB/sec average.
Another nice thing would be nice if the read errors defective files or HDD segments would not be UNB "moved" and one could find out the name of the "lost" files.
I attached 2 screen shots to explain what i mean ...
cheers
-
Thank you so much - the last link to the wiki enabled me to start the rebuild - re-enable process ...
fiy - the weirdest thing though - I was able to see the files in dolphin and even on my win pc (emulated probably) via Samba and NFS.
Now my most stupid Question - how can i tag the thread as solved (=edit the topic line ???) ?
-
23 hours ago, johnnie.black said:
Also note that both disks will still need to be rebuilt, but only if the emulated disks are mounting and showing the correct data.
hmmm - how can I find out if the data are still correct ?
And how can I start the rebuilt process ?
I thought the parity drives allow to replace complete failed/defective disks ....
-
Okay
23 hours ago, johnnie.black said:That's not what the diags show, initially:
Aug 10 01:10:27 Tower emhttpd: shcmd (85): mkdir -p /mnt/disk12 Aug 10 01:10:27 Tower emhttpd: shcmd (86): mount -t xfs -o noatime,nodiratime /dev/md12 /mnt/disk12 Aug 10 01:10:27 Tower kernel: XFS (md12): Metadata CRC error detected at xfs_sb_read_verify+0x114/0x15e [xfs], xfs_sb block 0xffffffffffffffff Aug 10 01:10:27 Tower kernel: XFS (md12): Unmount and run xfs_repair Aug 10 01:10:27 Tower kernel: XFS (md12): First 128 bytes of corrupted metadata buffer: Aug 10 01:10:27 Tower kernel: 00000000d3e59167: 58 46 53 42 00 00 10 00 00 00 00 00 1d 1c 11 0e XFSB............ Aug 10 01:10:27 Tower kernel: 00000000680eb2cf: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Aug 10 01:10:27 Tower kernel: 000000007cb90224: 29 d1 16 8f 8d 1c 42 6b b6 a7 42 d1 f4 88 c4 75 ).....Bk..B....u Aug 10 01:10:27 Tower kernel: 00000000c3566992: 00 00 00 00 10 00 00 05 00 00 00 00 00 00 00 60 ...............` Aug 10 01:10:27 Tower kernel: 00000000323821d9: 00 00 00 00 00 00 00 61 00 00 00 00 00 00 00 62 .......a.......b Aug 10 01:10:27 Tower kernel: 00000000f1b45957: 00 00 00 01 07 47 04 44 00 00 00 04 00 00 00 00 .....G.D........ Aug 10 01:10:27 Tower kernel: 00000000d994568a: 00 03 a3 82 b4 b5 02 00 02 00 00 08 00 00 00 00 ................ Aug 10 01:10:27 Tower kernel: 0000000019056dcd: 00 00 00 00 00 00 00 00 0c 09 09 03 1b 00 00 05 ................ Aug 10 01:10:27 Tower kernel: XFS (md12): SB validate failed with error -74. Aug 10 01:10:27 Tower root: mount: /mnt/disk12: mount(2) system call failed: Structure needs cleaning. Aug 10 01:10:27 Tower emhttpd: shcmd (86): exit status: 32 Aug 10 01:10:27 Tower emhttpd: /mnt/disk12 mount error: No file system Aug 10 01:10:27 Tower emhttpd: shcmd (87): umount /mnt/disk12 Aug 10 01:10:27 Tower root: umount: /mnt/disk12: not mounted. Aug 10 01:10:27 Tower emhttpd: shcmd (87): exit status: 32 Aug 10 01:10:27 Tower emhttpd: shcmd (88): rmdir /mnt/disk12 Aug 10 01:10:27 Tower emhttpd: shcmd (89): mkdir -p /mnt/disk13 Aug 10 01:10:27 Tower emhttpd: shcmd (90): mount -t xfs -o noatime,nodiratime /dev/md13 /mnt/disk13 Aug 10 01:10:27 Tower root: mount: /mnt/disk13: mount(2) system call failed: Structure needs cleaning. Aug 10 01:10:27 Tower kernel: XFS (md13): Metadata CRC error detected at xfs_sb_read_verify+0x114/0x15e [xfs], xfs_sb block 0xffffffffffffffff Aug 10 01:10:27 Tower kernel: XFS (md13): Unmount and run xfs_repair Aug 10 01:10:27 Tower kernel: XFS (md13): First 128 bytes of corrupted metadata buffer: Aug 10 01:10:27 Tower kernel: 000000006f8c05c4: 58 46 53 42 00 00 10 00 00 00 00 00 1d 1c 11 0e XFSB............ Aug 10 01:10:27 Tower kernel: 00000000ce15d76b: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Aug 10 01:10:27 Tower kernel: 00000000204e19e6: 84 8f 09 65 2b b2 41 fc 85 8c e1 ba fb 86 15 3f ...e+.A........? Aug 10 01:10:27 Tower kernel: 00000000ef363133: 00 00 00 00 10 00 00 05 00 00 00 00 00 00 00 60 ...............` Aug 10 01:10:27 Tower kernel: 000000008480b48b: 00 00 00 00 00 00 00 61 00 00 00 00 00 00 00 62 .......a.......b Aug 10 01:10:27 Tower kernel: 000000004876be3a: 00 00 00 01 07 47 04 44 00 00 00 04 00 00 00 00 .....G.D........ Aug 10 01:10:27 Tower kernel: 000000002d34a656: 00 03 a3 82 b4 b5 02 00 02 00 00 08 00 00 00 00 ................ Aug 10 01:10:27 Tower kernel: 00000000188e404a: 00 00 00 00 00 00 00 00 0c 09 09 03 1b 00 00 05 ................ Aug 10 01:10:27 Tower kernel: XFS (md13): SB validate failed with error -74. Aug 10 01:10:27 Tower emhttpd: shcmd (90): exit status: 32 Aug 10 01:10:27 Tower emhttpd: /mnt/disk13 mount error: No file system Aug 10 01:10:27 Tower emhttpd: shcmd (91): umount /mnt/disk13 Aug 10 01:10:27 Tower root: umount: /mnt/disk13: not mounted.Then:
Aug 10 01:36:43 Tower emhttpd: shcmd (430): mkdir -p /mnt/disk12 Aug 10 01:36:43 Tower emhttpd: shcmd (431): mount -t xfs -o noatime,nodiratime /dev/md12 /mnt/disk12 Aug 10 01:36:43 Tower kernel: XFS (md12): Mounting V5 Filesystem Aug 10 01:36:44 Tower kernel: XFS (md12): Starting recovery (logdev: internal) Aug 10 01:36:44 Tower kernel: XFS (md12): Ending recovery (logdev: internal) Aug 10 01:36:44 Tower emhttpd: shcmd (432): xfs_growfs /mnt/disk12 Aug 10 01:36:44 Tower root: meta-data=/dev/md12 isize=512 agcount=4, agsize=122094660 blks Aug 10 01:36:44 Tower root: = sectsz=512 attr=2, projid32bit=1 Aug 10 01:36:44 Tower root: = crc=1 finobt=1, sparse=0, rmapbt=0 Aug 10 01:36:44 Tower root: = reflink=0 Aug 10 01:36:44 Tower root: data = bsize=4096 blocks=488378638, imaxpct=5 Aug 10 01:36:44 Tower root: = sunit=0 swidth=0 blks Aug 10 01:36:44 Tower root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Aug 10 01:36:44 Tower root: log =internal log bsize=4096 blocks=238466, version=2 Aug 10 01:36:44 Tower root: = sectsz=512 sunit=0 blks, lazy-count=1 Aug 10 01:36:44 Tower root: realtime =none extsz=4096 blocks=0, rtextents=0 Aug 10 01:36:44 Tower emhttpd: shcmd (433): mkdir -p /mnt/disk13 Aug 10 01:36:44 Tower emhttpd: shcmd (434): mount -t xfs -o noatime,nodiratime /dev/md13 /mnt/disk13 Aug 10 01:36:44 Tower kernel: XFS (md13): Mounting V5 Filesystem Aug 10 01:36:44 Tower kernel: XFS (md13): Starting recovery (logdev: internal) Aug 10 01:36:44 Tower kernel: XFS (md13): Ending recovery (logdev: internal) Aug 10 01:36:44 Tower emhttpd: shcmd (435): xfs_growfs /mnt/disk13 Aug 10 01:36:44 Tower root: meta-data=/dev/md13 isize=512 agcount=4, agsize=122094660 blks Aug 10 01:36:44 Tower root: = sectsz=512 attr=2, projid32bit=1 Aug 10 01:36:44 Tower root: = crc=1 finobt=1, sparse=0, rmapbt=0 Aug 10 01:36:44 Tower root: = reflink=0 Aug 10 01:36:44 Tower root: data = bsize=4096 blocks=488378638, imaxpct=5 Aug 10 01:36:44 Tower root: = sunit=0 swidth=0 blks Aug 10 01:36:44 Tower root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Aug 10 01:36:44 Tower root: log =internal log bsize=4096 blocks=238466, version=2 Aug 10 01:36:44 Tower root: = sectsz=512 sunit=0 blks, lazy-count=1 Aug 10 01:36:44 Tower root: realtime =none extsz=4096 blocks=0, rtextents=0Please post new diags after array start.
here we are sir ;) .....
-
44 minutes ago, johnnie.black said:
Parity can't help with filesystem corruption, according to your diags discs 12 and 13 weren't mounting, but they are now, likely the result of running xfs_repair.
No they are still marked as unmountable - as there is no (or a corrupt) file system present. I wonder what the parity discs are for if not for repairing corrupt data ?
-
Hello,
using my unraid mostly for data storage and streaming I was puzzled about the fact that 2 drives fell into an unmountable status without former warnings.
The filesystem is XFS - so I tried to repair them without the -n option. That did not work, so I used the recomended -L option. The 2 drives are still not mountable but the content is still there provided by the parity discs.
I attached the diagnosis file called "tower-diagnostics-20200810-1216.zip" , if you need something else .....
Please provide me with an easy to understand - repair using the parity discs protocol ...
cheers alex
-
Hello,
I'd like to use unassigned Disks (NTFS) to feed Data to my Array. Here are my questions :
1. where can one find the unassigned and mountes disk(s) in Crusader or dolphin starting from /
2. would a program like unbalance work in one way unass. disk ---> array or even <---> ?
3. many Android driven tv-media boxes are able to read and write to NTFS formatted disks - so doable in Unraid ???
cheers alX
-
Hello Folks,
i am relatively new to Unraid and a complete Unix/Linux noob - i can use a terminal app from windows to comandos but i do not know them ....
my question - could anyone help me with the installation and the config part of deluge and how i use deluge on my unraid server ....
cheers - ahab666
-
i tried that and it worked like a charm ....
thx for tha help
-
1
-
-
On 1.4.2017 at 6:17 PM, Squid said:
Old bug from a prior trip. Just click in the box where you're seeing it, and delete the contents. Disk won't actually be read-only. Just the comment got left in there a while ago.
hello
there is no box - that line is shown in GUI - shares - disc shares - comment - it is not select- or editable
cheers - ahab666
....
Parity drive 01 is deactivated parity 02 seems to be okay, one Array Disk is now emulated :(
in General Support
Posted
Hello,
due to a general power outage, I found my server in that bad (or just annoying) situation.
What is the fastest way to restore the whole system - I am quite sure that there are no hardware problems with the HDD's a.s.o.
If you need any log files, please tell me how to generate and/or where to find them ....
Cheers - ahab