[Risolto] si blocca all'avvio

Fedora Linux Configurazione
#61

Se non possiamo accontentare il servizio problematico… Proviamo a disabilitarlo!
N.B.: includo anche una query dalla cronologia di dnf, per vedere se l’inconveniente è stato introdotto da qualche aggiornamento. Quindi… Come hai correttamente fatto fino ad ora, riporta qui tutto il listato del terminale.

Da live:

# mkdir /mnt/fedora
# mount /dev/mapper/vg_luca-lv_root /mnt/fedora
# mount /dev/sda1 /mnt/fedora/boot
# for i in {/dev/,/dev/pts/,/proc/,/sys/}; do mount -o bind "$i" "/mnt/fedora$i"; done
# chroot /mnt/fedora
# dnf history info last
# systemctl disable systemd-vconsole-setup.service
# exit
# for i in {/boot/,/sys/,/proc/,/dev/pts/,/dev/}; do umount "/mnt/fedora$i"; done
# umount /mnt/fedora

Avvia il sistema installato e verifica se completa il boot. Se anche così non funziona (altrimenti ignora i comandi successivi), torna sulla live e riabilita il servizio incriminato:

# mkdir /mnt/fedora
# mount /dev/mapper/vg_luca-lv_root /mnt/fedora
# mount /dev/sda1 /mnt/fedora/boot
# for i in {/dev/,/dev/pts/,/proc/,/sys/}; do mount -o bind "$i" "/mnt/fedora$i"; done
# chroot /mnt/fedora
# systemctl enable systemd-vconsole-setup.service
# exit
# for i in {/boot/,/sys/,/proc/,/dev/pts/,/dev/}; do umount "/mnt/fedora$i"; done
# umount /mnt/fedora
#62

incrocio le dita.

[liveuser@localhost ~]$ su - [root@localhost ~]# mkdir /mnt/fedora [root@localhost ~]# mount /dev/mapper/vg_luca-lv_root /mnt/fedora [root@localhost ~]# mount /dev/sda1 /mnt/fedora/boot [root@localhost ~]# for i in {/dev/,/dev/pts/,/proc/,/sys/}; do mount -o bind "$i" "/mnt/fedora$i"; done [root@localhost ~]# chroot /mnt/fedora [root@localhost /]# dnf history info last Last metadata expiration check performed 29 days, 0:36:59 ago on Thu Jan 21 14:53:31 2016. Transaction ID : 192 Begin time : Wed Jan 20 08:43:49 2016 Begin rpmdb : 3496:5dc05ba5f76bd9a75b3685c3ba7658a85471208f End time : 08:46:58 2016 (189 seconds) End rpmdb : 3496:91655fc38716cce6d6974a71e97ab80dd5216def User : luca <luca> Return-Code : Success Transaction performed with: Installed dnf-1.1.5-1.fc23.noarch @updates Installed rpm-4.13.0-0.rc1.7.fc23.i686 @updates Packages Altered: Upgraded boost-1.58.0-10.fc23.i686 @updates Upgrade 1.58.0-11.fc23.i686 @updates Upgraded boost-atomic-1.58.0-10.fc23.i686 @updates Upgrade 1.58.0-11.fc23.i686 @updates Upgraded boost-chrono-1.58.0-10.fc23.i686 @updates Upgrade 1.58.0-11.fc23.i686 @updates Upgraded boost-container-1.58.0-10.fc23.i686 @updates Upgrade 1.58.0-11.fc23.i686 @updates Upgraded boost-context-1.58.0-10.fc23.i686 @updates Upgrade 1.58.0-11.fc23.i686 @updates Upgraded boost-coroutine-1.58.0-10.fc23.i686 @updates Upgrade 1.58.0-11.fc23.i686 @updates Upgraded boost-date-time-1.58.0-10.fc23.i686 @updates Upgrade 1.58.0-11.fc23.i686 @updates Upgraded boost-devel-1.58.0-10.fc23.i686 @updates Upgrade 1.58.0-11.fc23.i686 @updates Upgraded boost-filesystem-1.58.0-10.fc23.i686 @updates Upgrade 1.58.0-11.fc23.i686 @updates Upgraded boost-graph-1.58.0-10.fc23.i686 @updates Upgrade 1.58.0-11.fc23.i686 @updates Upgraded boost-iostreams-1.58.0-10.fc23.i686 @updates Upgrade 1.58.0-11.fc23.i686 @updates Upgraded boost-locale-1.58.0-10.fc23.i686 @updates Upgrade 1.58.0-11.fc23.i686 @updates Upgraded boost-log-1.58.0-10.fc23.i686 @updates Upgrade 1.58.0-11.fc23.i686 @updates Upgraded boost-math-1.58.0-10.fc23.i686 @updates Upgrade 1.58.0-11.fc23.i686 @updates Upgraded boost-program-options-1.58.0-10.fc23.i686 @updates Upgrade 1.58.0-11.fc23.i686 @updates Upgraded boost-python-1.58.0-10.fc23.i686 @updates Upgrade 1.58.0-11.fc23.i686 @updates Upgraded boost-python3-1.58.0-10.fc23.i686 @updates Upgrade 1.58.0-11.fc23.i686 @updates Upgraded boost-random-1.58.0-10.fc23.i686 @updates Upgrade 1.58.0-11.fc23.i686 @updates Upgraded boost-regex-1.58.0-10.fc23.i686 @updates Upgrade 1.58.0-11.fc23.i686 @updates Upgraded boost-serialization-1.58.0-10.fc23.i686 @updates Upgrade 1.58.0-11.fc23.i686 @updates Upgraded boost-signals-1.58.0-10.fc23.i686 @updates Upgrade 1.58.0-11.fc23.i686 @updates Upgraded boost-system-1.58.0-10.fc23.i686 @updates Upgrade 1.58.0-11.fc23.i686 @updates Upgraded boost-test-1.58.0-10.fc23.i686 @updates Upgrade 1.58.0-11.fc23.i686 @updates Upgraded boost-thread-1.58.0-10.fc23.i686 @updates Upgrade 1.58.0-11.fc23.i686 @updates Upgraded boost-timer-1.58.0-10.fc23.i686 @updates Upgrade 1.58.0-11.fc23.i686 @updates Upgraded boost-wave-1.58.0-10.fc23.i686 @updates Upgrade 1.58.0-11.fc23.i686 @updates Upgraded cups-filters-1.4.0-1.fc23.i686 @updates Upgrade 1.6.0-1.fc23.i686 @updates Upgraded cups-filters-libs-1.4.0-1.fc23.i686 @updates Upgrade 1.6.0-1.fc23.i686 @updates Upgraded devede-3.23.0-4.fc22.noarch (unknown) Upgrade 3.23.0-5.20140821git.fc23.noarch @rpmfusion-free-updates-testing Upgraded ffmpeg-2.8.4-1.fc23.i686 @rpmfusion-free-updates-testing Upgrade 2.8.5-1.fc23.i686 @rpmfusion-free-updates-testing Upgraded ffmpeg-libs-2.8.4-1.fc23.i686 @rpmfusion-free-updates-testing Upgrade 2.8.5-1.fc23.i686 @rpmfusion-free-updates-testing Upgraded flite-1.3-23.fc22.i686 (unknown) Upgrade 1.3-25.fc23.i686 @updates Upgraded kde-l10n-15.08.3-1.fc23.noarch @updates Upgrade 15.08.3-2.fc23.noarch @updates Upgraded libavdevice-2.8.4-1.fc23.i686 @rpmfusion-free-updates-testing Upgrade 2.8.5-1.fc23.i686 @rpmfusion-free-updates-testing Upgraded libetonyek-0.1.5-1.fc23.i686 @updates Upgrade 0.1.6-1.fc23.i686 @updates Upgraded perl-PathTools-3.60-2.fc23.i686 @updates Upgrade 3.62-1.fc23.i686 @updates Scriptlet output: 1 warning: /etc/cups/cups-browsed.conf created as /etc/cups/cups-browsed.conf.rpmnew [root@localhost /]# systemctl disable systemd-vconsole-setup.service [root@localhost /]# exit exit [root@localhost ~]# for i in {/boot/,/sys/,/proc/,/dev/pts/,/dev/}; do umount "/mnt/fedora$i"; done [root@localhost ~]# umount /mnt/fedora [root@localhost ~]#

#63

niente, anche cosi’ non cambia nulla…

[code][liveuser@localhost ~]$ su -
[root@localhost ~]# mkdir /mnt/fedora
[root@localhost ~]# mount /dev/mapper/vg_luca-lv_root /mnt/fedora
[root@localhost ~]# mount /dev/sda1 /mnt/fedora/boot
[root@localhost ~]# for i in {/dev/,/dev/pts/,/proc/,/sys/}; do mount -o bind “$i” “/mnt/fedora$i”; done
[root@localhost ~]# chroot /mnt/fedora
[root@localhost /]# systemctl enable systemd-vconsole-setup.service
The unit files have no [Install] section. They are not meant to be enabled
using systemctl.
Possible reasons for having this kind of units are:

  1. A unit may be statically enabled by being symlinked from another unit’s
    .wants/ or .requires/ directory.
  2. A unit’s purpose may be to act as a helper for some other unit which has
    a requirement dependency on it.
  3. A unit may be started when needed via activation (socket, path, timer,
    D-Bus, udev, scripted systemctl call, …).
    [root@localhost /]# exit
    exit
    [root@localhost ~]# for i in {/boot/,/sys/,/proc/,/dev/pts/,/dev/}; do umount “/mnt/fedora$i”; done
    [root@localhost ~]# umount /mnt/fedora
    [root@localhost ~]#
    [/code]
#64

Allora. La situazione è questa: il 21/01 è stata l’ultima volta che il sistema è stato avviato. Non è stata effettuata alcuna operazione particolare: Fedora, senza nessun motivo apparente, ha smesso di funzionare. L’ultima operazione con dnf è avvenuta il 20/01, quindi possiamo escludere l’introduzione di un qualche problema a causa di un aggiornamento.

Inoltre… Riguardando il journal, il servizio “systemd-vconsole-setup.service” molto probabilmente falliva già a suo tempo, quindi mi verrebbe da dire che non sia la vera causa del problema. Viene invece riportato un avvertimento di fsck.

Quindi… Toglimi una curiosità… L’hard disk e i vari filesystem sono in buono stato? Dalla live, vediamo:

# fsck -M /dev/mapper/vg_luca-lv_root
# fsck -M /dev/mapper/vg_luca-lv_home
# fsck -M /dev/sda1
# smartctl --info /dev/sda | grep "support"
# smartctl -c /dev/sda
#65

eccoti

[code][liveuser@localhost ~]$ su -
[root@localhost ~]# fsck -M /dev/mapper/vg_luca-lv_root
fsck from util-linux 2.27
e2fsck 1.42.13 (17-May-2015)
/dev/mapper/vg_luca-lv_root contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix? yes
Inode 2280321 was part of the orphaned inode list. FIXED.
Deleted inode 2280322 has zero dtime. Fix? yes
Inode 2280323 was part of the orphaned inode list. FIXED.
Deleted inode 2280324 has zero dtime. Fix? yes
Inode 2280325 is in use, but has dtime set. Fix? yes
Inode 2280325, i_size is 15136035397638815745, should be 0. Fix? yes
Inode 2280325, i_blocks is 3524132864, should be 0. Fix? yes
Inode 2280326 is in use, but has dtime set. Fix? yes
Inode 2280326, i_size is 15280150589222027264, should be 0. Fix? yes
Inode 2280326, i_blocks is 3557687296, should be 0. Fix? yes
Inode 2280327 is in use, but has dtime set. Fix? yes
Inode 2280327, i_size is 15424265777331437568, should be 0. Fix? yes
Inode 2280327, i_blocks is 3591241728, should be 0. Fix? yes
Inode 2280328 is in use, but has dtime set. Fix? yes
Inode 2280328, i_size is 15424265777448878080, should be 0. Fix? yes
Inode 2280328, i_blocks is 3591241728, should be 0. Fix? yes
Inode 2280329 is in use, but has dtime set. Fix? yes
Inode 2280329, i_size is 15424265777381769216, should be 0. Fix? yes
Inode 2280329, i_blocks is 3591241728, should be 0. Fix? yes
Inode 2280330 is in use, but has dtime set. Fix? yes
Inode 2280330, i_size is 15424265777381769216, should be 0. Fix? yes
Inode 2280330, i_blocks is 3591241728, should be 0. Fix? yes
Inode 2280331 is in use, but has dtime set. Fix? yes
Inode 2280331, i_size is 15424265777381769216, should be 0. Fix? yes
Inode 2280331, i_blocks is 3591241728, should be 0. Fix? yes
Inode 2280332 is in use, but has dtime set. Fix? yes
Inode 2280332, i_size is 16361014500092936192, should be 0. Fix? yes
Inode 2280332, i_blocks is 3809345536, should be 0. Fix? yes
Inode 2280333 is in use, but has dtime set. Fix? yes
Inode 2280333, i_size is 16577187282206720000, should be 0. Fix? yes
Inode 2280333, i_blocks is 3809345536, should be 0. Fix? yes
Inode 2280334 is in use, but has dtime set. Fix? yes
Inode 2280334, i_size is 15424265777683759104, should be 0. Fix? yes
Inode 2280334, i_blocks is 3591241728, should be 0. Fix? yes
Inode 2280335 is in use, but has dtime set. Fix? yes
Inode 2280335, i_size is 15424265777717313536, should be 0. Fix? yes
Inode 2280335, i_blocks is 3591241728, should be 0. Fix? yes
Inode 2280336 is in use, but has dtime set. Fix? yes
Inode 2280336, i_size is 15424265777767645184, should be 0. Fix? yes
Inode 2280336, i_blocks is 3993894912, should be 0. Fix? yes
Inode 2280337 is in use, but has dtime set. Fix? yes
Inode 2280337, i_size is 15424265777381769216, should be 0. Fix? yes
Inode 2280337, i_blocks is 3591241728, should be 0. Fix? yes
Inode 2280338 is in use, but has dtime set. Fix? yes
Inode 2280338, i_size is 17946281569229340672, should be 0. Fix? yes
Inode 2280338, i_blocks is 4144889856, should be 0. Fix? yes
Inode 2280339 is in use, but has dtime set. Fix? yes
Inode 2280339, i_size is 18090396757389082624, should be 0. Fix? yes
Inode 2280339, i_blocks is 4195221504, should be 0. Fix? yes
Inode 2280340 is in use, but has dtime set. Fix? yes
Inode 2280340, i_size is 436567693090226176, should be 0. Fix? yes
Inode 2280340, i_blocks is 16777216, should be 0. Fix? yes
Inode 2280341 was part of the orphaned inode list. FIXED.
Inode 2280342 is in use, but has dtime set. Fix? yes
Inode 2280342 has imagic flag set. Clear? yes
Inode 2280342 has a extra size (25963) which is invalid
Fix? yes
Inode 2280343 is in use, but has dtime set. Fix? yes
Inode 2280343 has imagic flag set. Clear? yes
Inode 2280343 has a extra size (11828) which is invalid
Fix? yes
Inode 2280343 has compression flag set on filesystem without compression support. Clear? yes
Inode 2280343, i_size is 3386759057148948019, should be 0. Fix? yes
Inode 2280343, i_blocks is 125840115576677, should be 0. Fix? yes
Inode 2280344 is in use, but has dtime set. Fix? yes
Inode 2280344 has imagic flag set. Clear? yes
Inode 2280344 has a extra size (28271) which is invalid
Fix? yes
Inode 2280344 has compression flag set on filesystem without compression support. Clear? yes
Inode 2280344, i_size is 3630858074013460783, should be 0. Fix? yes
Inode 2280344, i_blocks is 59616066219890, should be 0. Fix? yes
Inode 2280345 is in use, but has dtime set. Fix? yes
Inode 2280345 has imagic flag set. Clear? yes
Inode 2280345 has a extra size (30828) which is invalid
Fix? yes
Inode 2280346 is in use, but has dtime set. Fix? yes
Inode 2280346 has imagic flag set. Clear? yes
Inode 2280346 has a extra size (11827) which is invalid
Fix? yes
Inode 2280347 is in use, but has dtime set. Fix? yes
Inode 2280347 has imagic flag set. Clear? yes
Inode 2280347 has a extra size (11824) which is invalid
Fix? yes
Inode 2280348 is in use, but has dtime set. Fix? yes
Inode 2280348 has imagic flag set. Clear? yes
Inode 2280348 has a extra size (12136) which is invalid
Fix? yes
Inode 2280348 has compression flag set on filesystem without compression support. Clear? yes
Inode 2280348, i_size is 3415814730893128293, should be 0. Fix? yes
Inode 2280348, i_blocks is 55183504520760, should be 0. Fix? yes
Inode 2280349 is in use, but has dtime set. Fix? yes
Inode 2280349 has imagic flag set. Clear? yes
Inode 2280349 has a extra size (12131) which is invalid
Fix? yes
Inode 2280350 is in use, but has dtime set. Fix? yes
Inode 2280350 has imagic flag set. Clear? yes
Inode 2280350 has a extra size (25974) which is invalid
Fix? yes
Inode 2280351 is in use, but has dtime set. Fix? yes
Inode 2280351 has imagic flag set. Clear? yes
Inode 2280351 has a extra size (29548) which is invalid
Fix? yes
Inode 2280351, i_size is 8314609387606207279, should be 0. Fix? yes
Inode 2280351, i_blocks is 125839156459113, should be 0. Fix? yes
Inode 2280352 is in use, but has dtime set. Fix? yes
Inode 2280352 has a extra size (12086) which is invalid
Fix? yes
Inode 2280352, i_size is 3329338196411037289, should be 0. Fix? yes
Inode 2280352, i_blocks is 52997436695087, should be 0. Fix? yes
Inode 2280350 has compression flag set on filesystem without compression support. Clear? yes
Inode 2280350, i_size is 7955942127335531876, should be 0. Fix? yes
Inode 2280350, i_blocks is 52111613374323, should be 0. Fix? yes
Inode 2280349 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes
Inode 2280349, i_size is 7164779708573968483, should be 0. Fix? yes
Inode 2280349, i_blocks is 109054272941619, should be 0. Fix? yes
Inode 2280342 has compression flag set on filesystem without compression support. Clear? yes
Inode 2280342, i_size is 7453294858215894899, should be 0. Fix? yes
Inode 2280342, i_blocks is 52125408521315, should be 0. Fix? yes
Inode 2280347, i_size is 3414698781633427049, should be 0. Fix? yes
Inode 2280347, i_blocks is 119181872804400, should be 0. Fix? yes
Inode 2280345 has compression flag set on filesystem without compression support. Clear? yes
Inode 2280345 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes
Inode 2280345, i_size is 3906932503228804461, should be 0. Fix? yes
Inode 2280345, i_blocks is 129107575583534, should be 0. Fix? yes
Inode 2280346, i_size is 8319607565501951602, should be 0. Fix? yes
Inode 2280346, i_blocks is 52104100654902, should be 0. Fix? yes
Pass 2: Checking directory structure
Entry ‘San_Juan’ in /usr/share/zoneinfo/America/Argentina (2097920) has deleted/unused inode 2099512. Clear? yes
Entry ‘Windows-1255’ in /usr/share/poppler/unicodeMap (2099501) has deleted/unused inode 2099507. Clear? yes
Entry ‘Shift-JIS’ in /usr/share/poppler/unicodeMap (2099501) has deleted/unused inode 2099505. Clear? yes
Entry ‘TIS-620’ in /usr/share/poppler/unicodeMap (2099501) has deleted/unused inode 2099506. Clear? yes
Entry ‘Tucuman’ in /usr/share/javazi/America/Argentina (2100501) has deleted/unused inode 2099516. Clear? yes
Entry ‘serviceproviders.xml’ in /usr/share/mobile-broadband-provider-info (2101142) has deleted/unused inode 2099511. Clear? yes
Entry ‘archive-open.page’ in /usr/share/help/da/file-roller (2113493) has deleted/unused inode 2099514. Clear? yes
Entry ‘README’ in /usr/share/doc/vinagre (2220871) has deleted/unused inode 2099515. Clear? yes
Entry ‘openbios-ppc’ in /usr/share/qemu (2112365) has deleted/unused inode 2099508. Clear? yes
Entry ‘RamPatch.txt’ in /usr/lib/firmware/ar3k/1020201 (2120877) has deleted/unused inode 2099510. Clear? yes
Entry ‘security.h’ in /usr/src/kernels/4.2.8-300.fc23.i686+PAE/include/linux (2089553) has deleted/unused inode 2280341. Clear? yes
Inode 2280326 (/usr/src/kernels/4.2.8-300.fc23.i686+PAE/include/linux/sched.h) has invalid mode (00).
Clear? yes
Entry ‘libevoablo.so’ in /usr/lib/libreoffice/program (2113049) has deleted/unused inode 2099519. Clear? yes
Entry ‘IBM1142.so’ in /usr/lib/gconv (2110551) has deleted/unused inode 2099518. Clear? yes
Entry ‘IBM1141.so’ in /usr/lib/gconv (2110551) has deleted/unused inode 2099517. Clear? yes
Entry ‘BNG2-OTF.flt’ in /usr/share/m17n (2097685) has deleted/unused inode 2099513. Clear? yes
Entry ‘libmsformslo.so’ in /usr/lib/libreoffice/program (2113049) has deleted/unused inode 2099520. Clear? yes
Entry ‘gcc.mo’ in /usr/share/locale/uk/LC_MESSAGES (2097200) has deleted/unused inode 2099509. Clear? yes
Entry ‘security.h’ in /usr/src/kernels/4.2.8-300.fc23.i686/include/linux (2187888) has deleted/unused inode 2280341. Clear? yes
Entry ‘sched.h’ in /usr/src/kernels/4.2.8-300.fc23.i686/include/linux (2187888) has deleted/unused inode 2280326. Clear? yes
Entry ‘security.h’ in /usr/src/kernels/4.3.3-300.fc23.i686+PAE/include/linux (2220793) has deleted/unused inode 2280341. Clear? yes
Entry ‘security.h’ in /usr/src/kernels/4.3.3-300.fc23.i686/include/linux (2294824) has deleted/unused inode 2280341. Clear? yes
Entry ‘security.h’ in /usr/src/kernels/4.2.7-300.fc23.i686+PAE/include/linux (2408865) has deleted/unused inode 2280341. Clear? yes
Entry ‘sched.h’ in /usr/src/kernels/4.2.7-300.fc23.i686+PAE/include/linux (2408865) has deleted/unused inode 2280326. Clear? yes
Entry ‘sched.h’ in /usr/src/kernels/4.2.7-300.fc23.i686/include/linux (2482350) has deleted/unused inode 2280326. Clear? yes
Entry ‘security.h’ in /usr/src/kernels/4.2.7-300.fc23.i686/include/linux (2482350) has deleted/unused inode 2280341. Clear? yes
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Inode 2280325 (…) has invalid mode (00).
Clear? yes
Inode 2280327 (…) has invalid mode (00).
Clear? yes
Inode 2280328 (…) has invalid mode (00).
Clear? yes
Inode 2280329 (…) has invalid mode (00).
Clear? yes
Inode 2280330 (…) has invalid mode (00).
Clear? yes
Inode 2280331 (…) has invalid mode (00).
Clear? yes
Inode 2280332 (…) has invalid mode (00).
Clear? yes
Inode 2280333 (…) has invalid mode (00).
Clear? yes
Inode 2280334 (…) has invalid mode (00).
Clear? yes
Inode 2280335 (…) has invalid mode (00).
Clear? yes
Inode 2280336 (…) has invalid mode (00).
Clear? yes
Inode 2280337 (…) has invalid mode (00).
Clear? yes
Inode 2280338 (…) has invalid mode (00).
Clear? yes
Inode 2280339 (…) has invalid mode (00).
Clear? yes
Inode 2280340 (…) has invalid mode (00).
Clear? yes
Inode 2280342 (…) is an illegal block device.
Clear? yes
Inode 2280343 (…) is an illegal character device.
Clear? yes
Inode 2280344 (…) has invalid mode (033151).
Clear? yes
Inode 2280345 (…) has invalid mode (071554).
Clear? yes
Inode 2280346 (…) is an illegal character device.
Clear? yes
Inode 2280347 (…) has invalid mode (031143).
Clear? yes
Inode 2280348 (…) is an illegal block device.
Clear? yes
Inode 2280349 (…) is an illegal character device.
Clear? yes
Inode 2280350 (…) has invalid mode (071163).
Clear? yes
Inode 2280351 (…) has invalid mode (071457).
Clear? yes
Inode 2280352 (…) has invalid mode (031143).
Clear? yes
Pass 5: Checking group summary information
Block bitmap differences: -(117561–117665) -(141654–141836) -8424004 -(8430136–8430137) -8436524 -8441114 -8442390 -8459986 -8459997 -(8475592–8475597) -(8514280–8514285) -(8514700–8514708) -(8557221–8557237) -(8999040–8999062) -(8999089–8999099) -(11545460–11545537) -(11546097–11546177)
Fix? yes
Free blocks count wrong for group #3 (4772, counted=4877).
Fix? yes
Free blocks count wrong for group #4 (10245, counted=10428).
Fix? yes
Free blocks count wrong for group #257 (207, counted=213).
Fix? yes
Free blocks count wrong for group #258 (7303, counted=7311).
Fix? yes
Free blocks count wrong for group #259 (12794, counted=12809).
Fix? yes
Free blocks count wrong for group #261 (8620, counted=8637).
Fix? yes
Free blocks count wrong for group #274 (7466, counted=7500).
Fix? yes
Free blocks count wrong for group #352 (8778, counted=8937).
Fix? yes
Free blocks count wrong (2224964, counted=2225491).
Fix? yes
Inode bitmap differences: -(2099505–2099520) -2280341
Fix? yes
Free inodes count wrong for group #256 (0, counted=16).
Fix? yes
Free inodes count wrong for group #278 (5079, counted=5054).
Fix? yes
Free inodes count wrong (2777468, counted=2777459).
Fix? yes
y
/dev/mapper/vg_luca-lv_root: ***** FILE SYSTEM WAS MODIFIED *****
/dev/mapper/vg_luca-lv_root: 499341/3276800 files (1.7% non-contiguous), 10881709/13107200 blocks
[root@localhost ~]# fsck -M /dev/mapper/vg_luca-lv_home
fsck from util-linux 2.27
e2fsck 1.42.13 (17-May-2015)
/dev/mapper/vg_luca-lv_home: clean, 67348/11632640 files, 7723663/46514176 blocks
[root@localhost ~]# fsck -M /dev/sda1
fsck from util-linux 2.27
e2fsck 1.42.13 (17-May-2015)
/dev/sda1: clean, 498/128016 files, 272383/512000 blocks
[root@localhost ~]# smartctl --info /dev/sda | grep “support”
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
[root@localhost ~]# smartctl -c /dev/sda
smartctl 6.4 2015-06-04 r4109 [i686-linux-4.2.3-300.fc23.i686] (local build)
Copyright © 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 103) seconds.
Offline data collection
capabilities: (0x51) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 103) minutes.
SCT capabilities: (0x003f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

[root@localhost ~]#
[/code]

#66

Fsck ha sistemato un gran numero di problemi al filesystem. Prova ora ad avviare normalmente il sistema.

#67

si, adesso è ripartito, che cosa è successo?

#68

Qualche corruzione a livello di filesystem può capitare, soprattutto in caso di spegnimenti forzati e interruzioni di corrente.

Le incongruenze rilevate però, erano veramente tante. Ho paura che il tuo hard disk non sia in buona salute (immagino abbia qualche anno sulle spalle, correggimi se sbaglio).

Per toglierci ogni dubbio, dalla live, possiamo provare ad eseguire un test:

# smartctl -t short /dev/sda

Il comando lancerà un processo diagnostico in background, che durerà all’incirca due minuti. Esso stamperà inoltre un orario in cui i risultati potranno essere visualizzati.

Controlla l’orologio con il seguente:

$ date

Non appena superi l’orario evidenziato da smartctl (prudenzialmente lascia passare un minutino in più), posta questo:

# smartctl -a /dev/sda

P.S.:
Mi spiace di averti fatto perdere del tempo inutilmente, quando la causa era abbastanza evidente; purtroppo sono andato fuori strada appena ho visto che un servizio in particolare falliva.

#69

[quote=arkanoid]

P.S.:
Mi spiace di averti fatto perdere del tempo inutilmente, quando la causa era abbastanza evidente; purtroppo sono andato fuori strada appena ho visto che un servizio in particolare falliva.[/quote]

il tempo non si perde mai…si impara dal tempo che trascorre…

mi sa che per le altre informazioni non riesco a darteli nell’immediato…ho fatto partire gli aggiornamenti…

grazie in anticipo della tua enorme pazienza

#70

Felice di aver finalmente [Risolto] (perlomeno la problematica del mancato avvio… Per il resto, ho paura che l’hard disk sia da sostituire…).

A questo punto, raccomando però un’ultima cosa: backup regolari e frequenti. Il buon fsck sistema quello che può, ma se l’hardware sottostante non è affidabile, non può fare miracoli in eterno.

#71

eccoti le informazioni chieste

[code][liveuser@localhost ~]$ su -
Last login: Fri Feb 19 23:31:16 EST 2016 on pts/0
[root@localhost ~]# smartctl -t short /dev/sda
smartctl 6.4 2015-06-04 r4109 [i686-linux-4.2.3-300.fc23.i686] (local build)
Copyright © 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command: “Execute SMART Short self-test routine immediately in off-line mode”.
Drive command “Execute SMART Short self-test routine immediately in off-line mode” successful.
Testing has begun.
Please wait 2 minutes for test to complete.
Test will complete after Fri Feb 19 23:34:03 2016

Use smartctl -X to abort test.
[root@localhost ~]# exit
logout
[liveuser@localhost ~]$ date
Fri Feb 19 23:33:56 EST 2016
[liveuser@localhost ~]$ su -
Last login: Fri Feb 19 23:31:45 EST 2016 on pts/0
[root@localhost ~]# smartctl -a /dev/sda
smartctl 6.4 2015-06-04 r4109 [i686-linux-4.2.3-300.fc23.i686] (local build)
Copyright © 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: SAMSUNG SpinPoint M6
Device Model: SAMSUNG HM251JI
Serial Number: S1BVJDNS510589
LU WWN Device Id: 5 0f0000 0e3510589
Firmware Version: 2SS00_03
User Capacity: 250,059,350,016 bytes [250 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS, ATA/ATAPI-7 T13/1532D revision 0
SATA Version is: SATA 2.5, 3.0 Gb/s
Local Time is: Fri Feb 19 23:36:55 2016 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
See vendor-specific Attribute list for marginal Attributes.

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 103) seconds.
Offline data collection
capabilities: (0x51) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 103) minutes.
SCT capabilities: (0x003f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 100 100 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0007 252 252 025 Pre-fail Always - 2812
4 Start_Stop_Count 0x0032 093 093 000 Old_age Always - 7327
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 2
7 Seek_Error_Rate 0x000f 252 252 051 Pre-fail Always - 0
8 Seek_Time_Performance 0x0025 252 252 015 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 084 084 000 Old_age Always - 8569
10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always - 1
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 879
12 Power_Cycle_Count 0x0032 097 097 000 Old_age Always - 3769
184 End-to-End_Error 0x0033 252 252 070 Pre-fail Always - 0
187 Reported_Uncorrect 0x0032 252 252 000 Old_age Always - 0
188 Command_Timeout 0x0032 252 252 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 043 031 040 Old_age Always In_the_past 57 (Min/Max 10/69)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 3608
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 508
193 Load_Cycle_Count 0x0032 096 096 000 Old_age Always - 41202
194 Temperature_Celsius 0x0022 043 031 000 Old_age Always - 57 (Min/Max 10/69)
195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 2
196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0
197 Current_Pending_Sector 0x0012 252 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always - 1
201 Soft_Read_Error_Rate 0x0032 252 252 000 Old_age Always - 0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error

1 Short offline Completed without error 00% 8569 -

2 Short offline Completed without error 00% 3493 -

SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Completed [00% left] (0-65535)
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

[root@localhost ~]#
[/code]

#72

non ci credo, come detto prima, ho aggiornato il sistema, compreso l’ultimo kernel, al riavvio normale si ripresenta il blocco che fino adesso ha dato problemi.

Alla luce dei fatti, e’ da tutto quello che sta succedendo, prenderei in considerazione di fare un paio di operazioni, un backup in una chiavetta esterna, formattare completamente tutto l’hard disk, e reinstallare ex novo fedora.

Poi vedremo come si comporta, in caso, sostituisco l’hard disk con uno nuovo.

In effetti, nel tempo, ho fatto parecchi pasticci…

grazie di nuovo per la pazienza.

#73

smartctl non ha evidenziato errori:

[quote=lucah74]

[code]
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error

1 Short offline Completed without error 00% 8569 -

2 Short offline Completed without error 00% 3493 -

[root@localhost ~]#
[/code][/quote]

Va detto però che è stato eseguito il diagnostico rapido, quindi è probabile che un eventuale test approfondito evidenzi qualcosa.

#74

ciao, scusami per la risposta tardiva, sono stato parecchio impegnato gli ultimi tempi.
dall’ultimo post mio, avevo reinstallato fedora, ad oggi forse l’ho utilizzato 3 volte, con operazioni molto sbrigative, e quelle volte in cui abbia usato il pc, non ho più avuto problemi nell’accensione.

in ogni caso, sono pronto ad approfondire il test che mi hai proposto.

#75

Il test approfondito richiede più tempo, ma credo ne valga la pena.

Dalla live:

# smartctl -t long /dev/sda

Il comando lancerà il processo diagnostico in background, che questa volta durerà all’incirca 103 minuti. Presta attenzione all’output restituito alla partenza, che indicherà l’orario in cui i risultati potranno essere visualizzati.

Controlla periodicamente l’orologio con il seguente:

$ date

Non appena superi l’orario evidenziato da smartctl (prudenzialmente lascia passare qualche minuto in più), posta questo:

# smartctl -a /dev/sda
#76

certo che un periodo cosi’…mia moglie mi ha rotto inavertitamente la chiavetta dove avevo la live…negozio…ed eccomi qui…

[code][liveuser@localhost ~]$ su -
Last login: Thu Mar 24 03:28:03 EDT 2016 on pts/0
[root@localhost ~]# smartctl -a /dev/sda
smartctl 6.4 2015-06-04 r4109 [i686-linux-4.2.3-300.fc23.i686] (local build)
Copyright © 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: SAMSUNG SpinPoint M6
Device Model: SAMSUNG HM251JI
Serial Number: S1BVJDNS510589
LU WWN Device Id: 5 0f0000 0e3510589
Firmware Version: 2SS00_03
User Capacity: 250,059,350,016 bytes [250 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS, ATA/ATAPI-7 T13/1532D revision 0
SATA Version is: SATA 2.5, 3.0 Gb/s
Local Time is: Thu Mar 24 05:17:42 2016 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
See vendor-specific Attribute list for marginal Attributes.

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 103) seconds.
Offline data collection
capabilities: (0x51) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 103) minutes.
SCT capabilities: (0x003f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 100 100 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0007 252 252 025 Pre-fail Always - 2812
4 Start_Stop_Count 0x0032 093 093 000 Old_age Always - 7387
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 2
7 Seek_Error_Rate 0x000f 252 252 051 Pre-fail Always - 0
8 Seek_Time_Performance 0x0025 252 252 015 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 084 084 000 Old_age Always - 8670
10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always - 1
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 881
12 Power_Cycle_Count 0x0032 097 097 000 Old_age Always - 3802
184 End-to-End_Error 0x0033 252 252 070 Pre-fail Always - 0
187 Reported_Uncorrect 0x0032 252 252 000 Old_age Always - 0
188 Command_Timeout 0x0032 252 252 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 041 031 040 Old_age Always In_the_past 59 (Min/Max 10/69)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 3645
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 514
193 Load_Cycle_Count 0x0032 096 096 000 Old_age Always - 41202
194 Temperature_Celsius 0x0022 041 031 000 Old_age Always - 59 (Min/Max 10/69)
195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 2
196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0
197 Current_Pending_Sector 0x0012 252 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always - 1
201 Soft_Read_Error_Rate 0x0032 252 252 000 Old_age Always - 0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error

1 Extended offline Completed without error 00% 8670 -

2 Short offline Completed without error 00% 8569 -

3 Short offline Completed without error 00% 3493 -

SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Completed [00% left] (0-65535)
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

[root@localhost ~]#
[/code]

#77

[quote=lucah74]

[code]

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error

1 Extended offline Completed without error 00% 8670 -

2 Short offline Completed without error 00% 8569 -

3 Short offline Completed without error 00% 3493 -

[/code][/quote]

Il test non riporta problemi rilevanti e si conclude con successo.

#78

grazie per la tua pazienza :slight_smile: