troppo tempo per il boot...

[yashi79]

leggendo dal mio syslog noto che :

3:18:15 somarello kernel: [    4.024292] scsi 4:0:0:0: CD-ROM            TSSTcorp CDDVDW SH-S223C  SB03 PQ: 0 ANSI: 5
Jun  3 13:18:15 somarello kernel: [    4.027569] sr0: scsi3-mmc drive: 52x/52x writer dvd-ram cd/rw xa/form2 cdda tray
Jun  3 13:18:15 somarello kernel: [    4.027573] cdrom: Uniform CD-ROM driver Revision: 3.20
Jun  3 13:18:15 somarello kernel: [    4.027703] sr 4:0:0:0: Attached scsi CD-ROM sr0
Jun  3 13:18:15 somarello kernel: [    4.027771] sr 4:0:0:0: Attached scsi generic sg1 type 5
Jun  3 13:18:15 somarello kernel: [   34.960058] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Jun  3 13:18:15 somarello kernel: [   34.960062] ata5.00: failed command: IDENTIFY PACKET DEVICE
Jun  3 13:18:15 somarello kernel: [   34.960066] ata5.00: cmd a1/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
Jun  3 13:18:15 somarello kernel: [   34.960067]          res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Jun  3 13:18:15 somarello kernel: [   34.960069] ata5.00: status: { DRDY }
Jun  3 13:18:15 somarello kernel: [   34.960073] ata5: hard resetting link
Jun  3 13:18:15 somarello kernel: [   35.510058] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Jun  3 13:18:15 somarello kernel: [   36.112251] ata5.00: configured for UDMA/100
Jun  3 13:18:15 somarello kernel: [   36.713095] ata5: EH complete
Jun  3 13:18:15 somarello kernel: [   66.960051] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Jun  3 13:18:15 somarello kernel: [   66.960054] ata5.00: failed command: IDENTIFY PACKET DEVICE
Jun  3 13:18:15 somarello kernel: [   66.960059] ata5.00: cmd a1/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
Jun  3 13:18:15 somarello kernel: [   66.960059]          res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Jun  3 13:18:15 somarello kernel: [   66.960061] ata5.00: status: { DRDY }
Jun  3 13:18:15 somarello kernel: [   66.960065] ata5: hard resetting link
Jun  3 13:18:15 somarello kernel: [   67.510054] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Jun  3 13:18:15 somarello kernel: [   68.112326] ata5.00: configured for UDMA/100
Jun  3 13:18:15 somarello kernel: [   68.713056] ata5: EH complete
Jun  3 13:18:15 somarello kernel: [   68.734354] uvesafb: (C) 1988-2005, ATI Technologies Inc. , RS880, 01.00, OEM: ATI ATOMBIOS, VBE v3.0
Jun  3 13:18:15 somarello kernel: [   68.764363] uvesafb: VBIOS/hardware supports DDC2 transfers
Jun  3 13:18:15 somarello kernel: [   68.936455] uvesafb: monitor limits: vf = 75 Hz, hf = 81 kHz, clk = 170 MHz
Jun  3 13:18:15 somarello kernel: [   68.936570] uvesafb: scrolling: redraw
Jun  3 13:18:15 somarello kernel: [   68.939038] Console: switching to colour frame buffer device 80x30
Jun  3 13:18:15 somarello kernel: [   68.939052] uvesafb: framebuffer at 0xd0000000, mapped to 0xffffc90010980000, using 16384k, total 16384k
Jun  3 13:18:15 somarello kernel: [   68.939054] fb0: VESA VGA frame buffer device
Jun  3 13:18:15 somarello kernel: [   69.122301] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
Jun  3 13:18:15 somarello kernel: [   81.933476] <30>udev[399]: starting version 167
Jun  3 13:18:15 somarello kernel: [   81.944078] lp: driver loaded but no devices found
Jun  3 13:18:15 somarello kernel: [   81.948223] w83627ehf: Found W83627DHG-P chip at 0x290

qualcuno mi saprebbe dire come ovviare al problema? Se ne sta andando l'HD?

[Gimli[2BV!2B]]

Sembrerebbe questo bug: Red Hat #684599

Potresti provare quanto consigliato alla decima risposta, ovvero aggiungere l'opzione libata.atapi_passthru16=0 al kernel.

Metodo standard: modificare la variabile GRUB_CMDLINE_LINUX_DEFAULT (in modo da lasciare stare il recovery mode).

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash libata.atapi_passthru16=0"

Una volta salvata la modifica un bel

sudo update-grub

ed per aggiornare il grub.cfg ed un riavvio per testare.

[yashi79]

grazie! sono passata da 2 minuti abbondanti a meno di uno...

[Gimli[2BV!2B]]

Bene
Dovrebbe trattarsi di un problema transitorio relativo ad alcune versioni del kernel/udev, quindi quell'impostazione non dovrebbe essere più necessaria fra qualche mese (tempo che correggano, che la tua distribuzione prenda la correzione/aggiornamento e che arrivi alla tua installazione).