2015-02-13 14:54 GMT+02:00 manuel "lonely wolf" wolfshant <wo...@prolinux.ro >:
> > > > Problema e ca a failuit intr-un mod extrem de mizerabil, imho. > exista si fail placut ? :)) > Sigur, nu era un principiu "fail early, with the least harm done" ? M-as fi astepta la ceva de genul "hei, am observat ca nu pot updata pachetul X, am sa ma opresc aici". Eventual sa incerce un rollback. Spre deosebire de "am sa instalez pe jum'ate toate pachetele, si am sa las fisiere corupte pe tot discul". > > > > >La un moment dat desigur ca am dat reboot, si se panicheaza cu "VFS: > > Cannot > > open root device UUID=.... or unknown-block(0,0)" > > btw, asta rimeaza cu un initramfs incorect generat ( care de asemenea > rimeaza, ca si toate pb de dinainte, cu erori de disc ), am patit-o si > eu acum vreo 2 sapt > Intr-adevar, initramfs-ul de la kernelul nou nu era bun :) Anyway, ca sa incheiem povestea. Am gasit ceva interesant in /var/log/messages: Feb 13 00:08:12 eg-PB-proc3 yum[39971]: Updated: libgcc-4.4.7-11.el6.x86_64 Feb 13 00:08:12 eg-PB-proc3 yum[39971]: Updated: centos-release-6-6.el6.centos.12.2.x86_64 Feb 13 00:08:13 eg-PB-proc3 kernel: EXT4-fs error (device vda2): ext4_free_inode: bit already cleared for inode 46758 Feb 13 00:08:13 eg-PB-proc3 kernel: EXT4-fs error (device vda2): ext4_claim_inode: reserved inode or inode > inodes count - block_group = 0, inode=3 Feb 13 00:08:13 eg-PB-proc3 kernel: EXT4-fs error (device vda2): ext4_claim_inode: reserved inode or inode > inodes count - block_group = 0, inode=4 Feb 13 00:08:13 eg-PB-proc3 kernel: EXT4-fs error (device vda2): ext4_claim_inode: reserved inode or inode > inodes count - block_group = 0, inode=7 Feb 13 00:08:13 eg-PB-proc3 kernel: EXT4-fs error (device vda2): ext4_claim_inode: reserved inode or inode > inodes count - block_group = 0, inode=8 Feb 13 00:08:13 eg-PB-proc3 kernel: EXT4-fs error (device vda2): ext4_claim_inode: reserved inode or inode > inodes count - block_group = 0, inode=9 Feb 13 00:08:13 eg-PB-proc3 kernel: EXT4-fs error (device vda2): ext4_claim_inode: reserved inode or inode > inodes count - block_group = 0, inode=10 Feb 13 00:08:13 eg-PB-proc3 yum[39971]: kernel-headers-2.6.32-504.8.1.el6.x86_64: 100 Feb 13 00:08:13 eg-PB-proc3 yum[39971]: 12:dhcp-common-4.1.1-43.P1.el6.centos.1.x86_64: 100 Feb 13 00:08:15 eg-PB-proc3 yum[39971]: Updated: kernel-firmware-2.6.32-504.8.1.el6.noarch Feb 13 00:08:15 eg-PB-proc3 yum[39971]: tzdata-2015a-1.el6.noarch: 100 Feb 13 00:08:15 eg-PB-proc3 yum[39971]: nss-softokn-freebl-3.14.3-22.el6_6.x86_64: 100 Feb 13 00:08:15 eg-PB-proc3 yum[39971]: bash-4.1.2-29.el6.x86_64: 100 Feb 13 00:08:15 eg-PB-proc3 yum[39971]: glibc-common-2.12-1.149.el6_6.5.x86_64: 100 Feb 13 00:08:15 eg-PB-proc3 yum[39971]: glibc-2.12-1.149.el6_6.5.x86_64: 100 etc. Deci se pare ca a fost ceva problema de consistenta cu FS-ul (vda2 e / ). Intre timp am refacut masina -- nici macar de la zero, am reusit s-o recuperez: montat discul intr-o alta, fsck, restore din backup. A mai fost nevoie apoi si de chroot && grub-install, ca era stricat pana si grub. (se agata dupa "Booting from hard disk", cred ca la stage1 ca nu aparea promptul de Grub sa selectez kernelul). -- flo.ro _______________________________________________ RLUG mailing list RLUG@lists.lug.ro http://lists.lug.ro/mailman/listinfo/rlug
