Jump to content
  • Stuck in Boot Menu in RC4 and RC5 after upgrade from RC3


    KingB
    • Solved

    Hello,

     

    i just tried to update from RC3 to RC4 and then RC5 got released.

     

    When the the update applied and the GUI tells me to reboot, it switches back to default white skin and the docker tab for example is gone.

     

    When I reboot i get stuck in the boot menu where I can  choose between gui mode, safe mode etc.

     

    None of them work. When i choose the regular one, the 5 second automatic boot timer loops.

     

    Strange behavior.

     

    I restored the the files from the previous folder from the flash drive and now back on RC3. No logs in the log folder. Any logs I can grab?

     

    Not many Informations i can provide, I know.

     

    Specs:

     

    Custom
    M/B: ASRock - H87M Pro4
    CPU: Intel® Core™ i3-4130 CPU @ 3.40GHz
    HVM: Enabled
    IOMMU: Disabled
    Cache: 128 kB, 512 kB, 3072 kB
    Memory: 16 GB (max. installable capacity 32 GB)

     

     

    EDIT: I did the update again, same behaviour. But this time I downloaded the syslog and Diagnostics before the reboot.

     

    The error in syslog?

    Apr  8 21:34:30 Tower root: plugin: creating: /tmp/unRAIDServer.sh - from INLINE content
    Apr  8 21:34:30 Tower root: plugin: running: /tmp/unRAIDServer.sh
    Apr  8 21:34:31 Tower kernel: usb 4-1: Disable of device-initiated U1 failed.
    Apr  8 21:34:31 Tower kernel: usb 4-1: Disable of device-initiated U2 failed.
    Apr  8 21:34:32 Tower kernel: xhci_hcd 0000:00:14.0: Cannot set link state.
    Apr  8 21:34:32 Tower kernel: usb usb4-port1: cannot disable (err = -32)
    Apr  8 21:34:32 Tower kernel: xhci_hcd 0000:00:14.0: Cannot set link state.
    Apr  8 21:34:32 Tower kernel: usb usb4-port1: cannot disable (err = -32)
    Apr  8 21:34:32 Tower kernel: usb 4-1: USB disconnect, device number 2
    Apr  8 21:34:32 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
    Apr  8 21:34:32 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 00 07 22 c0 00 08 00 00
    Apr  8 21:34:32 Tower kernel: print_req_error: I/O error, dev sda, sector 467648
    Apr  8 21:34:32 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
    Apr  8 21:34:32 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 01 05 2b 40 00 00 02 00
    Apr  8 21:34:32 Tower kernel: print_req_error: I/O error, dev sda, sector 17115968
    Apr  8 21:34:32 Tower kernel: Buffer I/O error on dev sda1, logical block 17107776, lost async page write
    Apr  8 21:34:32 Tower kernel: Buffer I/O error on dev sda1, logical block 17107777, lost async page write
    Apr  8 21:34:32 Tower kernel: FAT-fs (sda1): Directory bread(block 16384) failed
    Apr  8 21:34:32 Tower kernel: FAT-fs (sda1): Directory bread(block 16385) failed
    Apr  8 21:34:32 Tower kernel: FAT-fs (sda1): Directory bread(block 16386) failed
    Apr  8 21:34:32 Tower kernel: FAT-fs (sda1): Directory bread(block 16384) failed
    Apr  8 21:34:32 Tower kernel: FAT-fs (sda1): Directory bread(block 16385) failed
    Apr  8 21:34:32 Tower kernel: FAT-fs (sda1): Directory bread(block 16386) failed
    Apr  8 21:34:32 Tower kernel: FAT-fs (sda1): Directory bread(block 16384) failed
    Apr  8 21:34:32 Tower kernel: FAT-fs (sda1): Directory bread(block 16385) failed
    Apr  8 21:34:32 Tower kernel: FAT-fs (sda1): Directory bread(block 16386) failed
    Apr  8 21:34:32 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/Backup.cfg
    Apr  8 21:34:32 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/CommunityApplicationsAppdataBackup.cfg
    Apr  8 21:34:32 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/Downloads.cfg
    Apr  8 21:34:32 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/Medien.cfg
    Apr  8 21:34:32 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/Nextcloud.cfg
    Apr  8 21:34:32 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/appdata.cfg
    Apr  8 21:34:32 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/domains.cfg
    Apr  8 21:34:32 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/isos.cfg
    Apr  8 21:34:32 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/system.cfg
    Apr  8 21:34:32 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/vdisks.cfg
    Apr  8 21:34:32 Tower emhttpd: Starting services...
    Apr  8 21:34:32 Tower kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
    Apr  8 21:34:32 Tower kernel: sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
    Apr  8 21:34:32 Tower kernel: blk_partition_remap: fail for partition 1

     

     

    tower-diagnostics-20180408-2137.zip




    User Feedback

    Recommended Comments

    Looks like you have corruption on your flash device.

     

    Shutdown your system and put the flash device in a Windows machine for repair.

     

    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.

×
×
  • Create New...