
madpoet
Members-
Content Count
238 -
Joined
-
Last visited
Community Reputation
0 NeutralAbout madpoet
-
Rank
Member
Converted
-
Gender
Undisclosed
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
Docker containers failed update and now are "stuck"
madpoet replied to madpoet's topic in Docker Engine
Whew -
Docker containers failed update and now are "stuck"
madpoet replied to madpoet's topic in Docker Engine
No room in the case for another controller. Have to think about what I can do. -
Docker containers failed update and now are "stuck"
madpoet replied to madpoet's topic in Docker Engine
Weird. Been running perfectly fine for almost 3 years -
Docker containers failed update and now are "stuck"
madpoet replied to madpoet's topic in Docker Engine
Thanks, I knew I forgot something. Ignore the bad drive I need to get that sorted today tower-diagnostics-20200224-0827.zip -
Hello, I went to mass update a few Docker containers and it completely bombed out on them. Now none of them will start, and if I try force update they all give me "Error: open /var/lib/docker/tmp/GetImageBlob777644061: read-only file system". Different blob names obviously. Any ideas on how to recover? One of them is Plex so I REALLY don't want to have to recreate it. Thanks!
-
[Support] Linuxserver.io - Plex Media Server
madpoet replied to linuxserver.io's topic in Docker Containers
Sorry just found the video in the other thread -
So the test completed fine: SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 18588 - So... what do I do to recover this sucker? Do I just need to reformat it or something?
-
Thanks yeah I had a fan issue one time and they all got super toasty but it was quite some time ago. I'll be interested to see what the extended test shows. Appreciate the help.
-
Running a long test now, it will be done sometime tomorrow
-
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.14.26-unRAID] (local build) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Archive HDD Device Model: ST8000AS0002-1NA17Z Serial Number: Z840AM58 LU WWN Device Id: 5 000c50 08744c3ee Firmware Version: AR15 User Capacity: 8,001,563,222,016 bytes [8.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5980 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ACS
-
madpoet started following Problems with the Cremax trays, Recovering a drive question, [SOLVED] Recovering after the hurricane... something is badly wrong. and 2 others
-
So I had a drive that appeared to go south on me. Swapped it out with a new one and rebuilt the array, but since I had an open slot I put the old drive in intending to try and see if it was really bad. Since I haven't been paying attention I didn't realize that preclear is screwy right now (or so I gather). When I try and use Unassigned Devices I get this: bad superblock on /dev/sdb1 The drive shows as xfs and really all I want to do is format and stress test it. What's a good option to do that with now?
-
http://www.tigerdirect.com/applications/searchtools/item-Details.asp?EdpNo=127103&sku=40090194&SRCCODE=3WWEBEML782&utm_source=EML&utm_medium=main&utm_campaign=3WWEBEML782&ecm=T2qrlh7IBDxv6Me318ja88p18hCkQDHIvXa2uUcvYFJ3e3xZWZglqAUT00P8Ilxu&elqTrackId=348d406a24054878b469f98d2fcec8e1&elq=b823ed6fed134c26818a1d463edfabe6&elqaid=967&elqat=1&elqCampaignId=752 Yes I know it's the external drive, crack it open and pull it out I've done that with 3.
-
"Error: layers from manifest don't match image configuration"
madpoet replied to madpoet's topic in Docker Engine
Thank you seems to have solved it. -
So I upgraded to the latest unRaid stable, and was futzing around with my Docker images and checked for updates. They all say they need an update but when I try and do it I get the following after it pulls the image: "Error: layers from manifest don't match image configuration". I don't know what I did wrong (I assume it was my fault somewhere) but now I'm stuck unable to perform any upgrades. Normally I'd shrug it off and try to start over but I've got a pretty massive Plex config in there that I really, really don't want to lose. Any suggestions? Thanks, Paul
-
Thanks just found that on another thread and updated. Everything is working again