I have been replacing a few hard drives that were failing. I followed the directions and installed a new 14tb drive, and using unbalanced I transfered one of my 6TB drives to it.

Went perfectly. I started the 2nd 4TB drive that needed to be moved and after 26 hours with almost 15 minuted my neighborhood and a 1/2 a second power glitch.

The unraid server was not attached to the backup battery because I had moved it to another room to work on.

I went into unbalance again and reran the source disk to target disk command. It looks like all the files that were supposed to be moved are still listed on the source disk.

Before I attempt to do anything what should I do. I know that most of the 4TB drive files were moved because the 14TB drive increased in size while the 4TB drive decreased.

What should be my next step.

Thanks

Just now, cwb said:

followed the directions

Which directions were those?

The reason I ask is because Unbalance is not a usual part of replacing disks, but it might be useful depending on what else you were trying to do.

Attach Diagnostics ZIP to your NEXT post in this thread.

The directions I followed were from a few YT videos, Spaceinvader and AlienTech.

I added the new drives and allowed them to be "adopted" through the unraid process.

I then wanted to move data from one of my failing drives to the new drive. That is when I used unbalance because it has the move/copy options.

That is when I had my glitch.

micah-diagnostics-20260110-0714.zip

Edited January 10Jan 10 by cwb

1 hour ago, cwb said:

The directions I followed were from a few YT videos, Spaceinvader and AlienTech.

I was hoping you might have some specific link or something that would let me know better exactly what you had done.

Still some confusion with your terminology. Adding a disk is not at all the same as replacing a disk.

If you did replace instead of add, then I guess by "adopt" you really mean rebuild.

1 hour ago, cwb said:

I then wanted to move data from one of my failing drives to the new drive.

Why didn't you rebuild that drive too? Or are you planning to remove it and shrink the array instead?

SMART reports for all array disks seems fine. Why do you think any were failing?

There are some problems going on with your cache_ssd though. Looks like it might even be readonly since your syslog share seems unwriteable and so is spamming syslog with errors about that. It does look like an actual drive error so it might need replacing.

All this unbalance and moving things around seems unnecessary even if you were really having failing disks.

3 minutes ago, trurl said:

SMART reports for all array disks seems fine. Why do you think any were failing?

And are you really adding disks, or are you replacing disks?

If you were adding, no good reason to be moving things.

And if you were replacing disks, the only reason you might move things off a disk is so you could remove it and shrink the array.