xisplo
-
Posts
37 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by xisplo
-
-
19 hours ago, trurl said:
Oct 31 16:50:16 MS2 emhttpd: shcmd (190): xfs_growfs /mnt/disk7 Oct 31 16:50:16 MS2 kernel: XFS (md7): Corruption warning: Metadata has LSN (1227558665:4426755) ahead of current LSN (1:24). Please unmount and run xfs_repair (>= v4.3) to resolve. Oct 31 16:50:16 MS2 kernel: XFS (md7): Metadata CRC error detected at xfs_allocbt_read_verify+0xd/0x3a [xfs], xfs_bnobt block 0xaea86668 Oct 31 16:50:16 MS2 kernel: XFS (md7): Unmount and run xfs_repair Oct 31 16:50:16 MS2 kernel: XFS (md7): First 128 bytes of corrupted metadata buffer: Oct 31 16:50:16 MS2 kernel: 00000000: 36 2e 35 34 30 00 3c 00 a6 09 00 00 d4 31 08 00 6.540.<......1.. Oct 31 16:50:16 MS2 kernel: 00000010: 00 00 00 00 23 72 00 00 49 2b 0f 09 00 43 8c 03 ....#r..I+...C.. Oct 31 16:50:16 MS2 kernel: 00000020: 8a 41 e5 27 4b 10 a9 5f 28 64 e8 49 a5 5b e2 00 .A.'K.._(d.I.[.. Oct 31 16:50:16 MS2 kernel: 00000030: 00 00 00 00 fa d3 f8 06 ff ff ff ff 01 00 00 00 ................ Oct 31 16:50:16 MS2 kernel: 00000040: 12 00 00 80 ff 03 00 4d 00 55 00 76 00 52 00 00 .......M.U.v.R.. Oct 31 16:50:16 MS2 kernel: 00000050: 00 44 42 36 30 55 70 64 74 37 20 41 74 61 63 61 .DB60Updt7 Ataca Oct 31 16:50:16 MS2 kernel: 00000060: 6e 64 20 31 36 6d 67 20 43 6f 73 74 3a 38 2e 33 nd 16mg Cost:8.3 Oct 31 16:50:16 MS2 kernel: 00000070: 32 20 46 65 65 3a 36 2e 35 34 30 00 3c 00 a6 09 2 Fee:6.540.<... Oct 31 16:50:16 MS2 kernel: XFS (md7): metadata I/O error in "xfs_btree_read_buf_block.constprop.0+0x75/0xc1 [xfs]" at daddr 0xaea86668 len 8 error 74 Oct 31 16:50:16 MS2 kernel: XFS (md7): xfs_do_force_shutdown(0x1) called from line 296 of file fs/xfs/xfs_trans_buf.c. Return address = 00000000f269dff4 Oct 31 16:50:16 MS2 kernel: XFS (md7): I/O Error Detected. Shutting down filesystem Oct 31 16:50:16 MS2 root: xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: Structure needs cleaning Oct 31 16:50:16 MS2 root: meta-data=/dev/md7 isize=512 agcount=4, agsize=122094660 blks Oct 31 16:50:16 MS2 root: = sectsz=512 attr=2, projid32bit=1 Oct 31 16:50:16 MS2 root: = crc=1 finobt=1, sparse=1, rmapbt=0 Oct 31 16:50:16 MS2 root: = reflink=1 Oct 31 16:50:16 MS2 root: data = bsize=4096 blocks=488378638, imaxpct=5 Oct 31 16:50:16 MS2 root: = sunit=0 swidth=0 blks Oct 31 16:50:16 MS2 root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Oct 31 16:50:16 MS2 root: log =internal log bsize=4096 blocks=238466, version=2 Oct 31 16:50:16 MS2 root: = sectsz=512 sunit=0 blks, lazy-count=1 Oct 31 16:50:16 MS2 root: realtime =none extsz=4096 blocks=0, rtextents=0 Oct 31 16:50:16 MS2 emhttpd: shcmd (190): exit status: 1 Oct 31 16:50:16 MS2 kernel: XFS (md7): Please unmount the filesystem and rectify the problem(s)
https://wiki.unraid.net/Manual/Storage_Management#Repairing_a_File_System
this solved it, thank you!
-
1 hour ago, trurl said:
Which controller is that disk on? Marvell controllers are NOT recommended, and RAID controllers are NOT recommended.
04:00.0 RAID bus controller [0104]: Marvell Technology Group Ltd. 88SE9485 SAS/SATA 6Gb/s controller [1b4b:9485] (rev c3) 0a:00.0 RAID bus controller [0104]: Marvell Technology Group Ltd. 88SE9485 SAS/SATA 6Gb/s controller [1b4b:9485] (rev c3)
2x SM AOC-SAS2LP-MV8 cards in JBOD
Thank you for the recommendation on the fs repair, we are trying it now.
-
Thank you,
Please find attached.
(we are aware of the SMART errors, these are old WO disks being used to template) -
Just now, trurl said:
And then what? Did you do the required rebuild of the replaced disk? Or did you arrive at this screenshot some other way?
of course the rebuild of the replaced disk took place. I've actually swapped in a second 3Tb and did a full rebuild and still the "size" identity shows 2TB
-
Hello Everyone,
I dont want to recreate the Array as this is a test bench before i go live with it, and this was a test which I'd rather resolve than scratch and rebuild.
On my current production environment, I can easily swap disks and everything works correctly.
However, i cant solve this issue. Disk was precleared.
I swapped in a 3TB for an artificially failed 2TB (unplugged).Any suggestion?
The disk information shows 3TB, I'm just assuming this is a display issue under "size" (note the parity is 4Tb so the 2TB limit consideration does not apply)
-
I would say that no, LT's support for their containers has NOT ended (their last update to Plex was 9/13 (although BTSync lists the latest change as 7/2) But, if you absolutely want to run the absolute latest and greatest version of Plex (instead of something that just plain works), then the LT docker is not for you. Switch to Linuxserver's or Binhex's who concentrate on supporting those apps instead of LT where they have multiple areas to concentrate on (and their docker containers are not their priority - nor should it be)Hello?
Has the support for this container ended?
Please advise if so.
Thank you for all the work you've done,
PLo
Thanks, will do and move to the "latest and greatest" docker containers.
Apologies if this is the wrong thread, I am running the limetech repository version of Plex media server, I am currently trying to connect a smart TV plex app to the fully operational server but I am unable to do so as the server is presenting itself of 2 subnets, 192.168.x.x (My LAN) and 172.17.0.1 (Research tells me this is Docker container networking)
Plex states that the server needs to present itself on a single subnet due to Smart TV app restrictions, is this possible to do with the dockerised version of the PMS?
Thanks ahead for any assistance.
Hi,
under docker > PMS config make sure plex is running
Network type: Host
Privileged: Check
Bind time: Check
PLo
-
Hello?
Has the support for this container ended?
Please advise if so.
Thank you for all the work you've done,
PLo
-
Hello,
Plex has recently release one of the most anticipated updates yet: the ability to control end user bandwidth.
When do you think you'll have the time to release the new update into the docker environment?
thank you for all your work,
PLo
-
I understand what you guys are attempting.
but there are 47 pages of material to skim through. i don't think anyone newer is willing to go through the trouble of finding the solution this way or even attempt to post in the right location.
I was unaware that needo is no longer as involved as he once was. Maybe I should change my repos.
None the less, thanks for the cooperation and help.
CHBMB has helped me solve my problem
-
I was unaware of this.
This is by far the worst experience on this forum.
Users should be able to create new topics in the container support section.
for example "needo sabnzbd: help needed about blah blah"
This has honestly turned me away from seeking help regarding containers on this community forum.
[SOLVED] replaced drive size does not match actual capacity
in General Support
Posted
which part, the cards or not in JBOD?
We will verify that, thank you.
Changing Subject to [Solved]