Everything posted by dboonthego
-
Re: Format XFS on replacement drive / Convert from RFS to XFS (discussion only)
How do you reformat an existing xfs disk as xfs? Do these steps twice by formatting with a different filesystem first, then putting it back to xfs?
-
Re: Format XFS on replacement drive / Convert from RFS to XFS (discussion only)
Interesting quagmire I got myself into. Thanks. I didn't think unRAID allowed user shares with reserved names like flash, disk1, disk2, etc.
-
Re: Format XFS on replacement drive / Convert from RFS to XFS (discussion only)
Makes complete sense. I formatted disk2 to XFS, but my data is still showing up in windows explorer for \\tower\disk2. Why is that? If I look from the console /mnt/disk2 is empty as expected. Is it being emulated from parity? At what point can I trust what windows explorer says?
-
Re: Format XFS on replacement drive / Convert from RFS to XFS (discussion only)
This will copy the contents of disk1 to disk2; change the disk # as needed for your situation. Include the trailing slashes. I forgot to include them which altered my destination folder structure. rsync -avPX /mnt/disk1/ /mnt/disk2/ More info here: http://lime-technology.com/wiki/index.php/Upgrading_to_UnRAID_v6#Converting_Drives_from_ReiserFS_to_XFS
-
Re: Format XFS on replacement drive / Convert from RFS to XFS (discussion only)
I'm sure that's what I did. Thanks! I want to copy the data back to disk2 after the format. Considering my mistake earlier, this should do it correct? rsync -avPX /mnt/disk3/disk2/ /mnt/disk2/
-
Re: Format XFS on replacement drive / Convert from RFS to XFS (discussion only)
I've recently upgraded my unRAID server and while I'm at it, I'd like to switch from reiserfs to XFS. I added a new pre-clear XFS disk3 to the array and executed rsync -avPX /mnt/disk2/ /mnt/disk3/ from the console to kick off the copy. Two questions. 1. The folder structure on the copy to disk3 looks like this: /mnt/disk3/disk2/myDataFolders. Did I foul up the command? How would I get it to copy as /mnt/disk3/myDataFolders? 2. The copy is parity protected (by design), but is there a best practice to bypass this for the sake of increasing transfer speed? I understand there is a risk of data loss.
-
Preclear plugin
Try starting the array with the disk unassigned. The disk assignments don't actually get updated until the array is started. That was it. Thanks!
-
Preclear plugin
I just installed yesterday, the log has just 4 lines. Feb 02 23:53:05 preclear_disk_sdd_11145: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --notify 3 --frequency 2 --cycles 3 --no-prompt /dev/sdd Feb 02 23:53:05 preclear_disk_sdd_11145: Preclear Disk Version: 0.8.4-beta Feb 02 23:53:05 preclear_disk_sdd_11145: S.M.A.R.T. info type: default Feb 02 23:53:05 preclear_disk_sdd_11145: S.M.A.R.T. attrs type: default It looks like preclear does not want to clear my drive that has been part of the array already. I want to rebuild disk2 from parity back to itself, but I want to run a few preclear cycles it before doing that; the drive is suspect. The array is stopped and disk2=no device. If I try to clear this disk, it gets stuck. I have a brand new unformatted unassigned disk that has never been part of the array. I am able to successfully kick off a preclear of this disk. Did I miss a step or is this not normal? I'm running unRAID v6.2.4
-
Preclear plugin
I just installed yesterday, the log has just 4 lines. Feb 02 23:53:05 preclear_disk_sdd_11145: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --notify 3 --frequency 2 --cycles 3 --no-prompt /dev/sdd Feb 02 23:53:05 preclear_disk_sdd_11145: Preclear Disk Version: 0.8.4-beta Feb 02 23:53:05 preclear_disk_sdd_11145: S.M.A.R.T. info type: default Feb 02 23:53:05 preclear_disk_sdd_11145: S.M.A.R.T. attrs type: default
-
Preclear plugin
Was there a solution for this? I'm experiencing the same issue.
-
Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array
I had the exact same issue. Cycling the setting resolved it for me.
-
Upgrading unRAID from Version 5 to Version 6
Thanks Frank. I appreciate your response and you have answered my question. I didn't necessarily want to go that route and will copy the files, but for the sake of educating myself to understand how unRAID works, assume my flash stick is dead or lost. What kind of issues would I expect to run into? Network settings and a server name seems easy enough, so I'm more curious about recreating disk.cfg and sharename.cfg's. If I was forced to do that, is it mission critical that the share settings be exactly as they were before? Or would I be free to change things like highwater vs fillup, or even the share name? Does a share name change require renaming the folders on each disk? These questions might be getting off topic, but thank you for your input.
-
Upgrading unRAID from Version 5 to Version 6
I have been using the free 3-disk v5.0-beta13 version of unRAID. I'm upgrading to 6.2.4. The only hardware I'm keeping is the disk drives; everything else is new including the flash stick. My old server was barebones with 3 shares and no plugins. The new flash stick boots and I have registered for a 30-day trial. I know my previous device-to-serial assignments, but have not assigned them and started the array yet. http://lime-technology.com/wiki/index.php/Upgrading_to_UnRAID_v6 "There are a few configuration files that are safe to keep and restore, ident.cfg, network.cfg, share.cfg, and any .cfg files in the config/shares folder. These files hold your network settings and identification, and your share settings, and are safe to bring forward. They will help you get back on the network quicker!" All that's left to do is copy some .cfg files and start the array, right? Are there any negative effects if I don't copy them and re-create the shares manually? Also, I suspect data disk 2 might be failing, but, I don't know for sure. In the past, problems with this disk have been tied to the SATA cable. The SMART check seems to pass. Maybe the new mobo and cables will help. I do have a same-size replacement drive if needed. How should I handle disk 2 during the upgrade? Are there any drive health assessment tests I can do?