• 6.8.1 upgrade failed in the middle of the process

    RokleM

    By RokleM

      • Closed

    Upgrade failed and second attempts will not go through.  My other server worked.

     

     

     

    plugin: updating: unRAIDServer.plg
    plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.8.1-x86_64.zip ... done
    plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.8.1-x86_64.md5 ... done

    writing flash device - please wait...
    Archive: /tmp/unRAIDServer.zip
    plugin: run failed: /bin/bash retval: 1

     

     

    My Dockers are also now down after the failed upgrade:

     

    Warning: parse_ini_file(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 43

    Warning: array_replace_recursive(): Expected parameter 2 to be an array, bool given in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 43

     

     

     

    And my VM's:
     

    Warning: parse_ini_file(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/include/libvirt_helpers.php on line 460

     

     

     

    root@nas:/boot# ls -alh
    total 8.0K
    drwx------ 10 root root 8.0K Jan 12 11:10 ./
    drwxr-xr-x 20 root root  440 Jan 11 19:47 ../

    Go to reports Stable Releases

    User Feedback

    Recommended Comments

    RokleM

    Looks like the USB "disconnected" right at upgrade time, which makes no sense as it was working perfect for probably 5 years.  I remove / re-insert and nothing shows up in /boot.  It works in my windows machine.

     

    Jan 12 11:10:40 nas emhttpd: req (8): cmd=/plugins/dynamix.plugin.manager/scripts/plugin&arg1=update&arg2=unRAIDServer.plg&csrf_token=****************
    Jan 12 11:10:40 nas emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin update unRAIDServer.plg
    Jan 12 11:10:40 nas root: plugin: creating: /tmp/unRAIDServer.sh - from INLINE content
    Jan 12 11:10:40 nas root: plugin: running: /tmp/unRAIDServer.sh
    Jan 12 11:10:40 nas root: plugin: creating: /tmp/unRAIDServer.zip - downloading from URL https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.8.1-x86_64.zip
    Jan 12 11:10:49 nas root: plugin: creating: /tmp/unRAIDServer.md5 - downloading from URL https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.8.1-x86_64.md5
    Jan 12 11:10:49 nas root: plugin: creating: /tmp/unRAIDServer.sh - from INLINE content
    Jan 12 11:10:49 nas root: plugin: running: /tmp/unRAIDServer.sh
    Jan 12 11:11:00 nas kernel: usb 5-1: USB disconnect, device number 2
    Jan 12 11:11:00 nas kernel: print_req_error: I/O error, dev sda, sector 9830280
    Jan 12 11:11:00 nas kernel: print_req_error: I/O error, dev sda, sector 9830520
    Jan 12 11:11:00 nas kernel: print_req_error: I/O error, dev sda, sector 9830760
    Jan 12 11:11:00 nas kernel: print_req_error: I/O error, dev sda, sector 9831000
    Jan 12 11:11:00 nas kernel: print_req_error: I/O error, dev sda, sector 9831240
    Jan 12 11:11:00 nas kernel: print_req_error: I/O error, dev sda, sector 9831480
    Jan 12 11:11:00 nas kernel: print_req_error: I/O error, dev sda, sector 9831720
    Jan 12 11:11:00 nas kernel: print_req_error: I/O error, dev sda, sector 9831960
    Jan 12 11:11:00 nas kernel: print_req_error: I/O error, dev sda, sector 9832200
    Jan 12 11:11:00 nas kernel: print_req_error: I/O error, dev sda, sector 9832440
    Jan 12 11:11:00 nas kernel: Buffer I/O error on dev sda1, logical block 1, lost async page write
    Jan 12 11:11:00 nas kernel: Buffer I/O error on dev sda1, logical block 4789, lost async page write
    Jan 12 11:11:00 nas kernel: Buffer I/O error on dev sda1, logical block 4790, lost async page write
    Jan 12 11:11:00 nas kernel: Buffer I/O error on dev sda1, logical block 4791, lost async page write
    Jan 12 11:11:00 nas kernel: Buffer I/O error on dev sda1, logical block 4792, lost async page write
    Jan 12 11:11:00 nas kernel: Buffer I/O error on dev sda1, logical block 4793, lost async page write
    Jan 12 11:11:00 nas kernel: Buffer I/O error on dev sda1, logical block 4794, lost async page write
    Jan 12 11:11:00 nas kernel: Buffer I/O error on dev sda1, logical block 4795, lost async page write
    Jan 12 11:11:00 nas kernel: Buffer I/O error on dev sda1, logical block 4796, lost async page write
    Jan 12 11:11:00 nas kernel: Buffer I/O error on dev sda1, logical block 4797, lost async page write
    Jan 12 11:11:00 nas rc.diskinfo[23443]: SIGHUP received, forcing refresh of disks info.
    Jan 12 11:11:00 nas kernel: ------------[ cut here ]------------
    Jan 12 11:11:00 nas kernel: bdi-block not registered
    Jan 12 11:11:00 nas kernel: WARNING: CPU: 8 PID: 24973 at fs/fs-writeback.c:2239 __mark_inode_dirty+0x151/0x1d5
    Jan 12 11:11:00 nas kernel: Modules linked in: macvlan xt_nat xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat nf_nat_ipv6 iptable_mangle ip6table_filter ip6_tables vhost_net tun vhost tap veth ipt_MASQUERADE iptable_filter iptable_nat nf
    _nat_ipv4 nf_nat ip_tables xfs md_mod nct6775 hwmon_vid k10temp bonding r8169 realtek edac_mce_amd kvm_amd kvm mpt3sas crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel ahci aes_x86_64 i2c_piix4 crypto_simd i2c_
    core cryptd ccp libahci raid_class wmi_bmof glue_helper scsi_transport_sas nvme button pcc_cpufreq acpi_cpufreq nvme_core wmi [last unloaded: realtek]
    Jan 12 11:11:00 nas kernel: CPU: 8 PID: 24973 Comm: unzip Not tainted 4.19.88-Unraid #1
    Jan 12 11:11:00 nas kernel: Hardware name: System manufacturer System Product Name/TUF GAMING X570-PLUS (WI-FI), BIOS 1405 11/19/2019
    Jan 12 11:11:00 nas kernel: RIP: 0010:__mark_inode_dirty+0x151/0x1d5
    Jan 12 11:11:00 nas kernel: Code: ef e7 ff ff 49 89 c4 48 8b 00 f6 40 3c 02 75 1c 49 8b 54 24 08 80 e2 01 75 12 48 8b 70 30 48 c7 c7 b5 da d4 81 e8 fd db ed ff <0f> 0b 48 8b 05 94 2c c9 00 45 85 ed 48 89 85 c0 00 00 00 74 0e 48
    Jan 12 11:11:00 nas kernel: RSP: 0018:ffffc9000f043d78 EFLAGS: 00010286
    Jan 12 11:11:00 nas kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000007
    Jan 12 11:11:00 nas kernel: RDX: 0000000000000519 RSI: 0000000000000002 RDI: ffff889f9e8164f0
    Jan 12 11:11:00 nas kernel: RBP: ffff889f5b34f6a8 R08: 0000000000000003 R09: 0000000000019a00
    Jan 12 11:11:00 nas kernel: R10: 0000000000000000 R11: 0000000000000038 R12: ffff889f9468b858
    Jan 12 11:11:00 nas kernel: R13: 0000000000000000 R14: ffff889f5b34f728 R15: 0000000000000000
    Jan 12 11:11:00 nas kernel: FS:  000014ab42f2c740(0000) GS:ffff889f9e800000(0000) knlGS:0000000000000000
    Jan 12 11:11:00 nas kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Jan 12 11:11:00 nas kernel: CR2: 0000150a58b20899 CR3: 0000001eebd56000 CR4: 0000000000340ee0
    Jan 12 11:11:00 nas kernel: Call Trace:
    Jan 12 11:11:00 nas kernel: fat_setattr+0x1fc/0x20f
    Jan 12 11:11:00 nas kernel: notify_change+0x269/0x352
    Jan 12 11:11:00 nas kernel: utimes_common+0x12c/0x190
    Jan 12 11:11:00 nas kernel: do_utimes+0xf6/0x136
    Jan 12 11:11:00 nas kernel: __se_sys_utime+0x77/0x8e
    Jan 12 11:11:00 nas kernel: do_syscall_64+0x57/0xf2
    Jan 12 11:11:00 nas kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
    Jan 12 11:11:00 nas kernel: RIP: 0033:0x14ab43034d77
    Jan 12 11:11:00 nas kernel: Code: 48 89 ef b8 35 01 00 00 0f 05 48 89 c2 48 3d 00 f0 ff ff 77 c9 48 83 c4 08 5d 41 5c c3 66 0f 1f 44 00 00 b8 84 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e9 90 0d 00 f7 d8 64 89 01 48
    Jan 12 11:11:00 nas kernel: RSP: 002b:00007ffe88ee3f78 EFLAGS: 00000297 ORIG_RAX: 0000000000000084
    Jan 12 11:11:00 nas kernel: RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 000014ab43034d77
    Jan 12 11:11:00 nas kernel: RDX: 0000000000000000 RSI: 00007ffe88ee3fa0 RDI: 000000000051d6b8
    Jan 12 11:11:00 nas kernel: RBP: 0000000000000002 R08: 000000000052004a R09: 0000000000000000
    Jan 12 11:11:00 nas kernel: R10: 00007ffe88ee35e0 R11: 0000000000000297 R12: 0000000000000000
    Jan 12 11:11:00 nas kernel: R13: 000000000042674b R14: 0000000000000000 R15: 00007ffe88ee40d0
    Jan 12 11:11:00 nas kernel: ---[ end trace 330187821b978133 ]---
    Jan 12 11:11:00 nas kernel: FAT-fs (sda1): Directory bread(block 9732312) failed
    Jan 12 11:11:00 nas kernel: FAT-fs (sda1): Directory bread(block 9732313) failed
    Jan 12 11:11:00 nas kernel: FAT-fs (sda1): Directory bread(block 9732314) failed
    Jan 12 11:11:00 nas kernel: FAT-fs (sda1): Directory bread(block 9732315) failed
    Jan 12 11:11:00 nas kernel: FAT-fs (sda1): Directory bread(block 9732316) failed
    Jan 12 11:11:00 nas kernel: FAT-fs (sda1): Directory bread(block 9732317) failed
    Jan 12 11:11:00 nas kernel: FAT-fs (sda1): Directory bread(block 9732318) failed
    Jan 12 11:11:00 nas kernel: FAT-fs (sda1): Directory bread(block 9732319) failed
    Jan 12 11:11:00 nas kernel: FAT-fs (sda1): Directory bread(block 9732320) failed
    Jan 12 11:11:00 nas kernel: FAT-fs (sda1): Directory bread(block 9732321) failed
    Jan 12 11:11:00 nas kernel: FAT-fs (sda1): FAT read failed (blocknr 4913)
     

    Link to comment
    itimpi

    I suspect you are going to need to reformat and rewrite the flash device as it is definitely getting read errors on the Unraid server at the moment.   Doing an upgrade is the one time you do a significant amount of writing to the flash drive in normal running of Unraid.

     

    Before doing to make sure you have a backup of the 'config' folder from either the current flash drive or a recent backup.   Putting that back after recreating the USB drive will put back your configuration.

     

     

    Link to comment
    RokleM

    can read in windows...  Logs when I try to plug the disk in
     

     

    Jan 12 11:46:12 nas emhttpd: Starting services...
    Jan 12 11:46:12 nas emhttpd: shcmd (6546): /etc/rc.d/rc.samba restart
    Jan 12 11:46:12 nas root: cp: cannot create regular file '/boot/config': Input/output error
    Jan 12 11:46:12 nas kernel: FAT-fs (sda1): FAT read failed (blocknr 4913)
    Jan 12 11:46:12 nas kernel: usb 3-2: new high-speed USB device number 6 using xhci_hcd
    Jan 12 11:46:12 nas kernel: usb-storage 3-2:1.0: USB Mass Storage device detected
    Jan 12 11:46:12 nas kernel: scsi host11: usb-storage 3-2:1.0
    Jan 12 11:46:12 nas kernel: SQUASHFS error: Unable to read data cache entry [89a6c4]
    Jan 12 11:46:12 nas kernel: SQUASHFS error: Unable to read page, block 89a6c4, size 3840
    Jan 12 11:46:13 nas kernel: scsi 11:0:0:0: Direct-Access     SanDisk  Cruzer Fit       1.27 PQ: 0 ANSI: 6
    Jan 12 11:46:13 nas kernel: sd 11:0:0:0: Attached scsi generic sg0 type 0
    Jan 12 11:46:13 nas kernel: SQUASHFS error: Unable to read data cache entry [89a6c4]
    Jan 12 11:46:13 nas kernel: SQUASHFS error: Unable to read page, block 89a6c4, size 3840
    Jan 12 11:46:13 nas kernel: sd 11:0:0:0: [sdi] 31266816 512-byte logical blocks: (16.0 GB/14.9 GiB)
    Jan 12 11:46:13 nas kernel: sd 11:0:0:0: [sdi] Write Protect is off
    Jan 12 11:46:13 nas kernel: sd 11:0:0:0: [sdi] Mode Sense: 43 00 00 00
    Jan 12 11:46:13 nas kernel: sd 11:0:0:0: [sdi] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
    Jan 12 11:46:13 nas kernel: SQUASHFS error: Unable to read data cache entry [89a6c4]
    Jan 12 11:46:13 nas kernel: SQUASHFS error: Unable to read page, block 89a6c4, size 3840
    Jan 12 11:46:13 nas kernel: sdi: sdi1
    Jan 12 11:46:13 nas kernel: SQUASHFS error: Unable to read data cache entry [89a6c4]
    Jan 12 11:46:13 nas kernel: SQUASHFS error: Unable to read page, block 89a6c4, size 3840
    Jan 12 11:46:13 nas kernel: sd 11:0:0:0: [sdi] Attached SCSI removable disk
    Jan 12 11:46:14 nas root: /etc/rc.d/rc.samba: line 25: /boot/config/machine-id: No such file or directory
    Jan 12 11:46:14 nas root: cp: cannot stat '/boot/config/machine-id': No such file or directory
    Jan 12 11:46:14 nas root: Starting Samba:  /usr/sbin/smbd -D
    Jan 12 11:46:14 nas root:                  /usr/sbin/nmbd -D
     

     

    Link to comment
    RokleM

    Re-created the flash disk in windows using the utility, copied the config directory over, same error....

     

     

    Jan 12 11:54:37 nas root: cp: cannot create regular file '/boot/config': Input/output error
    Jan 12 11:54:37 nas kernel: FAT-fs (sda1): FAT read failed (blocknr 4913)
    Jan 12 11:54:38 nas kernel: usb 3-2: new high-speed USB device number 8 using xhci_hcd
    Jan 12 11:54:38 nas kernel: usb-storage 3-2:1.0: USB Mass Storage device detected
    Jan 12 11:54:38 nas kernel: scsi host11: usb-storage 3-2:1.0
    Jan 12 11:54:38 nas kernel: SQUASHFS error: Unable to read data cache entry [89a6c4]
    Jan 12 11:54:38 nas kernel: SQUASHFS error: Unable to read page, block 89a6c4, size 3840
    Jan 12 11:54:39 nas kernel: scsi 11:0:0:0: Direct-Access     SanDisk  Cruzer Fit       1.27 PQ: 0 ANSI: 6
    Jan 12 11:54:39 nas kernel: sd 11:0:0:0: Attached scsi generic sg0 type 0
    Jan 12 11:54:39 nas kernel: SQUASHFS error: Unable to read data cache entry [89a6c4]
    Jan 12 11:54:39 nas kernel: SQUASHFS error: Unable to read page, block 89a6c4, size 3840
    Jan 12 11:54:39 nas kernel: sd 11:0:0:0: [sdi] 31266816 512-byte logical blocks: (16.0 GB/14.9 GiB)
    Jan 12 11:54:39 nas kernel: sd 11:0:0:0: [sdi] Write Protect is off
    Jan 12 11:54:39 nas kernel: sd 11:0:0:0: [sdi] Mode Sense: 43 00 00 00
    Jan 12 11:54:39 nas kernel: sd 11:0:0:0: [sdi] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
    Jan 12 11:54:39 nas kernel: SQUASHFS error: Unable to read data cache entry [89a6c4]
    Jan 12 11:54:39 nas kernel: SQUASHFS error: Unable to read page, block 89a6c4, size 3840
    Jan 12 11:54:39 nas kernel: sdi: sdi1
    Jan 12 11:54:39 nas kernel: SQUASHFS error: Unable to read data cache entry [89a6c4]
    Jan 12 11:54:39 nas kernel: SQUASHFS error: Unable to read page, block 89a6c4, size 3840
    Jan 12 11:54:39 nas kernel: sd 11:0:0:0: [sdi] Attached SCSI removable disk
    Jan 12 11:54:39 nas root: /etc/rc.d/rc.samba: line 25: /boot/config/machine-id: No such file or directory
     

    Link to comment
    RokleM

    Took a risk and rebooted and it's working... something in the upgrade process made the disk not accessible but somehow is restored during reboot.  Very odd.Took a risk and rebooted and it's working... something in the upgrade process made the disk not accessible but somehow is restored during reboot.  Very odd.

    Link to comment
    RokleM

    I will however it is nearly 100% unlikely that a USB stick that has been 100% reliable for over 5 years somehow had an issue within seconds of clicking the upgrade button...The statistical improbability... 

     

    There is something wrong with the update process, but hopefully other don't run into it.   

    Edited by RokleM
    Link to comment
    itimpi
    23 minutes ago, RokleM said:

    I will however it is nearly 100% unlikely that a USB stick that has been 100% reliable for over 5 years somehow had an issue within seconds of clicking the upgrade button...The statistical improbability... 

     

    There is something wrong with the update process, but hopefully other don't run into it.   

    The upgrade process is one time that a lot of writes occur to the USB drive so maybe not that unlikely.

     

    Link to comment


    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.