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.

[Solved(ish)] Errors found on disk - what to do?

Featured Replies

Built the beginnings of an unraid server (5.0b4) yesterday.  Have a 2TB parity drive, 2TB data drive, and a 1TB data drive.  Started copying data over from my WHS box.  Found that the 2TB data drive had 64 errors during an automated parity check.  Relevant log here.

 

I did not do a "preclear" on any of the drives before adding them to the pool because I wasn't aware of the process at the time.  I have copied about 1TB onto the unraid server at this point.  Should I start over, doing a preclear of the drives first?  Is there another way to test the integrity of the drives?  Is there any way to know exactly what is damaged so I can re-copy it over?  What is the recommended course of action here?

  • Author

I guess there is no procedure for narrowing down drive errors?

 

With my WHS box on its last legs, I couldn't wait around for advise.  I stopped the server and am now pre-clearing my three drives.  The 1TB completed with no issues, and the 1st 2TB is running now.

Disk1 had problems. Your current procedure may fix it.

  • Author

This isn't good.  I think it's a problem with the preclear script, not the drive itself.  The script is still running, but I get this message refreshing every few seconds.  Should I force it to quit or just let it keep going?

IMG_20110224_082217.jpg.101c0866034ea596f9310c9f98b0dbac.jpg

This isn't good.  I think it's a problem with the preclear script, not the drive itself.  The script is still running, but I get this message refreshing every few seconds.  Should I force it to quit or just let it keep going?

If "malloc" is failing, you've run out of free RAM.

 

I'd quit it.  There are options to limit the number of blocks read, and the size of the blocks read and written.

 

      -w size  = write block size in bytes

 

      -r size  = read block size in bytes

 

      -b count = number of blocks to read at a time

 

I'd try something like

-w 1M -r 1M -b 10

Joe L.

 

 

Joe L.

  • Author

Weird.  I've got 2GB of RAM so I shouldn't be running out.  The script was still making progress when I left for work.  If it's still going when I get home, I may just let it finish on its own.

  • Author

When I got home the preclear had completed with no problems that I could see.  I suppose this is "solved" for now.

Archived

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

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.