Jump to content

vettenstein

Members
  • Posts

    16
  • Joined

Posts posted by vettenstein

  1. <snip>

    10. Stop the array; we are now going to swap their assignments; when stopped, click on the dropdown for the new drive (e.g. Disk 11) and unassign it; it should notify you of 'Missing drive'

    11. Click on the dropdown for the other drive (e.g. Disk 10), the one being converted, and reassign it as the physical drive that was just added, the new drive that was empty; you will be notified of 'Wrong drive'

    12. Click on the dropdown for the slot of the new drive (e.g. Disk 11) and reassign it to the physical drive that was being converted (e.g. Disk 10); you will get more notifications of wrong or missing drives; you have just swapped the 2 drives, which is fine as they are identical (except for file system format)

    13. Important! Click on each drive name (e.g. Disk 10 and Disk 11) and change the format of the drive; if it's ReiserFS change it to XFS, if it's XFS change it to ReiserFS; it's important to swap the disk formats as well as the physical drive assignments

    14. You should see both drives listed with errors, possibly as unmountable, and a check box; click it and click the Start button to start the array; it should start up without issue and look almost identical to what it looked like before the swap, with no parity check needed; however the XFS disk is now online and its files are now being shared as they normally would; check it all if you are in doubt

     

    I'm on 6.2 and there doesn't appear to be a way to 'Start' the array with the swapped assignments. I'm getting...

    Too many wrong and/or missing disks!

     

    The 'Start' is grayed out and nothing to tick to continue.

     

    I'm presuming, it's not necessary to swap assignments, if I'm keeping track of the drives through the migration.

    WAG, but you can't swap assignments if you have both parity disks enabled and valid. Single parity - switching slots allowed, Dual parity - slots not movable without recalculating Q parity. It's not necessary to swap things around as long as you don't use disk specific locations, and even then it's fine as long as you change the assignments to track the new disk number.

     

    Thanks, but I'm only using single Parity. Also don't have User Shares.

     

    Unlike v6.1, v6.2 doesn't allow disk swapping even when using single parity, Tom already posted that this will be fixed on a future release.

    Must have missed that discussion.  :o

     

    So, for now if you want to move disk assignments, you will have to set a new config and carefully assign the drives where you want them. Just be ABSOLUTELY positive which drive is your parity drive. You can check the box to indicate parity is already valid, but I would do a parity check afterwards anyway.

     

    Unless you have a pressing need to keep each migration's disk assignments correct, I'd just wait til you are all done, then reassign all disks at once.

     

    Understood, thanks.

  2. <snip>

    10. Stop the array; we are now going to swap their assignments; when stopped, click on the dropdown for the new drive (e.g. Disk 11) and unassign it; it should notify you of 'Missing drive'

    11. Click on the dropdown for the other drive (e.g. Disk 10), the one being converted, and reassign it as the physical drive that was just added, the new drive that was empty; you will be notified of 'Wrong drive'

    12. Click on the dropdown for the slot of the new drive (e.g. Disk 11) and reassign it to the physical drive that was being converted (e.g. Disk 10); you will get more notifications of wrong or missing drives; you have just swapped the 2 drives, which is fine as they are identical (except for file system format)

    13. Important! Click on each drive name (e.g. Disk 10 and Disk 11) and change the format of the drive; if it's ReiserFS change it to XFS, if it's XFS change it to ReiserFS; it's important to swap the disk formats as well as the physical drive assignments

    14. You should see both drives listed with errors, possibly as unmountable, and a check box; click it and click the Start button to start the array; it should start up without issue and look almost identical to what it looked like before the swap, with no parity check needed; however the XFS disk is now online and its files are now being shared as they normally would; check it all if you are in doubt

     

    I'm on 6.2 and there doesn't appear to be a way to 'Start' the array with the swapped assignments. I'm getting...

    Too many wrong and/or missing disks!

     

    The 'Start' is grayed out and nothing to tick to continue.

     

    I'm presuming, it's not necessary to swap assignments, if I'm keeping track of the drives through the migration.

    WAG, but you can't swap assignments if you have both parity disks enabled and valid. Single parity - switching slots allowed, Dual parity - slots not movable without recalculating Q parity. It's not necessary to swap things around as long as you don't use disk specific locations, and even then it's fine as long as you change the assignments to track the new disk number.

     

    Thanks, but I'm only using single Parity. Also don't have User Shares.

     

    Unlike v6.1, v6.2 doesn't allow disk swapping even when using single parity, Tom already posted that this will be fixed on a future release.

     

    Thanks for the clarification. I'll just skip the assignment swapping steps and just use the previous drive as the 'new' empty.

  3. <snip>

    10. Stop the array; we are now going to swap their assignments; when stopped, click on the dropdown for the new drive (e.g. Disk 11) and unassign it; it should notify you of 'Missing drive'

    11. Click on the dropdown for the other drive (e.g. Disk 10), the one being converted, and reassign it as the physical drive that was just added, the new drive that was empty; you will be notified of 'Wrong drive'

    12. Click on the dropdown for the slot of the new drive (e.g. Disk 11) and reassign it to the physical drive that was being converted (e.g. Disk 10); you will get more notifications of wrong or missing drives; you have just swapped the 2 drives, which is fine as they are identical (except for file system format)

    13. Important! Click on each drive name (e.g. Disk 10 and Disk 11) and change the format of the drive; if it's ReiserFS change it to XFS, if it's XFS change it to ReiserFS; it's important to swap the disk formats as well as the physical drive assignments

    14. You should see both drives listed with errors, possibly as unmountable, and a check box; click it and click the Start button to start the array; it should start up without issue and look almost identical to what it looked like before the swap, with no parity check needed; however the XFS disk is now online and its files are now being shared as they normally would; check it all if you are in doubt

     

    I'm on 6.2 and there doesn't appear to be a way to 'Start' the array with the swapped assignments. I'm getting...

    Too many wrong and/or missing disks!

     

    The 'Start' is grayed out and nothing to tick to continue.

     

    I'm presuming, it's not necessary to swap assignments, if I'm keeping track of the drives through the migration.

    WAG, but you can't swap assignments if you have both parity disks enabled and valid. Single parity - switching slots allowed, Dual parity - slots not movable without recalculating Q parity. It's not necessary to swap things around as long as you don't use disk specific locations, and even then it's fine as long as you change the assignments to track the new disk number.

     

    Thanks, but I'm only using single Parity. Also don't have User Shares.

  4. <snip>

    10. Stop the array; we are now going to swap their assignments; when stopped, click on the dropdown for the new drive (e.g. Disk 11) and unassign it; it should notify you of 'Missing drive'

    11. Click on the dropdown for the other drive (e.g. Disk 10), the one being converted, and reassign it as the physical drive that was just added, the new drive that was empty; you will be notified of 'Wrong drive'

    12. Click on the dropdown for the slot of the new drive (e.g. Disk 11) and reassign it to the physical drive that was being converted (e.g. Disk 10); you will get more notifications of wrong or missing drives; you have just swapped the 2 drives, which is fine as they are identical (except for file system format)

    13. Important! Click on each drive name (e.g. Disk 10 and Disk 11) and change the format of the drive; if it's ReiserFS change it to XFS, if it's XFS change it to ReiserFS; it's important to swap the disk formats as well as the physical drive assignments

    14. You should see both drives listed with errors, possibly as unmountable, and a check box; click it and click the Start button to start the array; it should start up without issue and look almost identical to what it looked like before the swap, with no parity check needed; however the XFS disk is now online and its files are now being shared as they normally would; check it all if you are in doubt

     

    I'm on 6.2 and there doesn't appear to be a way to 'Start' the array with the swapped assignments. I'm getting...

    Too many wrong and/or missing disks!

     

    The 'Start' is grayed out and nothing to tick to continue.

     

    I'm presuming, it's not necessary to swap assignments, if I'm keeping track of the drives through the migration.

  5. koshia

     

    Do you have the 'eye' icon?

     

    2gUXe7q.png

     

     

    EDIT:

    It probably only shows after starting a preclear. I'm curious if it shows only when a preclear is started from the plugin or if it should also be there if a preclear was started manually?

  6. Updated to .26b and still had the same issue.

     

    I noticed on the flash, I had a new directory /boot/.preclear

     

    I didn't see a directory /boot/preclear_reports  -  I added the directory manually and it now shows me the unassigned drive. I presume it may be working now. Can't test, as I'd already started the preclear manually.

     

    Is this all I will see, if I currently have the preclear running manually?

     

    siECS5l.png

     

     

    EDIT:

    I also ran the tmux code and still have...

     

    no server running on /tmp/tmux-0/default

     

    if that matters?

     

    EDIT2:

    I guess something is still wrong, I don't see the 'eye' that was being discussed earlier and in gfjardim's screenshot.

     

  7. So I ran the update and had the same issue after starting the plugin.

     

    Ran what you posted previously.

    tmux ls|awk 'BEGIN { FS=":" } /^preclear_disk/ {print $1}'|while read i; do tmux capture-pane -t "$i" && tmux show-buffer | sed '/^$/{:a;N;s/\n$//;ta}'; done

    error connecting to /tmp/tmux-0/default (No such file or directory)

     

    Did what PhAzE posted...

     

    touch /tmp/tmux-0/default

     

    re-ran the tmux code

     

    no server running on /tmp/tmux-0/default

     

    Still not able to start the plugin.

     

    WJXMffI.png

  8. I have this issue with 6.2, using the latest Preclear plugin. Installed from CA. Modified the script as suggested. It never shows any drives. I'm able to run the script manually through Screen/Putty without a problem.

     

    WJXMffI.png

×
×
  • Create New...