Thank you! Performed the procediementos indicated. It was necessary to recreate the media (RW) with powerful formatting and set the speed.
Em 25 de março de 2012 10:29, Colin Watson <[email protected]> escreveu: > The syslog has this set of errors: > > Mar 24 11:53:01 bt kernel: [ 287.652281] sr 2:0:0:0: [sr0] Unhandled sense > code > Mar 24 11:53:01 bt kernel: [ 287.652303] sr 2:0:0:0: [sr0] Result: > hostbyte=DID_OK driverbyte=DRIVER_SENSE > Mar 24 11:53:01 bt kernel: [ 287.652325] sr 2:0:0:0: [sr0] Sense Key : > Medium Error [current] > Mar 24 11:53:01 bt kernel: [ 287.652354] Info fld=0x0 > Mar 24 11:53:01 bt kernel: [ 287.652366] sr 2:0:0:0: [sr0] Add. Sense: > Unrecovered read error > Mar 24 11:53:01 bt kernel: [ 287.652390] sr 2:0:0:0: [sr0] CDB: Read(10): 28 > 00 00 12 e0 be 00 00 20 00 > Mar 24 11:53:01 bt kernel: [ 287.652444] end_request: I/O error, dev sr0, > sector 4948728 > Mar 24 11:53:08 bt kernel: [ 294.830036] sr 2:0:0:0: [sr0] Unhandled sense > code > Mar 24 11:53:08 bt kernel: [ 294.830055] sr 2:0:0:0: [sr0] Result: > hostbyte=DID_OK driverbyte=DRIVER_SENSE > Mar 24 11:53:08 bt kernel: [ 294.830088] sr 2:0:0:0: [sr0] Sense Key : > Medium Error [current] > Mar 24 11:53:08 bt kernel: [ 294.830112] Info fld=0x0 > Mar 24 11:53:08 bt kernel: [ 294.830123] sr 2:0:0:0: [sr0] Add. Sense: > Unrecovered read error > Mar 24 11:53:08 bt kernel: [ 294.830145] sr 2:0:0:0: [sr0] CDB: Read(10): 28 > 00 00 12 e0 de 00 00 36 00 > Mar 24 11:53:08 bt kernel: [ 294.830199] end_request: I/O error, dev sr0, > sector 4948856 > Mar 24 11:53:15 bt kernel: [ 302.146082] sr 2:0:0:0: [sr0] Unhandled sense > code > Mar 24 11:53:15 bt kernel: [ 302.146102] sr 2:0:0:0: [sr0] Result: > hostbyte=DID_OK driverbyte=DRIVER_SENSE > Mar 24 11:53:15 bt kernel: [ 302.146122] sr 2:0:0:0: [sr0] Sense Key : > Medium Error [current] > Mar 24 11:53:15 bt kernel: [ 302.146145] Info fld=0x0 > Mar 24 11:53:15 bt kernel: [ 302.146156] sr 2:0:0:0: [sr0] Add. Sense: > Unrecovered read error > Mar 24 11:53:15 bt kernel: [ 302.146178] sr 2:0:0:0: [sr0] CDB: Read(10): 28 > 00 00 12 e0 d4 00 00 02 00 > Mar 24 11:53:15 bt kernel: [ 302.146232] end_request: I/O error, dev sr0, > sector 4948816 > Mar 24 11:53:15 bt kernel: [ 302.148009] SQUASHFS error: squashfs_read_data > failed to read block 0x9702da1f > Mar 24 11:53:15 bt kernel: [ 302.149005] SQUASHFS error: Unable to read data > cache entry [9702da1f] > Mar 24 11:53:15 bt kernel: [ 302.149021] SQUASHFS error: Unable to read > page, block 9702da1f, size d5cc > Mar 24 11:53:15 bt kernel: [ 302.152825] SQUASHFS error: Unable to read data > cache entry [9702da1f] > > ... and then it all goes downhill from there. > > This indicates that there's been a problem reading from the CD. This is > generally due to a faulty CD/DVD disk or drive, rather than being an > installer bug as such. It may help to clean the CD/DVD, to burn the > CD/DVD at a lower speed, or to clean the CD/DVD drive lens (cleaning > kits are often available from electronics suppliers). > > ** Tags removed: 135 code erro exit patch > > ** Changed in: ubiquity (Ubuntu) > Status: New => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/963998 > > Title: > erro na instalação (exit code 135) > > Status in “ubiquity” package in Ubuntu: > Invalid > > Bug description: > Na instalação do backtrack 5, no passo 7 está retornando este os erro > conforme os logs abaixo: > > /var/log/syslog: > > > Mar 24 11:53:47 bt ubiquity[2085]: Traceback (most recent call last): > Mar 24 11:53:47 bt ubiquity[2085]: File "/usr/lib/ubiquity/bin/ubiquity", > line 524, in <module> > Mar 24 11:53:47 bt ubiquity[2085]: main(oem_config) > Mar 24 11:53:47 bt ubiquity[2085]: File "/usr/lib/ubiquity/bin/ubiquity", > line 511, in main > Mar 24 11:53:47 bt ubiquity[2085]: install(query=options.query) > Mar 24 11:53:47 bt ubiquity[2085]: File "/usr/lib/ubiquity/bin/ubiquity", > line 242, in install > Mar 24 11:53:47 bt ubiquity[2085]: ret = wizard.run() > Mar 24 11:53:47 bt ubiquity[2085]: File > "/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py", line 513, in run > Mar 24 11:53:47 bt ubiquity[2085]: self.process_step() > Mar 24 11:53:47 bt ubiquity[2085]: File > "/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py", line 1179, in process_step > Mar 24 11:53:47 bt ubiquity[2085]: self.progress_loop() > Mar 24 11:53:47 bt ubiquity[2085]: File > "/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py", line 1065, in progress_loop > Mar 24 11:53:47 bt ubiquity[2085]: "/var/log/syslog" % ret) > Mar 24 11:53:47 bt ubiquity[2085]: RuntimeError: Install failed with exit > code 135; see /var/log/syslog > Mar 24 11:53:47 bt ubiquity[2085]: > Mar 24 11:56:20 bt kernel: [ 487.471051] atkbd serio0: Spurious NAK on > isa0060/serio0. Some program might be trying access hardware directly. > Mar 24 12:02:31 bt kernel: [ 857.534569] atkbd serio0: Spurious NAK on > isa0060/serio0. Some program might be trying access hardware directly. > Mar 24 12:02:48 bt kernel: [ 874.971412] atkbd serio0: Spurious NAK on > isa0060/serio0. Some program might be trying access hardware directly. > Mar 24 12:03:04 bt kernel: [ 890.558652] atkbd serio0: Spurious NAK on > isa0060/serio0. Some program might be trying access hardware directly. > Mar 24 12:03:42 bt kernel: [ 928.557546] atkbd serio0: Spurious NAK on > isa0060/serio0. Some program might be trying access hardware directly. > Mar 24 12:03:48 bt kernel: [ 935.328820] atkbd serio0: Spurious NAK on > isa0060/serio0. Some program might be trying access hardware directly. > Mar 24 12:09:01 bt CRON[5533]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime > ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -depth -mindepth 1 -maxdepth > 1 -type f -cmin +$(/usr/lib/php5/maxlifetime) -delete) > Mar 24 12:10:27 bt kernel: [ 1334.274829] atkbd serio0: Spurious NAK on > isa0060/serio0. Some program might be trying access hardware directly. > Mar 24 12:12:53 bt kernel: [ 1480.329299] atkbd serio0: Spurious NAK on > isa0060/serio0. Some program might be trying access hardware directly. > Mar 24 12:17:01 bt CRON[5570]: (root) CMD ( cd / && run-parts --report > /etc/cron.hourly) > Mar 24 12:18:54 bt kernel: [ 1841.380515] atkbd serio0: Spurious NAK on > isa0060/serio0. Some program might be trying access hardware directly. > Mar 24 12:21:14 bt kernel: [ 1980.753883] atkbd serio0: Spurious NAK on > isa0060/serio0. Some program might be trying access hardware directly. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/963998/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/963998 Title: erro na instalação (exit code 135) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/963998/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
