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.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

After upgrading from 6.2.1 to 6.2.3 cache drive is unmountable

Tim2011
in General Support

Featured Replies

Hi,

 

After upgrading Unraid my SSD cache drive is unmountable. Any ideas?

 

Nov 4 10:09:37 Tower kernel: ata5: SATA max UDMA/133 abar m1024@0xfd60b000 port 0xfd60b300 irq 19

Nov 4 10:09:37 Tower kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

Nov 4 10:09:37 Tower kernel: ata5.00: ATA-8: KINGSTON SV300S37A120G, 50026B7849035A36, 583ABBF0, max UDMA/133

Nov 4 10:09:37 Tower kernel: ata5.00: 234441648 sectors, multi 1: LBA48 NCQ (depth 31/32), AA

Nov 4 10:09:37 Tower kernel: ata5.00: configured for UDMA/133

Nov 4 10:09:37 Tower kernel: sd 5:0:0:0: [sdf] 234441648 512-byte logical blocks: (120 GB/112 GiB)

Nov 4 10:09:37 Tower kernel: sd 5:0:0:0: [sdf] Write Protect is off

Nov 4 10:09:37 Tower kernel: sd 5:0:0:0: [sdf] Mode Sense: 00 3a 00 00

Nov 4 10:09:37 Tower kernel: sd 5:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Nov 4 10:09:37 Tower kernel: sdf: sdf1

Nov 4 10:09:37 Tower kernel: sd 5:0:0:0: [sdf] Attached SCSI disk

Nov 4 10:09:37 Tower kernel: BTRFS: device fsid 7f58c17f-53a3-4742-af68-7ea1f3230070 devid 1 transid 1341192 /dev/sdf1

Nov 4 10:09:39 Tower emhttp: KINGSTON_SV300S37A120G_50026B7849035A36 (sdf) 117220792

Nov 4 10:09:39 Tower emhttp: import 30 cache device: sdf

Nov 4 10:09:41 Tower emhttp: shcmd (48): set -o pipefail ; mount -t btrfs -o noatime,nodiratime /dev/sdf1 /mnt/cache |& logger

Nov 4 10:09:41 Tower kernel: BTRFS info (device sdf1): disk space caching is enabled

Nov 4 10:09:41 Tower kernel: BTRFS critical (device sdf1): corrupt leaf, bad key order: block=12107776,root=1, slot=55

Nov 4 10:09:41 Tower kernel: BTRFS critical (device sdf1): corrupt leaf, bad key order: block=12107776,root=1, slot=55

Nov 4 10:09:41 Tower root: mount: wrong fs type, bad option, bad superblock on /dev/sdf1,

Nov 4 10:21:30 Tower emhttp: shcmd (940): /usr/sbin/hdparm -y /dev/sdf &> /dev/null

Nov 4 10:21:49 Tower emhttp: shcmd (964): /usr/sbin/hdparm -S0 /dev/sdf &> /dev/null

Nov 4 10:22:20 Tower emhttp: KINGSTON_SV300S37A120G_50026B7849035A36 (sdf) 117220792

Nov 4 10:22:20 Tower emhttp: import 30 cache device: sdf

Nov 4 10:22:21 Tower emhttp: KINGSTON_SV300S37A120G_50026B7849035A36 (sdf) 117220792

Nov 4 10:22:21 Tower emhttp: import 30 cache device: sdf

Nov 4 10:22:22 Tower emhttp: KINGSTON_SV300S37A120G_50026B7849035A36 (sdf) 117220792

Nov 4 10:22:22 Tower emhttp: import 30 cache device: sdf

Nov 4 10:22:58 Tower emhttp: shcmd (1085): set -o pipefail ; mount -t btrfs -o noatime,nodiratime /dev/sdf1 /mnt/cache |& logger

Nov 4 10:22:58 Tower kernel: BTRFS info (device sdf1): disk space caching is enabled

Nov 4 10:22:58 Tower kernel: BTRFS critical (device sdf1): corrupt leaf, bad key order: block=12107776,root=1, slot=55

Nov 4 10:22:58 Tower kernel: BTRFS critical (device sdf1): corrupt leaf, bad key order: block=12107776,root=1, slot=55

Nov 4 10:22:58 Tower root: mount: wrong fs type, bad option, bad superblock on /dev/sdf1,

Nov 4 10:33:19 Tower emhttp: shcmd (1402): /usr/sbin/hdparm -y /dev/sdf &> /dev/null

Nov 4 10:33:24 Tower emhttp: shcmd (1426): /usr/sbin/hdparm -S0 /dev/sdf &> /dev/null

Nov 4 11:18:25 Tower emhttp: shcmd (2485): /usr/sbin/hdparm -y /dev/sdf &> /dev/null

Nov 4 20:13:09 Tower emhttp: shcmd (14814): /usr/sbin/hdparm -S0 /dev/sdf &> /dev/null

Nov 4 20:15:58 Tower emhttp: shcmd (14973): /usr/sbin/hdparm -S0 /dev/sdf &> /dev/null

Nov 4 20:16:52 Tower emhttp: KINGSTON_SV300S37A120G_50026B7849035A36 (sdf) 117220792

Nov 4 20:16:52 Tower emhttp: import 30 cache device: sdf

Nov 4 20:16:53 Tower emhttp: KINGSTON_SV300S37A120G_50026B7849035A36 (sdf) 117220792

Nov 4 20:16:53 Tower emhttp: import 30 cache device: sdf

Nov 4 20:16:53 Tower emhttp: KINGSTON_SV300S37A120G_50026B7849035A36 (sdf) 117220792

Nov 4 20:16:53 Tower emhttp: import 30 cache device: sdf

Nov 4 20:17:01 Tower emhttp: KINGSTON_SV300S37A120G_50026B7849035A36 (sdf) 117220792

Nov 4 20:17:01 Tower emhttp: import 30 cache device: sdf

Nov 4 20:17:03 Tower emhttp: KINGSTON_SV300S37A120G_50026B7849035A36 (sdf) 117220792

Nov 4 20:17:03 Tower emhttp: import 30 cache device: sdf

Nov 4 20:18:02 Tower emhttp: KINGSTON_SV300S37A120G_50026B7849035A36 (sdf) 117220792

Nov 4 20:18:02 Tower emhttp: import 30 cache device: sdf

Nov 4 20:19:01 Tower emhttp: KINGSTON_SV300S37A120G_50026B7849035A36 (sdf) 117220792

Nov 4 20:19:01 Tower emhttp: import 30 cache device: sdf

Nov 4 20:20:01 Tower emhttp: KINGSTON_SV300S37A120G_50026B7849035A36 (sdf) 117220792

Nov 4 20:20:01 Tower emhttp: import 30 cache device: sdf

Nov 4 20:21:01 Tower emhttp: KINGSTON_SV300S37A120G_50026B7849035A36 (sdf) 117220792

Nov 4 20:21:01 Tower emhttp: import 30 cache device: sdf

Nov 4 20:21:25 Tower emhttp: KINGSTON_SV300S37A120G_50026B7849035A36 (sdf) 117220792

Nov 4 20:21:25 Tower emhttp: import 30 cache device: sdf

Nov 4 20:22:01 Tower emhttp: KINGSTON_SV300S37A120G_50026B7849035A36 (sdf) 117220792

Nov 4 20:22:01 Tower emhttp: import 30 cache device: sdf

Nov 4 20:22:18 Tower emhttp: shcmd (15230): set -o pipefail ; mount -t btrfs -o noatime,nodiratime /dev/sdf1 /mnt/cache |& logger

Nov 4 20:22:18 Tower kernel: BTRFS info (device sdf1): disk space caching is enabled

Nov 4 20:22:18 Tower kernel: BTRFS critical (device sdf1): corrupt leaf, bad key order: block=12107776,root=1, slot=55

Nov 4 20:22:18 Tower kernel: BTRFS critical (device sdf1): corrupt leaf, bad key order: block=12107776,root=1, slot=55

Nov 4 20:22:18 Tower root: mount: wrong fs type, bad option, bad superblock on /dev/sdf1,

  • Quote
    • Community Expert

    ... Any ideas?

    Not without a diagnostic. why do we have to ask?
  • Quote

    • Archived

    This topic is now archived and is closed to further replies.

    Go to topic listing

    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.