Sandwich Posted September 26, 2021 Share Posted September 26, 2021 I've been emptying out my largest data drive (6Tb), moving its contents over to other data drives, in preparation for making it a second parity disk. In unBalance, there were two top-level directories listed on the drive: /Public and /system. The /system/docker/docker.img file was the only file under /system that I could see. I moved both directories to other drives, letting unBalance decide which drives to use. It seemed to go fine, and in Settings -> Docker, the drive-agnostic path should still be the same: /mnt/user/system/docker/docker.img Nevertheless, Docker hasn't been able to successfully start since the move. Any ideas? Diagnostics attached. cube-diagnostics-20210926-2115.zip Quote Link to comment
Squid Posted September 27, 2021 Share Posted September 27, 2021 Port multipliers are not particularly recommended (Your mileage will vary) Sep 25 22:56:32 Cube kernel: ata10.04: SATA link up 6.0 Gbps (SStatus 133 SControl 330) Sep 25 22:56:32 Cube kernel: ata10.00: ATA-9: WDC WD30EZRX-00D8PB0, WD-WMC4N1244814, 80.00A80, max UDMA/133 Sep 25 22:56:32 Cube kernel: ata10.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 32), AA Sep 25 22:56:32 Cube kernel: ata10.00: configured for UDMA/133 Sep 25 22:56:32 Cube kernel: ata10.02: NCQ Send/Recv Log not supported Sep 25 22:56:32 Cube kernel: ata10.02: ATA-9: ST3000VN007-2E4166, Z730JMM1, SC60, max UDMA/133 Sep 25 22:56:32 Cube kernel: ata10.02: 5860533168 sectors, multi 0: LBA48 NCQ (depth 32), AA Sep 25 22:56:32 Cube kernel: ata10.02: NCQ Send/Recv Log not supported Sep 25 22:56:32 Cube kernel: ata10.02: configured for UDMA/133 Sep 25 22:56:32 Cube kernel: ata10.03: ATA-8: WDC WD30EZRX-00AZ6B0, WD-WMC070040204, 80.00A80, max UDMA/133 Sep 25 22:56:32 Cube kernel: ata10.03: 5860533168 sectors, multi 0: LBA48 NCQ (depth 32), AA Sep 25 22:56:32 Cube kernel: ata10.03: configured for UDMA/133 Sep 25 22:56:32 Cube kernel: ata10.04: failed to read native max address (err_mask=0x1) Sep 25 22:56:32 Cube kernel: ata10.04: HPA support seems broken, skipping HPA handling Sep 25 22:56:32 Cube kernel: ata10.04: failed to enable AA (error_mask=0x1) Sep 25 22:56:32 Cube kernel: ata10.04: ATA-9: WDC WD30EZRX-00DC0B0, WD-WCC1T1703192, 80.00A80, max UDMA/133 Sep 25 22:56:32 Cube kernel: ata10.04: 5860533168 sectors, multi 0: LBA48 NCQ (depth 32) Sep 25 22:56:32 Cube kernel: ata10.04: failed to enable AA (error_mask=0x1) Sep 25 22:56:32 Cube kernel: ata10.04: configured for UDMA/133 (device error ignored) Sep 25 22:56:32 Cube kernel: ata10: EH complete Your drives attached to it are continually resetting, probably severely impacting performance. 6 hours ago, Sandwich said: Docker hasn't been able to successfully start Just delete the image and recreate it, then reinstall via Apps -> Previous Apps Quote Link to comment
Sandwich Posted September 27, 2021 Author Share Posted September 27, 2021 8 hours ago, Squid said: Port multipliers are not particularly recommended (Your mileage will vary) Your drives attached to it are continually resetting, probably severely impacting performance. "Port multipliers"? Is that the same as SATA expansion cards? I got this off Amazon: https://www.amazon.com/dp/B083WF95Q1?psc=1&ref=ppx_yo2_dt_b_product_details My MB only has like 6 SATA ports natively, so I need extra ports somehow... 8 hours ago, Squid said: Just delete the image and recreate it, then reinstall via Apps -> Previous Apps Ahh, awesome, thanks! Quote Link to comment
Recommended Posts
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.