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.

Issues with Disks & now Array $ Cache showing as "new devices"

Featured Replies

Long story short, or short story long, I had a 1 disk failure on an extremely old drive replaced it with a new larger drive (no problem) rebuilt just fine. Then another drive went down and that was replaced and rebuilt fine. 

 

Now yesterday, I had UDMA CRC errors on disk2, checked cables and power cables on all drives (I messed up and didn't document the drive locations when build) and it came back for a little while and happened again, this time the drive became "disabled".  Now today disk 6 became disabled and had an error along the lines of (wrong filesystem or disk format) well that cant be right it was just working.  Fast forward to now, I have both disks visible in the console but they are "new devices" and now my cache drives are all "new devices"

 

Am I cooked here?

flair-diagnostics-20250220-2033.zip

Solved by JorgeB

  • Community Expert

It should be recoverable, assuming the emulated disks are mounting or can be fixed, first post the output from 

btrfs fi show

 

  • Author
6 hours ago, JorgeB said:

It should be recoverable, assuming the emulated disks are mounting or can be fixed, first post the output from 

btrfs fi show

 

Here you go.

Label: none  uuid: 5fd43c19-2e69-4009-9ee4-b3a556723527
        Total devices 4 FS bytes used 904.37GiB
        devid    1 size 3.64TiB used 439.96GiB path /dev/nvme2n1p1
        devid    2 size 3.64TiB used 439.96GiB path /dev/nvme1n1p1
        devid    3 size 931.51GiB used 356.00GiB path /dev/nvme0n1p1
        devid    4 size 931.51GiB used 356.00GiB path /dev/nvme3n1p1

 

  • Community Expert

To make sure the existing pool is reimported, do this:

 

on main click on the first device for that pool and then "remove pool"
back on main, create a new pool with the same name and number of slots
assign the pool devices, leave the filesystem set to auto

 

Now also unassign both disabled array disks and start the array to import the pool and see if the emulated disks are mounting, post new diags after that.

 

 

  • Author
32 minutes ago, JorgeB said:

To make sure the existing pool is reimported, do this:

 

on main click on the first device for that pool and then "remove pool"
back on main, create a new pool with the same name and number of slots
assign the pool devices, leave the filesystem set to auto

 

Now also unassign both disabled array disks and start the array to import the pool and see if the emulated disks are mounting, post new diags after that.

 

 

That worked for the cache drives. Thank you. Here is the new diag for the array.

flair-diagnostics-20250221-1008.zip

  • Community Expert

Those diags are with the array stopped, post new ones with the array started, with the disks still unassigned for now.

  • Author

Oh sorry about that, here is the one with the array started but in maintenance mode if that's not ok let me know. Appreciate the assistance here.

flair-diagnostics-20250221-1331.zip

  • Community Expert

Needs to be in normal mode, disks don't mount in maintenance mode, but you can also check yourself, make sure both emulated disks are mounting, and that contents look correct, also look for a lost+found folder, if there's one, check for any lost files there, if all looks good you can then rebuild both disks

  • Author
44 minutes ago, JorgeB said:

Needs to be in normal mode, disks don't mount in maintenance mode, but you can also check yourself, make sure both emulated disks are mounting, and that contents look correct, also look for a lost+found folder, if there's one, check for any lost files there, if all looks good you can then rebuild both disks

Got ya here you go.

flair-diagnostics-20250221-1456.zip

  • Community Expert

Looks OK, if contents look good, you can rebuild both disks.

  • Author

Thanks for the confirmation. Still getting the UDMA CRC errors on disk2, so I think that drive needs to be replaced.

  • Community Expert
48 minutes ago, BIGtoeknee said:

Still getting the UDMA CRC errors on disk2, so I think that drive needs to be replaced.

Not convinced as the CRC errors are rarely the drive itself.    I would suggest running the extended SMART test, and if that fails the drive should be replaced.

  • Community Expert
  • Solution
17 hours ago, BIGtoeknee said:

Still getting the UDMA CRC errors on disk2

Try replacing the SATA cable and/or using a different port.

  • 7 months later...
On 2/22/2025 at 1:35 AM, JorgeB said:

To make sure the existing pool is reimported, do this:

 

on main click on the first device for that pool and then "remove pool"
back on main, create a new pool with the same name and number of slots
assign the pool devices, leave the filesystem set to auto

 

Now also unassign both disabled array disks and start the array to import the pool and see if the emulated disks are mounting, post new diags after that.

 

 



Hey mate,

I had a similar issue. Many thanks. this worked for me too. <3 Very much appreciated that the googling brought this post up.

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.