Project

General

Profile

Bug #29277

Wait for zfs.pool.extend to complete so we can propagate errors when adding a mirrored USB drive

Added by Jeff Mueller over 1 year ago. Updated 11 months ago.

Status:
Done
Priority:
No priority
Assignee:
Vladimir Vinogradenko
Category:
Middleware
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

I plugged in a second USB drive and followed the guide to Attach it to my existing boot device (Stripe) to make it a mirror. After a few seconds, it shows a "success" message at the top, but there is no change to my boot device.

This seems to be related to this bug, but I am following the recommendation to create a new bug with debug info attached.

https://redmine.ixsystems.com/issues/27834

attach-success.png (52.4 KB) attach-success.png Jeff Mueller, 03/23/2018 08:43 AM
alert.PNG (12.5 KB) alert.PNG Jeff Mueller, 03/27/2018 06:04 AM
online.PNG (26.2 KB) online.PNG Jeff Mueller, 03/27/2018 06:04 AM
15576
15735
15738

Related issues

Related to FreeNAS - Bug #27834: Fix the attachment of boot mirror devicesDone2018-01-162018-02-12
Has duplicate FreeNAS - Bug #32445: Boot DriveClosed2018-04-18
Has duplicate FreeNAS - Bug #40424: USB boot drive issuesClosed
Has duplicate FreeNAS - Bug #47884: replacing a failed USB device, member of freenas-boot, does not work from the GUIClosed

Associated revisions

Revision 439eb586 (diff)
Added by Vladimir Vinogradenko over 1 year ago

fix(boot): Wait for zfs.pool.extend to complete so we can propagate errors from it (if any)

Ticket: #29277

Revision 46aa959f (diff)
Added by Vladimir Vinogradenko over 1 year ago

fix(zfs): Fix error message being meaningless

Ticket: #29277

Revision 4112badf (diff)
Added by Vladimir Vinogradenko over 1 year ago

fix(boot): Wait for zfs.pool.extend to complete so we can propagate errors from it (if any)

Ticket: #29277

Revision 1ad942c5 (diff)
Added by Vladimir Vinogradenko over 1 year ago

fix(zfs): Fix error message being meaningless

Ticket: #29277

Revision 837e062c (diff)
Added by Vladimir Vinogradenko about 1 year ago

fix(middleware): Fix exception reraise in job.wrap()

Ticket: #29277

Revision c17eb7b7 (diff)
Added by Vladimir Vinogradenko about 1 year ago

fix(boot.attach): Wait for zfs.pool.extend to complete so we can propagate errors from it (if any)

Ticket: #29277

Revision 802727d0 (diff)
Added by Vladimir Vinogradenko about 1 year ago

fix(zfs): Fix error message being meaningless

Ticket: #29277

Revision 747c5249 (diff)
Added by Vladimir Vinogradenko about 1 year ago

fix(boot.attach): Use freenas-boot pool disk guid instead of trying to guess its path

Ticket: #29277

History

#1 Updated by Jeff Mueller over 1 year ago

  • File debug-sabin-20180308134011.txz added
  • Private changed from No to Yes

#2 Updated by Dru Lavigne over 1 year ago

  • Related to Bug #27834: Fix the attachment of boot mirror devices added

#3 Updated by Dru Lavigne over 1 year ago

  • Category changed from OS to Middleware
  • Assignee changed from Release Council to Vladimir Vinogradenko
  • Target version set to 11.2-RC2

#4 Updated by Vladimir Vinogradenko over 1 year ago

  • Status changed from Unscreened to Blocked
  • Reason for Blocked set to Waiting for feedback

The only boot.attach call I see in the logs happened on 2018/02/11, it was before 11.1-U2 was released. Have you tried attaching your drive since then? Can you please try it once more and upload debug logs then?

#5 Updated by Jeff Mueller over 1 year ago

  • File fndebug.zip added

Tried again, same result. Debug is attached (sudo /usr/local/bin/freenas-debug -A)

#6 Updated by Dru Lavigne over 1 year ago

  • Status changed from Blocked to Not Started
  • Reason for Blocked deleted (Waiting for feedback)

#7 Updated by Vladimir Vinogradenko over 1 year ago

  • Status changed from Not Started to Blocked
  • Reason for Blocked set to Waiting for feedback

Jeff, sorry, that's not exactly what I need. This is your system info, I need logs. You get save them using System -> Advanced -> Save Debug

#8 Updated by Jeff Mueller over 1 year ago

  • File debug-sabin-20180323110811.tgz added

Gotcha, thanks. Should be there now.

#9 Updated by Vladimir Vinogradenko over 1 year ago

Jeff, have you tried attaching your USB drive before getting this logs? Most recent boot.attach I see in the logs happened on 2018/02/11

#10 Updated by Jeff Mueller over 1 year ago

15576

Yes, maybe this is part of the problem? I just tried it again at 11:41 AM EST. I will upload the resulting screenshot and another debug for you.

#11 Updated by Dru Lavigne over 1 year ago

  • Status changed from Blocked to Not Started
  • Reason for Blocked deleted (Waiting for feedback)

#12 Updated by Vladimir Vinogradenko over 1 year ago

  • Status changed from Not Started to Blocked
  • Reason for Blocked set to Waiting for feedback

Jeff, I am out of ideas. There is an update pending on your system, can you please reboot to apply it and check if problem persists?

#13 Updated by Jeff Mueller over 1 year ago

  • File deleted (fndebug.zip)

#14 Updated by Jeff Mueller over 1 year ago

  • File debug-sabin-20180324114255.tgz added
  • Seen in changed from 11.1-U2 to 11.1-U4

Hi,
I am now on 11.1-U4 with no change to the issue. I just tried again with the same result. Is there any log I can look at? Any command-line commands I can try? Uploading another debug.

#15 Updated by Dru Lavigne over 1 year ago

  • Status changed from Blocked to Not Started
  • Reason for Blocked deleted (Waiting for feedback)

#16 Updated by Vladimir Vinogradenko about 1 year ago

  • Status changed from Not Started to Blocked
  • Reason for Blocked set to Waiting for feedback

Jeff, thank you for your help with this, this bug will be resolved in 11.2

Meanwhile you can try running zpool attach freenas-boot gptid/6bc5cedd-6627-11e5-a5a5-d050995b1314 da1p2 and your USB drive should be attached to boot pool successfully.

Please post output of this command here so we can be sure that this was the only obstacle left.

#17 Updated by Jeff Mueller about 1 year ago

15735
15738

Thanks, I think that worked, although the GUI does not show "Resilvering", it already says both disks are "ONLINE". I also got a red CRITICAL error for the resilver happening. Here is the command output, and see attached for screenshots etc. Do I need to do something with "gpart" as the command output says?

root@sabin:~ # zpool attach freenas-boot gptid/6bc5cedd-6627-11e5-a5a5-d050995b1314 da1p2
Make sure to wait until resilver is done before rebooting.

If you boot from pool 'freenas-boot', you may need to update
boot code on newly attached disk 'da1p2'.

Assuming you use GPT partitioning and 'da0' is your new boot disk
you may use the following command:

        gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da0

root@sabin:~ # zpool status freenas-boot
  pool: freenas-boot
 state: ONLINE
status: One or more devices is currently being resilvered.  The pool will
        continue to function, possibly in a degraded state.
action: Wait for the resilver to complete.
  scan: resilver in progress since Tue Mar 27 08:51:37 2018
        11.3G scanned at 263M/s, 58.2M issued at 1.32M/s, 11.3G total
        49.5M resilvered, 0.50% done, no estimated completion time
config:

        NAME                                            STATE     READ WRITE CKSUM
        freenas-boot                                    ONLINE       0     0     0
          mirror-0                                      ONLINE       0     0     0
            gptid/6bc5cedd-6627-11e5-a5a5-d050995b1314  ONLINE       0     0     0
            da1p2                                       ONLINE       0     0     0  (resilvering)

errors: No known data errors
root@sabin:~ #

#18 Updated by Vladimir Vinogradenko about 1 year ago

  • Status changed from Blocked to Done

#19 Updated by Vladimir Vinogradenko about 1 year ago

Do I need to do something with "gpart" as the command output says?

No, this was already done by FreeNAS before. zpool attach was the only thing left. Thank you again for your reports.

#20 Updated by Dru Lavigne about 1 year ago

  • File deleted (debug-sabin-20180308134011.txz)

#21 Updated by Dru Lavigne about 1 year ago

  • File deleted (debug-sabin-20180323110811.tgz)

#22 Updated by Dru Lavigne about 1 year ago

  • File deleted (debug-sabin-20180323114355.tgz)

#23 Updated by Dru Lavigne about 1 year ago

  • File deleted (debug-sabin-20180324114255.tgz)

#24 Updated by Dru Lavigne about 1 year ago

  • File deleted (debug-sabin-20180327090213.tgz)

#25 Updated by Dru Lavigne about 1 year ago

  • Status changed from Done to Closed
  • Target version changed from 11.2-RC2 to N/A
  • Private changed from Yes to No
  • Reason for Closing set to Duplicate
  • Reason for Blocked deleted (Waiting for feedback)

#26 Updated by Vladimir Vinogradenko about 1 year ago

#27 Updated by William Grzybowski 11 months ago

  • Status changed from Closed to Done
  • Severity set to New

#28 Updated by William Grzybowski 11 months ago

  • Has duplicate Bug #40424: USB boot drive issues added

#29 Updated by Dru Lavigne 11 months ago

  • Target version changed from N/A to 11.2-BETA1
  • Reason for Closing deleted (Duplicate)

#30 Updated by Dru Lavigne 11 months ago

  • Subject changed from Boot device - adding mirrored USB drive shows success message in web UI, but does nothing to Wait for zfs.pool.extend to complete so we can propagate errors when adding a mirrored USB drive

#31 Updated by Dru Lavigne 11 months ago

  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

#33 Updated by William Grzybowski 9 months ago

  • Has duplicate Bug #47884: replacing a failed USB device, member of freenas-boot, does not work from the GUI added

Also available in: Atom PDF