• "There are differences between boot sector and its backup"


    Arbadacarba
    • Annoyance

    During boot I see the following:

     

    There are differences between boot sector and its backup. 

    This is mostly harmless. Differences: (offset:original/backup)

    65:01/00, 282:e0/b2, 283:43/42, 284:00/05, 303:1a/6e, 304:81/45, 305:37/2a, 306:6d/6c <--Not my numbers... There are a LOT of them

    Not automatically fixing this

     

    image.thumb.png.0d984f2562f3ba0d5f072a0567385cb7.png

    (Graphical glitch is caused by the video scrolling faster than my capture)

    image.thumb.png.0dfec7a83f6d0e6afc525c0189449090.png

     

     

    I first noticed this AFTER upgrading my system (Mainboard, CPU, USB key

     

    I have:

    Pulled the thumb drive out and scanned it with Windows (no errors found)

    Formatted and Restored the Backup Zip File Using the Unraid USB Creator

    Formatted with a fresh install of RC2 Using the Unraid USB Creator

     

    I recorded the boot, but none of this stuff shows up in the log.

     

    I was worried that something was wrong with my USB disk, or my install, but now that I'm seeing it on a fresh install... I'm curious if there is something wrong with the Unraid USB Creator? And if there is a way to fix the problem?

     

     

     

    jupiter-syslog-20220218-2039.zip




    User Feedback

    Recommended Comments

    dosfsck -v /dev/sda1

     

    It looks like this will give me the option of:

     

    1) Copy original to backup
    2) Copy backup to original
    3) No action
    [123?q]? 

     

    But is it safe? I have a backup of the Flash disk... and it is booting fine... I guess I'll try 1

     

    Boot sector contents:
    System ID "SYSLINUX"
    Media byte 0xf8 (hard disk)
           512 bytes per logical sector
         16384 bytes per cluster
            32 reserved sectors
    First FAT starts at byte 16384 (sector 32)
             2 FATs, 32 bit entries
       7830016 bytes per FAT (= 15293 sectors)
    Root directory start at cluster 2 (arbitrary size)
    Data area starts at byte 15676416 (sector 30618)
       1956999 data clusters (32063471616 bytes)
    63 sectors/track, 255 heads
             0 hidden sectors
      62654593 sectors total
    /CONFIG/DOMAIN.CFG
      Contains a free cluster (61354). Assuming EOF.
    /CONFIG/DOMAIN.CFG
      File size is 305 bytes, cluster chain length is 0 bytes.
      Truncating file to 0 bytes.
    Checking for unused clusters.
    Reclaimed 1 unused cluster (16384 bytes).
    Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
    1) Remove dirty bit
    2) No action
    [12?q]? 1
    Checking free cluster summary.
    Free cluster summary wrong (1899085 vs. really 1899086)
    1) Correct
    2) Don't correct
    [12?q]? 

     

    OK, 1 again

     

    Then it wants to confirm write... Going for it, and rebooting

     

    image.png.edfc0d7064850435eef7e454f5d285d2.png

     

    Well, it's better I guess... Still Confused though

     

    Arbadacarba

    Link to comment

    I had the same troubleshoot. Whatever, I procedeed as you did and got this "false positive" solved.

     

    I don't like having some errors unsolved


    Thanks

    Link to comment

    Hi!

    I had the same problem.

    I'll try you solution.

     

    I did.

     

    The amount of differences reduced, but one still appeared:

     

    Quote

    dosfsck -v /dev/sda1
    fsck.fat 4.2 (2021-01-31)
    Checking we can access the last sector of the filesystem
    Boot sector contents:
    System ID "SYSLINUX"
    Media byte 0xf8 (hard disk)
           512 bytes per logical sector
         16384 bytes per cluster
            32 reserved sectors
    First FAT starts at byte 16384 (sector 32)
             2 FATs, 32 bit entries
       7830016 bytes per FAT (= 15293 sectors)
    Root directory start at cluster 2 (arbitrary size)
    Data area starts at byte 15676416 (sector 30618)
       1956999 data clusters (32063471616 bytes)
    63 sectors/track, 255 heads
             0 hidden sectors
      62654593 sectors total
    Checking for unused clusters.
    Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
    1) Remove dirty bit
    2) No action
    [12?q]?

     

    Unraid ver 6.11.3

     

    I'll post in another thread that has not got to do with pre-releases.

    Edited by acastellab
    Link to comment

    I'll add my +1, I'm having the same issue. I did the same fix with "dosfsck -v /dev/sda" but still have that one "65:00/01" difference. that popped up at the next boot.

    Link to comment
    On 11/11/2022 at 9:15 AM, acastellab said:

    I'll post in another thread that has not got to do with pre-releases.

     

    Where did you post too?

    Link to comment

    Doing the process again should get rid of the remaining error, which is caused by the order the checks are done - offset 65 is the dirty bit.

    When the dirty bit is set and it is removed in the second fix listed in the log above the original will be again different from the backup (because the bit was set when the backup was created).

    If the command is run again it shouldn't find any other difference expect the first - if the original is then copied to the backup again the last remaining difference at offset 65 should disappear too.

    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.