March 23, 20251 yr Hey guys, im not a power user but have been running Unraid for 4-5 years now. I'm having an issue after I upgraded to 7.0.1. I had a failed drive and I was using unassigned devices to keep it going until I can afford to replace the failed drive. After the upgrade the disk has moved to "Historical" as seen in the picture attached. Now im unable to start my array. It just says "cache - too many wrong or missing devices" when I try. Is there a way I can fix this until I can get a new drive in the server? Any help is appreciated thank you. EDIT: I've tried to search the forums and didn't find a solutions. If there's been a similar issue please link! Edited March 23, 20251 yr by SeanFromYYC
March 23, 20251 yr Community Expert You are likely to get better informed feedback if you attach your system’s diagnostics (with everything in the one zip file) to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.
March 23, 20251 yr Author Thank you! I have attached the diagnostics zip file.media-diagnostics-20250323-1434.zip
March 24, 20251 yr Community Expert Does the missing device show up in the BIOS? Also post the output from: btrfs fi show
March 26, 20251 yr Author On 3/24/2025 at 2:04 AM, JorgeB said: Does the missing device show up in the BIOS? Also post the output from: btrfs fi show Hey, the missing device is currently unplugged and was previously able to be run via the parity drive and unassigned devices plugin. I think im saying that correctly but im not sure 100% as im not a power user. Which brings me to my next question. I Tried ot run "btrfs fi show" in the command terminal but it does not return anything. Still trying to figure this issue out as im not sure why upgrading the OS to a new version broke it. I was planning to get a replacement drive asap to restore the effected drive.
March 27, 20251 yr Community Expert 9 hours ago, SeanFromYYC said: I Tried ot run "btrfs fi show" in the command terminal but it does not return anything. Try instead: lsblk -lo TYPE,PARTN,NAME,START,SIZE,PTTYPE,PARTTYPE,FSTYPE,LABEL,SERIAL
March 27, 20251 yr Author 14 hours ago, JorgeB said: Try instead: lsblk -lo TYPE,PARTN,NAME,START,SIZE,PTTYPE,PARTTYPE,FSTYPE,LABEL,SERIAL Ok thank you, this is what it returned: TYPE PARTN NAME START SIZE PTTYPE PARTTYPE FSTYPE LABEL SERIAL loop loop0 557.3M squashfs loop loop1 89.2M squashfs disk sda 28.6G dos 4C530001090621106474 part 1 sda1 2048 28.6G dos 0xc vfat UNRAID disk sdb 5.5T gpt WD-WX72D509K1NF part 1 sdb1 64 5.5T gpt 0fc63daf-8483-4772-8e79-3d69d8477de4 xfs disk sdc 5.5T gpt WD-WX72D506VX6K part 1 sdc1 64 5.5T gpt 0fc63daf-8483-4772-8e79-3d69d8477de4 xfs disk sdd 5.5T gpt WD-WX92DA1NF231 part 1 sdd1 64 5.5T gpt 0fc63daf-8483-4772-8e79-3d69d8477de4 xfs
March 28, 20251 yr Community Expert Solution I assume those are the array devices, you should be able to start the array after clicking on the pool and selecting "remove pool"
March 28, 20251 yr Author 11 hours ago, JorgeB said: I assume those are the array devices, you should be able to start the array after clicking on the pool and selecting "remove pool" Oh man what a simple fix! I removed the cache from the pool and it fired right up. Thanks so much for teaching this noob. I was just afraid of doing something harmful to my array as I used it to backup and cloud my own personal company and files. I appreciate the help and have marked it as solved. Cheers
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.