ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Ubuntu Systemd Bad Entry

    Scheduled Pinned Locked Moved IT Discussion
    systemdubuntuvmext4smartctlerrorerrorssmartcorruptedbuffer io error on devicebuffer iodm-0
    53 Posts 5 Posters 9.8k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • thwrT
      thwr @scottalanmiller
      last edited by

      @scottalanmiller

      @DustinB3403 said in Ubuntu Systemd Bad Entry:

      MD RAID 10 is configured on this box for the storage space. So I can check that as well.

      Should be the very first thing to check.

      thwrT 1 Reply Last reply Reply Quote 2
      • DustinB3403D
        DustinB3403
        last edited by

        lots of deleted/unused inodes, clearing them all.

        StrongBadS 1 Reply Last reply Reply Quote 0
        • StrongBadS
          StrongBad @DustinB3403
          last edited by

          @DustinB3403 said in Ubuntu Systemd Bad Entry:

          lots of deleted/unused inodes, clearing them all.

          That is common in scenarios where you have filesystem corruption.

          1 Reply Last reply Reply Quote 0
          • DustinB3403D
            DustinB3403
            last edited by

             Inode ____ ref count is _, should be . Fix<u>? 
            

            Correcting these issues.

            1 Reply Last reply Reply Quote 0
            • thwrT
              thwr @thwr
              last edited by

              @thwr said in Ubuntu Systemd Bad Entry:

              @scottalanmiller

              @DustinB3403 said in Ubuntu Systemd Bad Entry:

              MD RAID 10 is configured on this box for the storage space. So I can check that as well.

              Should be the very first thing to check.

              Array status:

              mdadm --detail /dev/mdx
              

              https://raid.wiki.kernel.org/index.php/Detecting,_querying_and_testing#Querying_the_array_status

              1 Reply Last reply Reply Quote 2
              • DustinB3403D
                DustinB3403
                last edited by

                it looks like xvda is having issues according the current screen.

                0_1463745181513_XenCenterMain_2016-05-20_07-52-53.png

                Might have to replace that drive...

                1 Reply Last reply Reply Quote 0
                • DustinB3403D
                  DustinB3403
                  last edited by

                  At the moment the system appears to just be progressing through the blk_update_request with I/O errors for individual sectors on XVDA.

                  Should I abort this operation and find a replacement drive? Is it worth it to let this continue?

                  thwrT 1 Reply Last reply Reply Quote 0
                  • thwrT
                    thwr @DustinB3403
                    last edited by

                    @DustinB3403 said in Ubuntu Systemd Bad Entry:

                    At the moment the system appears to just be progressing through the blk_update_request with I/O errors for individual sectors on XVDA.

                    Should I abort this operation and find a replacement drive? Is it worth it to let this continue?

                    Hard to say. Real data on it? Would try to get a last backup first before doing filesystem operations.

                    1 Reply Last reply Reply Quote 1
                    • scottalanmillerS
                      scottalanmiller
                      last edited by

                      Yeah, all comes down to the value of recovery, really.

                      1 Reply Last reply Reply Quote 0
                      • DustinB3403D
                        DustinB3403
                        last edited by

                        I don't mind tearing down the system, it's only running 1 VM that I'm backing up my VM's too. Which those delta's get pushed off nightly to another disk.

                        1 Reply Last reply Reply Quote 0
                        • DustinB3403D
                          DustinB3403
                          last edited by

                          Time to reboot

                          0_1463746181028_XenCenterMain_2016-05-20_08-09-31.png

                          1 Reply Last reply Reply Quote 0
                          • DustinB3403D
                            DustinB3403
                            last edited by DustinB3403

                            And the system is in recovery mode. ..

                            0_1463746323966_XenCenterMain_2016-05-20_08-11-55.png

                            1 Reply Last reply Reply Quote 0
                            • scottalanmillerS
                              scottalanmiller
                              last edited by

                              Manual fsck is no fun.

                              1 Reply Last reply Reply Quote 0
                              • DustinB3403D
                                DustinB3403
                                last edited by

                                At least all of the instructions are there, and this is a learning experience.

                                1 Reply Last reply Reply Quote 1
                                • A
                                  Alex Sage @scottalanmiller
                                  last edited by

                                  This post is deleted!
                                  1 Reply Last reply Reply Quote 0
                                  • DustinB3403D
                                    DustinB3403
                                    last edited by DustinB3403

                                    All disks in the array appear to be fine according to MD.... So this is clearly this is something with the VM.

                                    0_1463748932727_XenCenterMain_2016-05-20_08-55-18.png

                                    1 Reply Last reply Reply Quote 0
                                    • DustinB3403D
                                      DustinB3403
                                      last edited by

                                      So I was able to just restore this VM to a snapshot from the other day.

                                      Should I perform another fsck on this virtual system?

                                      1 Reply Last reply Reply Quote 0
                                      • scottalanmillerS
                                        scottalanmiller
                                        last edited by

                                        Not if it does not prompt you to.

                                        1 Reply Last reply Reply Quote 0
                                        • DustinB3403D
                                          DustinB3403
                                          last edited by

                                          So how can I check to see if whatever caused this issue is still present? I mean if it just happens from time to time, fine.

                                          But wouldn't it be good to know what caused it?

                                          scottalanmillerS 1 Reply Last reply Reply Quote 0
                                          • scottalanmillerS
                                            scottalanmiller @DustinB3403
                                            last edited by

                                            @DustinB3403 said in Ubuntu Systemd Bad Entry:

                                            But wouldn't it be good to know what caused it?

                                            That's a common thought and it makes sense, kind of. But computers are ridiculously complex beasts and not all issues are replicable. Gamma radiation, insanely uncommon bugs, memory errors, CPU errors, disk errors and such can all lead to corruption. These things happen. If you want to investigate every possible error ever you can easily spend more than the system is worth and only "guess" at the problem in the end - all for something that is unlikely to ever happen again.

                                            Think of a windshield and you get a crack in it. You don't remember something hitting your windshield. Do you stop driving and spend months doing forensics trying to determine if it was a rock, bird, bug, bridge debris, glass fragility, bizarre temperature change, etc. that caused it to crack? Would knowing be useful? Not if it doesn't happen again.

                                            So yes, KNOWING would be great. But FINDING OUT is not. Make sense? The cost required to know isn't worth it unless it becomes a repeating problem.

                                            1 Reply Last reply Reply Quote 1
                                            • 1
                                            • 2
                                            • 3
                                            • 1 / 3
                                            • First post
                                              Last post