hello, i use solusvm and xen and i have this vps, uses 110~. limit is 150 . some tech modified it at 100gb now it was not working, no booting but if i mounted it i was able to acces it, edit files etc i asked for help at solusvm.com and pcsmartmanagement.com they tryed to help but i dont know how they do it cuz now i cant even mount the vps. they say that is damaged. i mount it, it says 108gb used, so files should be there, i dont KNOW WHAT THEY have done. now they wont speak with me, they are deleting my tickets. how can i fix it? i can pay if neede, im in nasty situation. atleast as was before they damaged it. to acces /home and /var/lib/mysql. i get this error at startup thank you
no, after they screwed up, after i mount and i try to get in, i get this ls: reading directory .: Input/output error
Well since it looks like it's already f*cked up, you could try to run an fsck on the partition? unmount the disc and run: fsck -a <device>
what this process do? i think the people whu scre*ed this already run that process. the thing is that i have like this /dev/mapper/neh24gb-vm132_img 148G 108G 33G 77% /home/31rofdns 108gb occupied. data should be there. now some friend is copiing entire server to try help me.
Is this an lvm partition? unmount it and run: fsck -a /dev/mapper/neh24gb-vm132_img it checks the partition and file/dir structure.
fsck 1.39 (29-May-2006) /dev/mapper/neh24gb-vm132_img contains a file system with errors, check forced. /dev/mapper/neh24gb-vm132_img: Deleted inode 196738 has zero dtime. FIXED. /dev/mapper/neh24gb-vm132_img: Inode 13210513, i_blocks is 56, should be 144. F IXED. /dev/mapper/neh24gb-vm132_img: Inode 13371024, i_blocks is 72, should be 160. F IXED. /dev/mapper/neh24gb-vm132_img: Inode 13409854, i_blocks is 88, should be 176. F IXED. /dev/mapper/neh24gb-vm132_img: Inode 13524763, i_blocks is 72, should be 160. F IXED. /dev/mapper/neh24gb-vm132_img: Inode 13536617, i_blocks is 56, should be 144. F IXED. /dev/mapper/neh24gb-vm132_img: Inode 13676772, i_blocks is 48, should be 136. F IXED. /dev/mapper/neh24gb-vm132_img: Inode 13723472, i_blocks is 160, should be 248. FIXED. /dev/mapper/neh24gb-vm132_img: Inode 13773922, i_blocks is 64, should be 152. F IXED. /dev/mapper/neh24gb-vm132_img: Inode 13792167, i_blocks is 32, should be 120. F IXED. /dev/mapper/neh24gb-vm132_img: Inode 13807713, i_blocks is 64, should be 152. F IXED. /dev/mapper/neh24gb-vm132_img: Inode 13830954, i_blocks is 48, should be 136. F IXED. /dev/mapper/neh24gb-vm132_img: Inode 15353809, i_blocks is 88, should be 176. F IXED. /dev/mapper/neh24gb-vm132_img: Inode 15553825, i_blocks is 64, should be 152. F IXED. /dev/mapper/neh24gb-vm132_img: Inode 16127809, i_blocks is 64, should be 152. F IXED. /dev/mapper/neh24gb-vm132_img: Inode 16148279, i_blocks is 64, should be 152. F IXED. /dev/mapper/neh24gb-vm132_img: Inode 16320406, i_blocks is 72, should be 160. F IXED. /dev/mapper/neh24gb-vm132_img: Inode 16468563, i_blocks is 64, should be 152. F IXED. /dev/mapper/neh24gb-vm132_img: Inode 16791564, i_blocks is 184, should be 272. FIXED. /dev/mapper/neh24gb-vm132_img: Inode 16926428, i_blocks is 64, should be 152. F IXED. /dev/mapper/neh24gb-vm132_img: Inode 16931439, i_blocks is 48, should be 136. F IXED. /dev/mapper/neh24gb-vm132_img: Inode 17019646, i_blocks is 96, should be 184. F IXED. /dev/mapper/neh24gb-vm132_img: Inode 17060887, i_blocks is 144, should be 232. FIXED. /dev/mapper/neh24gb-vm132_img: Inode 17085832, i_blocks is 56, should be 144. F IXED. /dev/mapper/neh24gb-vm132_img: Inode 17199706 has illegal block(s). /dev/mapper/neh24gb-vm132_img: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options)
keep running "fsck -y /dev/mapper/neh24gb-vm132_img" till you get no more errors (-y this time, it'll auto "yes" for you) else run w/o -y and submit "yes" for each fix
thank you. the process finished, i mounted image and it created an folder lost+found with many many files like this whats next?
Those are corrupted files found by fsck, most of the time you can delete them, but once in a while there's a chance one of those files is the one you lost. Anyway, those files aren't important at the moment, what's more important is if you are able to mount the disc and read the content of it so you can backup your files?
