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.

Red dot on little drive, remove drive, copy back to array?

Featured Replies

I put in an old janky drive, and its got a red dot now. I'd like to copy it's contents back to the array, and just stop using the drive. Is there a slick way to copy that discs contents back to the array, and permanently remove the drive?

Just replace the drive with a good one and UnRAID will automatically rebuild with the contents of the drive.  That's why you've got a parity drive -- so that it, together with your other drives, can reconstruct the contents of any one failed drive.

 

  • Author

I'd like to remove the drive and not replace it.

Pretty sure the only way is to manually move the data using the ghost drive, then start a new configuration (initconfig).

  • Author

When you say "manually move data," does that mean I need to drag each folder over? Is there a slick(er) way to do this? There's a lot of folders, and it seems to me that there should be an easier way to do this.

 

Pretty sure the only way is to manually move the data using the ghost drive, then start a new configuration (initconfig).

Log into your server via telnet and use midnight commander to do it - type

 

mc

 

And hit enter.  Then in the left pane, select /mnt/diskx (your dud disk) and in the right, select /mnt/diskx (destination disk)

 

On the left pane, highlight everything you want to copy by pressing insert a bunch of times (you will see it highlight) and then hit F6 (from memory) to 'renmov' everything to the other disk.

This will preserve correct permissions: "sudo -u nobody mc"

  • Author

It seems like:

/mnt/disk7/Other video/C-Nav/docs/249 prework.pdf

 

is the same file as

/mnt/user/Other video/C-Nav/docs/249 prework.pdf

 

But, from midnight commander (mc) I want to do a RenMove F6? I noticed that when I delete something from

/mnt/disk7/Other video/C-Nav/docs/blah.txt

 

It also disappears from

/mnt/user/Other video/C-Nav/docs/blah.txt

 

I was thinking this shouldn't happen because the disk7 has a red dot and is disabled.

 

I don't want to delete my stuff here...

It seems like:

/mnt/disk7/Other video/C-Nav/docs/249 prework.pdf

 

is the same file as

/mnt/user/Other video/C-Nav/docs/249 prework.pdf

 

But, from midnight commander (mc) I want to do a RenMove F6? I noticed that when I delete something from

/mnt/disk7/Other video/C-Nav/docs/blah.txt

 

It also disappears from

/mnt/user/Other video/C-Nav/docs/blah.txt

 

I was thinking this shouldn't happen because the disk7 has a red dot and is disabled.

 

I don't want to delete my stuff here...

 

you are copying to a user share , and thus the disk you are copying from is part of the share - and by default the files already exist on it.

 

 

i previously had to follow these steps(my example disk 2 is red balled)

 

1. On web management page for configuring user shares, remove disk 2 from inclusion in any shares (or exclude it) (eg. disk1,disk2,disk4 -> disk1,disk4)

2. open up MC , and browse to the /mnt/disk2 folder on both windows. rename all the primary share folders (eg movies/series/music) to movies_ / series_ / Music_

3. once done, open the renamed folder on the left, and your destination disk / user share on the right, and move the files inside over using F6. Should not encounter any duplicates any more. Repeat as neccesary for all share folders

 

4. Once all files is moved (verified via main page that the drive is almost empty ( mine had max 30MB on it), you still need to reset the array configuration(utils -> new config), and rebuild it excluding the affected drive (keeping your parity drive exactly the same drive as before...)

 

 

Do keep in mind - your system is currently at risk, and will only be free from data loss once step 3 is completed

 

I was thinking this shouldn't happen because the disk7 has a red dot and is disabled.

unRAID simulated the disabled disk using parity and ALL THE OTHER DATA DISKS.  Even though the physical disk is disabled, you can still read and write to it.

 

/mnt/user/whatever is just another view of /mnt/disk*/whatever.  The files you see are EXACTLY the same, as /mnt/user is just a view of the files (another way of listing them, somewhat similar to linked directories or shortcuts in windows)  This view is still in place even when a single physical disk is disabled.

 

As described, if another disk were to fail now, you would lose the data on both it and the one currently disabled.    When attempting to move files from one /mnt/disk* to another, it is probably best if you do not use the /mnt/user locations as destinations.  it will make it much easier to ensure you are moving the files to where you want.

 

Joe L.

 

 

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.