Noob need some help


Recommended Posts

Hi @ all.

Yesterday i have installt unRAID. But i can get shared folders. If i create a share it get instand delitet.

In my syslog i get 

ErrorWarningSystemArrayLogin


Feb 4 01:29:46 Tower kernel: 000000008746ba02: 57 ca ec a1 f1 cf f9 1f a8 4e 7e b0 7f 32 18 eb W........N~..2..
Feb 4 01:29:46 Tower kernel: 00000000396736e1: 7c 76 77 3c 60 bf f8 19 ff a9 26 40 66 4d ec eb |vw<`.....&@fM..
Feb 4 01:29:46 Tower kernel: 00000000e70d475b: 8e 20 e4 6a 2e 91 e1 0d ba fe 6d 8c 36 e4 82 7c . .j......m.6..|
Feb 4 01:29:46 Tower kernel: 000000009d690308: d6 d7 d3 4b 98 6e 2b bd d5 4b 9f 06 db b1 d6 07 ...K.n+..K......
Feb 4 01:29:46 Tower kernel: 00000000c8bbc85d: 29 8f 10 eb ae f1 9d 46 9b 7b 2b 9a f8 7d 46 0d )......F.{+..}F.
Feb 4 01:29:46 Tower kernel: 0000000055f2f94d: 67 ad a2 71 66 32 f8 fc 33 b8 d9 ee 84 8f b9 8c g..qf2..3.......
Feb 4 01:29:46 Tower kernel: 0000000035eb173f: 6b ff 63 8c 18 cf bd f8 39 28 66 ee 25 7c 19 28 k.c.....9(f.%|.(
Feb 4 01:29:46 Tower kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x748d60c0 len 32 error 117
Feb 4 01:29:46 Tower emhttpd: error: get_filesystem_status, 6453: Structure needs cleaning (117): scandir
Feb 4 01:29:46 Tower kernel: XFS (md4): xfs_imap_to_bp: xfs_trans_read_buf() returned error -117.
Feb 4 01:29:47 Tower kernel: XFS (md4): Metadata corruption detected at xfs_buf_ioend+0x4c/0x95 [xfs], xfs_inode block 0x748d60c0 xfs_inode_buf_verify
Feb 4 01:29:47 Tower kernel: XFS (md4): Unmount and run xfs_repair
Feb 4 01:29:47 Tower kernel: XFS (md4): First 128 bytes of corrupted metadata buffer:
Feb 4 01:29:47 Tower kernel: 00000000045f68d4: 1c 84 2d 60 07 6d 3b 76 bc 7e 6f a6 d6 79 90 00 ..-`.m;v.~o..y..
Feb 4 01:29:47 Tower kernel: 000000007457aa9a: 57 ca ec a1 f1 cf f9 1f a8 4e 7e b0 7f 32 18 eb W........N~..2..
Feb 4 01:29:47 Tower kernel: 000000008824be33: 7c 76 77 3c 60 bf f8 19 ff a9 26 40 66 4d ec eb |vw<`.....&@fM..
Feb 4 01:29:47 Tower kernel: 000000007fecf381: 8e 20 e4 6a 2e 91 e1 0d ba fe 6d 8c 36 e4 82 7c . .j......m.6..|
Feb 4 01:29:47 Tower kernel: 00000000c251518a: d6 d7 d3 4b 98 6e 2b bd d5 4b 9f 06 db b1 d6 07 ...K.n+..K......
Feb 4 01:29:47 Tower kernel: 00000000f1924bc0: 29 8f 10 eb ae f1 9d 46 9b 7b 2b 9a f8 7d 46 0d )......F.{+..}F.
Feb 4 01:29:47 Tower kernel: 00000000d5b52693: 67 ad a2 71 66 32 f8 fc 33 b8 d9 ee 84 8f b9 8c g..qf2..3.......
Feb 4 01:29:47 Tower kernel: 00000000c28117ca: 6b ff 63 8c 18 cf bd f8 39 28 66 ee 25 7c 19 28 k.c.....9(f.%|.(
Feb 4 01:29:47 Tower emhttpd: error: get_filesystem_status, 6453: Structure needs cleaning (117): scandir
Feb 4 01:29:47 Tower kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x748d60c0 len 32 error 117
Feb 4 01:29:47 Tower kernel: XFS (md4): xfs_imap_to_bp: xfs_trans_read_buf() returned error -117.
Feb 4 01:29:48 Tower kernel: XFS (md4): Metadata corruption detected at xfs_buf_ioend+0x4c/0x95 [xfs], xfs_inode block 0x748d60c0 xfs_inode_buf_verify
Feb 4 01:29:48 Tower kernel: XFS (md4): Unmount and run xfs_repair
Feb 4 01:29:48 Tower kernel: XFS (md4): First 128 bytes of corrupted metadata buffer:
Feb 4 01:29:48 Tower kernel: 0000000011a07842: 1c 84 2d 60 07 6d 3b 76 bc 7e 6f a6 d6 79 90 00 ..-`.m;v.~o..y..
Feb 4 01:29:48 Tower kernel: 00000000d129b4c9: 57 ca ec a1 f1 cf f9 1f a8 4e 7e b0 7f 32 18 eb W........N~..2..
Feb 4 01:29:48 Tower kernel: 000000003120db94: 7c 76 77 3c 60 bf f8 19 ff a9 26 40 66 4d ec eb |vw<`.....&@fM..
Feb 4 01:29:48 Tower kernel: 00000000e9dc39b1: 8e 20 e4 6a 2e 91 e1 0d ba fe 6d 8c 36 e4 82 7c . .j......m.6..|
Feb 4 01:29:48 Tower kernel: 000000000d883621: d6 d7 d3 4b 98 6e 2b bd d5 4b 9f 06 db b1 d6 07 ...K.n+..K......
Feb 4 01:29:48 Tower kernel: 000000007674e211: 29 8f 10 eb ae f1 9d 46 9b 7b 2b 9a f8 7d 46 0d )......F.{+..}F.
Feb 4 01:29:48 Tower kernel: 000000006dbd2ae0: 67 ad a2 71 66 32 f8 fc 33 b8 d9 ee 84 8f b9 8c g..qf2..3.......
Feb 4 01:29:48 Tower kernel: 00000000462c3d0b: 6b ff 63 8c 18 cf bd f8 39 28 66 ee 25 7c 19 28 k.c.....9(f.%|.(
Feb 4 01:29:48 Tower kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x748d60c0 len 32 error 117
Feb 4 01:29:48 Tower emhttpd: error: get_filesystem_status, 6453: Structure needs cleaning (117): scandir
Feb 4 01:29:48 Tower kernel: XFS (md4): xfs_imap_to_bp: xfs_trans_read_buf() returned error -117.
Feb 4 01:29:49 Tower kernel: XFS (md4): Metadata corruption detected at xfs_buf_ioend+0x4c/0x95 [xfs], xfs_inode block 0x748d60c0 xfs_inode_buf_verify
Feb 4 01:29:49 Tower kernel: XFS (md4): Unmount and run xfs_repair
Feb 4 01:29:49 Tower kernel: XFS (md4): First 128 bytes of corrupted metadata buffer:
Feb 4 01:29:49 Tower kernel: 00000000e39246a0: 1c 84 2d 60 07 6d 3b 76 bc 7e 6f a6 d6 79 90 00 ..-`.m;v.~o..y..
Feb 4 01:29:49 Tower kernel: 000000000334d22e: 57 ca ec a1 f1 cf f9 1f a8 4e 7e b0 7f 32 18 eb W........N~..2..
Feb 4 01:29:49 Tower kernel: 00000000bff09a57: 7c 76 77 3c 60 bf f8 19 ff a9 26 40 66 4d ec eb |vw<`.....&@fM..
Feb 4 01:29:49 Tower kernel: 0000000011ac0f33: 8e 20 e4 6a 2e 91 e1 0d ba fe 6d 8c 36 e4 82 7c . .j......m.6..|
Feb 4 01:29:49 Tower kernel: 00000000bb9c8508: d6 d7 d3 4b 98 6e 2b bd d5 4b 9f 06 db b1 d6 07 ...K.n+..K......
Feb 4 01:29:49 Tower kernel: 000000009dd2d0ce: 29 8f 10 eb ae f1 9d 46 9b 7b 2b 9a f8 7d 46 0d )......F.{+..}F.
Feb 4 01:29:49 Tower emhttpd: error: get_filesystem_status, 6453: Structure needs cleaning (117): scandir
Feb 4 01:29:49 Tower kernel: 0000000047beeab1: 67 ad a2 71 66 32 f8 fc 33 b8 d9 ee 84 8f b9 8c g..qf2..3.......
Feb 4 01:29:49 Tower kernel: 00000000528ed46e: 6b ff 63 8c 18 cf bd f8 39 28 66 ee 25 7c 19 28 k.c.....9(f.%|.(
Feb 4 01:29:49 Tower kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x748d60c0 len 32 error 117
Feb 4 01:29:49 Tower kernel: XFS (md4): xfs_imap_to_bp: xfs_trans_read_buf() returned error -117.
Feb 4 01:29:50 Tower kernel: XFS (md4): Metadata corruption detected at xfs_buf_ioend+0x4c/0x95 [xfs], xfs_inode block 0x748d60c0 xfs_inode_buf_verify
Feb 4 01:29:50 Tower kernel: XFS (md4): Unmount and run xfs_repair
Feb 4 01:29:50 Tower kernel: XFS (md4): First 128 bytes of corrupted metadata buffer:
Feb 4 01:29:50 Tower kernel: 0000000088571dc3: 1c 84 2d 60 07 6d 3b 76 bc 7e 6f a6 d6 79 90 00 ..-`.m;v.~o..y..
Feb 4 01:29:50 Tower kernel: 00000000e67afeaa: 57 ca ec a1 f1 cf f9 1f a8 4e 7e b0 7f 32 18 eb W........N~..2..
Feb 4 01:29:50 Tower kernel: 00000000421b27a3: 7c 76 77 3c 60 bf f8 19 ff a9 26 40 66 4d ec eb |vw<`.....&@fM..
Feb 4 01:29:50 Tower kernel: 00000000511e1016: 8e 20 e4 6a 2e 91 e1 0d ba fe 6d 8c 36 e4 82 7c . .j......m.6..|
Feb 4 01:29:50 Tower kernel: 000000001b09dc55: d6 d7 d3 4b 98 6e 2b bd d5 4b 9f 06 db b1 d6 07 ...K.n+..K......
Feb 4 01:29:50 Tower kernel: 000000000feec65f: 29 8f 10 eb ae f1 9d 46 9b 7b 2b 9a f8 7d 46 0d )......F.{+..}F.
Feb 4 01:29:50 Tower kernel: 00000000a9f21589: 67 ad a2 71 66 32 f8 fc 33 b8 d9 ee 84 8f b9 8c g..qf2..3.......
Feb 4 01:29:50 Tower emhttpd: error: get_filesystem_status, 6453: Structure needs cleaning (117): scandir
Feb 4 01:29:50 Tower kernel: 000000003c0d2e35: 6b ff 63 8c 18 cf bd f8 39 28 66 ee 25 7c 19 28 k.c.....9(f.%|.(
Feb 4 01:29:50 Tower kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x748d60c0 len 32 error 117
Feb 4 01:29:50 Tower kernel: XFS (md4): xfs_imap_to_bp: xfs_trans_read_buf() returned error -117.

All my harddrives are fine.

If you need more infos please ask. Sry for bad english.

 

regrads

MrYoshii

 

unraid.png

Link to comment
On 2/5/2019 at 1:39 PM, jonathanm said:

What do you mean?

i down´t know there was a red text. it says max posts a day reached.

 

i have checked filesystem on disk4 now its working. how can i veryfy that its trustet an not failing on me in one or two month?

 also i got 100% on a docker log?

 1474147335_Anmerkung2019-02-08134414.thumb.jpg.c2d5902c53bf86834df1367a43b07ff6.jpg

i have docker and vm dissabled.

sry for my bad english im not a native speaker :D

Link to comment
23 minutes ago, MrYoshii said:

i got 100% on a docker log?

There are  actually 3 items there, flash - log - docker. The 1st number is how full your flash drive is, the 2nd number is how full your log space is, and the 3rd number is how full your docker image is.

 

Your log space filled up with the errors you were getting. You can reboot to clear that.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.