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.

Replacing a failed pool device, trying to replace and rebuild parity - noob help

Featured Replies

Solved by JorgeB

  • Author

I have seen the CRC errors, unfortunately all of the SATA in my PC ATM are being used. Is there any risk of harm or damage from the bad cable/CRC errors to the dive (or anything else)? I'd have to do some cable management, but if it has the potential to cause damage I'd def do it, but I'm afraid if i start moving this around and plugging/unplugging the mess I made inside the server I'll mess something up and cause more issues >< (Google seems to say it can degrade network performance and cause data retransmissions, but doesn't mention damage).

Is http://paypal.me/blackjohnnie still a good way to tip?

No, CRC errors won't physically damage the SSD or anything else, and they don't silently corrupt data. Each transfer is checked, and when a CRC error is detected the command is retried. That is why you only see the counter go up. (What Google showed you is about network CRC errors, but it's the same idea: bad transfers get detected and resent.)

The risk is reliability, not damage. If the connection gets worse, the retries can fail. This already happened at your last boot: some reads were aborted and the link was slowed to 3Gb/s. When reads or writes fail, the device can drop offline, or btrfs can make the pool read-only. Right now the pool has a single device, so there is no second copy, and adding the new SSD makes Unraid read all the data from the current one. That's why I'd fix this before adding the mirror.

You don't need a free port, just replace the SATA cable on that SSD and plug it back into the same port. Or swap the cables/ports between the current cache SSD and the new SSD. The new one is on an onboard port and has zero CRC errors, so the current cache device would then use that good port and cable. Do it with the server powered off and only touch those two cables.

After that, just keep an eye on it. Unraid will send a notification if the CRC count goes up again. The count never resets, so all that matters is whether it keeps going up.

16 minutes ago, NewGuyEddie said:

Is http://paypal.me/blackjohnnie still a good way to tip?

Yes, thanks!

  • Author

Payment sent - The dives are balancing now (I think? not sure how to check, but I see device 1 reading, and both drives writing). Once the activity dies down and it appears completed I'll post diags to confirm everything - thanks for your help and patience!

Also was able to swap cable, server booted without any CRC errors!

Edited by NewGuyEddie
spelling

Sounds good, please post new diags when it's done. And thanks for the donation, much appreciated!

Diags look good, the pool is now raid1 again with both devices, no missing members, and all the data is there. The balance finished without errors.

However, the current cache device is still getting CRC errors, they happened when the pool was mounted, so after the boot, the count went from 87 to 91, and the link was again slowed down to 3Gb/s. Since you already replaced the cable, the problem may be that port on the add-on controller. I recommend, with the server powered off, swapping the SATA ports of the two cache devices, so the current one goes to the onboard port the new SSD is using now, and the new one goes to the add-on controller port. Then keep an eye on both: if the CRC errors now appear on the new SSD, it's the port, and it's best to avoid using it.

The pool is redundant now, so these errors are less of a concern, but I would still run a scrub to confirm all is good: click on the pool device on the Main page and use Scrub.

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.