Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Disk error one of RDP VPS
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Disk error one of RDP VPS

Hi,
I am using virtualizor and one of the windows container based RDP was hang,
i powered off and again start it.
after start it goes toward chckdisk windows.
here is the result.

After checkdisk windows went to startup recovery, which were failed, then i again restart to make it works finally i am able to login windows rdp now. I have node server and many rdps in it.

Please check would i need to change the server and deploy everything in new server if hdd start failing? what is that sign?

  • EventData

    Checking file system on C: The type of the file system is NTFS. One of your disks needs to be checked for consistency. You may cancel the disk check, but it is strongly recommended that you continue. Windows will now check the disk. Stage 1: Examining basic file system structure ... The total allocated size 0xe8bc000 of attribute of type 0x80 and instance tag 0x0 in file 0x67fb is incorrect. The expected value is 205d8000. Correcting total allocated size in attribute record (80, "") of file 20000000067fb. The allocated length 0xa4000 is not in multiple of 0x10000 for attribute of type 0x80 and instance tag 0x0. The total allocated size 0xa4000 of attribute of type 0x80 and instance tag 0x0 in file 0x19583 is incorrect. The expected value is 2510000. Correcting total allocated size in attribute record (80, $J) of file 2000000019583. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0xddf91b for possibly 0x9 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x1 in file 0x40db2 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0x40DB2. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0xddf924 for possibly 0x1 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0x40de6 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0x40DE6. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0x3be8b for possibly 0x19 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x1 in file 0x40e06 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0x40E06. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0x3bea4 for possibly 0x2 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x1 in file 0x40e0a is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0x40E0A. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0xdf64a7 for possibly 0x107 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x1 in file 0x40ecb is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0x40ECB. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0xddf340 for possibly 0x64 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x1 in file 0x40ed2 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0x40ED2. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0xddf3a4 for possibly 0x53 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x1 in file 0x40ed4 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0x40ED4. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0x303183 for possibly 0x5 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x1 in file 0x40eda is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0x40EDA. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0x2935f0 for possibly 0xe clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x1 in file 0x40fa4 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0x40FA4. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0x303193 for possibly 0x5 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x1 in file 0x40fb2 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0x40FB2. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0x3031a3 for possibly 0x5 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x1 in file 0x41051 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0x41051. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0xd8fa0d for possibly 0xcb clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x1 in file 0x41088 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0x41088. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0xd8fad8 for possibly 0x38 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x1 in file 0x41090 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0x41090. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0x641a30 for possibly 0x4 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x1 in file 0x41091 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0x41091. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0xf7093a for possibly 0x1a0 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x1 in file 0x41099 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0x41099. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0x3031b3 for possibly 0x5 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x1 in file 0x410a6 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0x410A6. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0x2943d0 for possibly 0xe clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x1 in file 0x410ad is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0x410AD. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0x6aca38 for possibly 0x7 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x1 in file 0x410d1 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0x410D1. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0xe39f8a for possibly 0x5e clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x1 in file 0x410de is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0x410DE. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0xe39fe8 for possibly 0x42 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x1 in file 0x410e4 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0x410E4. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0x77595 for possibly 0x3cd clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x1 in file 0x410e9 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0x410E9. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0xe3a02a for possibly 0x4a clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x1 in file 0x410ee is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0x410EE. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0xe3a074 for possibly 0x29 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x1 in file 0x4112f is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0x4112F. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0xe3a09d for possibly 0x17 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x1 in file 0x41131 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0x41131. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0x303853 for possibly 0x5 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x1 in file 0x411bd is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0x411BD. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0x716dcb for possibly 0xf7 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x1 in file 0x411d1 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0x411D1. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0x2ff922 for possibly 0x23 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0x71b27 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0x71B27. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0xe455a0 for possibly 0x4 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x1 in file 0x8e025 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0x8E025. Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0xdf6530 for possibly 0x211 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0x971e8 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0x971E8. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0xddf2ec for possibly 0x1 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0xa8cb6 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0xA8CB6. Attribute record of type 0xa0 and instance tag 0x4 is cross linked starting at 0xddf2ee for possibly 0x1 clusters. Some clusters occupied by attribute of type 0xa0 and instance tag 0x4 in file 0xa8cb7 is already in use. Deleting corrupt attribute record (0xA0, $I30) from file record segment 0xA8CB7. Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0xddf2ed for possibly 0x1 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0xa8cba is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0xA8CBA. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0xddf2ef for possibly 0x1 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0xa8cbb is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0xA8CBB. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0xddf300 for possibly 0x4 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0xa8cbe is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0xA8CBE. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0xddf304 for possibly 0x1 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0xa8cc0 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0xA8CC0. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0xddf305 for possibly 0x3 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0xa8cc1 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0xA8CC1. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0xddf308 for possibly 0x1 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0xa8cc2 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0xA8CC2. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0xddf309 for possibly 0x1 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0xa8cc4 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0xA8CC4. Attribute record of type 0xa0 and instance tag 0x3 is cross linked starting at 0xddf310 for possibly 0x1 clusters. Some clusters occupied by attribute of type 0xa0 and instance tag 0x3 in file 0xa8cc5 is already in use. Deleting corrupt attribute record (0xA0, $I30) from file record segment 0xA8CC5. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0xddf30a for possibly 0x2 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0xa8cc6 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0xA8CC6. Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0xddf30c for possibly 0x1 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0xa8cc7 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0xA8CC7. Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0xddf30d for possibly 0x2 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0xa8cc8 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0xA8CC8. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0xddf30f for possibly 0x1 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0xa8cc9 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0xA8CC9. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0xddf311 for possibly 0x1 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0xa8cca is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0xA8CCA. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0xddf322 for possibly 0x1 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0xa8ccb is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0xA8CCB. Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0xddf323 for possibly 0x1 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0xa8ccc is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0xA8CCC. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0xddf334 for possibly 0x3 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0xa8ccd is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0xA8CCD. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0xddf337 for possibly 0x2 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0xa8cce is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0xA8CCE. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0xddf339 for possibly 0x1 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0xa8ccf is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0xA8CCF. Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0xddf33a for possibly 0x1 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0xa8cd0 is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0xA8CD0. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0xddf33b for possibly 0x1 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0xa8cd1 is already

Comments

  • davidedavide Member
    edited December 2023

    Is this a dedicated machine? I bet it's Hetzner's junk.

    The file system is fucked, if that helps. Maybe there is some recovery ISO that you can mount and salvage some crap out of it.

  • that rdp vps is now working now, , so should i switch that server or what? or ask them to replace hdd?

  • davidedavide Member
    edited December 2023

    If that happens again and again you might want to replace the hardware. Otherwise, you might just like this Hetzner specimen of garbage the way it was meant to be.

    The problem may have been transient and resolved.

    Thanked by 1Dilstar
Sign In or Register to comment.