Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Docker wont start and cache mounted read only?!?

Featured Replies

I have been having issues with docker lately.
Upon reboot it does not auto start.  docker file at 75% full
Manually starting has worked once per boot.  shutting down docker and re-starting does not work. failed to start error.

Last night docker service shut down.
Reboot machine.
Docker wont start, even manually. 

 

I just got a message from "fix common problems" it says my cache is mounted read only?!?

Unraid 6.12.4

diags below

 

from dmesg:

[  147.302393] BTRFS error (device sdc1): unable to find ref byte nr 4726796288 parent 0 root 5  owner 110749390 offset 20393984

...

[  147.302598] BTRFS: error (device sdc1: state A) in __btrfs_free_extent:3067: errno=-2 No such entry
[  147.302944] BTRFS info (device sdc1: state EA): forced readonly
[  147.302948] BTRFS error (device sdc1: state EA): failed to run delayed ref for logical 4726796288 num_bytes 4096 type 178 action 2 ref_mod 1: -2
[  147.302952] BTRFS: error (device sdc1: state EA) in btrfs_run_delayed_refs:2144: errno=-2 No such entry
[  147.303304] BTRFS info (device sdc1: state EMA): turning on async discard
[  147.303307] BTRFS error (device sdc1: state EMA): Remounting read-write after error is not allowed

[  154.069448] BTRFS: device fsid 340edf27-5c02-45de-a544-66414f31295d devid 1 transid 1041182 /dev/loop2 scanned by mount (18956)
[  154.069842] BTRFS info (device loop2): using crc32c (crc32c-intel) checksum algorithm
[  154.069852] BTRFS info (device loop2): using free space tree
[  154.076436] BTRFS info (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 158, gen 0
[  154.116183] BTRFS info (device loop2): enabling ssd optimizations
[  154.116189] BTRFS info (device loop2): start tree-log replay
[  154.116192] BTRFS warning (device loop2): log replay required on RO media
[  154.116854] BTRFS error (device loop2): open_ctree failed
[  154.209514] loop2: detected capacity change from 0 to 2097152
[  154.214563] BTRFS: device fsid 19370b97-4ce9-472f-b454-3cd5fb59f6af devid 1 transid 16168 /dev/loop2 scanned by mount (19003)
[  154.214950] BTRFS info (device loop2): using crc32c (crc32c-intel) checksum algorithm
[  154.214960] BTRFS info (device loop2): using free space tree
[  154.220240] BTRFS info (device loop2): enabling ssd optimizations
...
[  174.250968] sd 11:0:0:0: device_block, handle(0x0011)
[  175.498424] sd 11:0:0:0: device_unblock and setting to running, handle(0x0011)
[  175.505760] sd 11:0:0:0: Power-on or device reset occurred
[  199.437504] loop3: detected capacity change from 0 to 157286400
[  199.439748] BTRFS: device fsid 340edf27-5c02-45de-a544-66414f31295d devid 1 transid 1041182 /dev/loop3 scanned by mount (25474)
[  199.440171] BTRFS info (device loop3): using crc32c (crc32c-intel) checksum algorithm
[  199.440180] BTRFS info (device loop3): using free space tree
[  199.441469] BTRFS info (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 158, gen 0
[  199.446427] BTRFS info (device loop3): enabling ssd optimizations
[  199.446432] BTRFS info (device loop3): start tree-log replay
[  199.446435] BTRFS warning (device loop3): log replay required on RO media
[  199.447325] BTRFS error (device loop3): open_ctree failed


is my cache drive failiing?
I found a similar issue with another user, his drive was dying.

 

EDIT:

i just got back from the store and installed a new 2tb nvme.

not sure how to do a cache swap though.
spaceinvaderone video on the subject requires docker working and using krusader.

 

EDIT:
6 hours later
I get a failed disk error on my parity 0 drive
rebooted, cant start array in maintenance mode.
more diags attached.


EDIT:
purchased an NVME its mounted as unassigned.
currently cp -Rfvp /mnt/cache/* /mnt/disk7/CACHE-BACKUP/

big-z-diagnostics-20240204-0906.zip

big-z-diagnostics-20240204-1617.zip

Edited by TRusselo

Solved by TRusselo

  • Author
  • Solution

My cache was bad.

purchased a new drive at store

 

started array with VM OFF / DOCKER OFF

 

terminal

mkdir /mnt/disk7/CACHE-BACKUP/
cp -Rfvp /mnt/cache/* /mnt/disk7/CACHE-BACKUP/
wait

stop array. remove old cache drive. start array.

stop array. add new cache drive. start array.
cp -Rfvp /mnt/disk7/CACHE-BACKUP/* /mnt/cache/

start array.  enable docker, enable VM

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...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.