Jump to content

  • [6.12.13] Zeroing disk for removal, unmounted disk, ran dd, now Stop Array endlessly attempts to umount: /mnt/disk1: not mounted

    iarp

    By iarp

      • Minor

    I followed the instructions to zero out a data drive for removal while keeping parity ( https://docs.unraid.net/unraid-os/manual/storage-management/#notes-1 ). It just finished the zeroing process and the next instruction is to stop the array and all I got was: 

    Nov 11 21:32:07 storage emhttpd: Unmounting disks...
Nov 11 21:32:07 storage emhttpd: shcmd (602): umount /mnt/disk1
Nov 11 21:32:07 storage root: umount: /mnt/disk1: not mounted.
Nov 11 21:32:07 storage emhttpd: shcmd (602): exit status: 32
Nov 11 21:32:07 storage emhttpd: Retry unmounting disk share(s)...
Nov 11 21:32:12 storage emhttpd: Unmounting disks...
Nov 11 21:32:12 storage emhttpd: shcmd (603): umount /mnt/disk1
Nov 11 21:32:12 storage root: umount: /mnt/disk1: not mounted.
Nov 11 21:32:12 storage emhttpd: shcmd (603): exit status: 32
Nov 11 21:32:12 storage emhttpd: Retry unmounting disk share(s)...
Nov 11 21:32:17 storage emhttpd: Unmounting disks...
Nov 11 21:32:17 storage emhttpd: shcmd (604): umount /mnt/disk1
Nov 11 21:32:17 storage root: umount: /mnt/disk1: not mounted.

     

    Thankfully my array is not set to auto start so i issued the reboot command which after a couple minutes forced it to stop its endless looping and restarted the server. I completed the following instructions and removed the drive without issue.

     

    ** I attempted to umount it myself and it did confirm it wasn't mounted. I had thought about mounting something fake in its place just to get the script to move along but i worried that might do something unintended.

     

    Also I'll add that the command given in the manual and the user script had dd targeting /dev/md1 but i had to target /dev/md1p1 in order to get it to actually run. I have it running a correcting parity check right now, 200GB into 4TB and 0 errors thus far, I'll report in the morning if it finds anything wrong.

    Go to reports Stable Releases

    User Feedback

    Recommended Comments



    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
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×

  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.

    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.

×
×
  • Create New...