Jump to content

Omega16

Members
  • Posts

    12
  • Joined

  • Last visited

Reputation

10 Good

About Omega16

  • Rank
    Registered user
    Newbie
  • Birthday 03/14/1986

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Am rezolvat problema astfel: 1. Am facut backup cu utilitarul TestDisk (foarte bun, recomand), salvand datele pe alt HDD. 2. Am sters logical volume pe care era /home si l-am recreat. 3. Am copiat datele salvate anterior pe /home. Asta a fost doar o alternativa, insa repararea "volumului logic" nu a reusit in niciun fel. Toate comenzile conduceau la rezultatul: "The filesystem size (according to the superblock) is 195463168 blocks The physical size of the device is 182093824 blocks Either the superblock or the partition table is likely to be corrupt!". Daca totusi ii s-a intamplat cuiva si a reusit sa-l repare fara sa piarda datele, sa ne spuna si noua. Cine stie cand are careva nevoie. Multumesc
  2. Salut. Un amic a incercat sa modifice niste partitii pe un CentOS astfel: sa "ia" 50 GB de la /home si sa-i adauge la /root. Nu stiu exact ce comenzi a folosit, in orice caz, a facut dupa un tutorial de pe net. Din cate m-am uitat eu, nu a modificat si file systemul. Acum /home da erori si sistemul nu mai porneste. Am reusit totusi sa-l pornesc, prin editarea fstab si comentarea liniei aferenta /home. root@web [/home]# fsck.ext4 -v /dev/mapper/vg_web-lv_home e2fsck 1.41.12 (17-May-2010) The filesystem size (according to the superblock) is 195463168 blocks The physical size of the device is 182093824 blocks Either the superblock or the partition table is likely to be corrupt! Abort<y>? no /dev/mapper/vg_web-lv_home contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Error reading block 183500832 (Invalid argument) while getting next inode from scan. Ignore error<y>? yes Force rewrite<y>? yes Error writing block 183500832 (Invalid argument) while getting next inode from scan. Ignore error<y>? yes Error reading block 183500833 (Invalid argument) while getting next inode from scan. Ignore error<y>? yes Force rewrite<y>? yes Error reading block 184549408 (Invalid argument) while getting next inode from scan. Ignore error<y>? no Error while scanning inodes (45875236): Can't read next inode e2fsck: aborted Si tot asa.....De aici, am tot cauta pe net cum sa pot rezolva, dar nimic nu merge. Vreo idee? Multumesc
×
×
  • Create New...