[SOLVED] Help Diagnosing A Desktop

Ztcoracat · 01-12-2014, 01:11 PM

About 3 days ago I booted up my AMD Quad Core desktop and the
DE crashed giving me a message about Compiz no longer being supported
and the option to report a bug. As soon as I moved the mouse
to hover over the launcher the DE went black and everything was
locked up.

After a reboot I had "grub rescue"
So I tried the Ubuntu DVD to see what I could find out.
I saw the msdos partitions and I saw the ext 4 linux and the linux swap
partitions. I also saw an unknown filesystem.

I tried 3 times to install Fedora but the DVD locked up all three times
during the installation just before the bootloader was being installed.

I used the Fedora DVD to delete the Windows XP partitions and the Ubuntu
partitions. I used RIP Linux to delete that unknown filesystem.

The next reboot I had:

Code:

Kernel panic not syncing VFS unable to mount to root fs on unknown block.

At that point obviously all partitions were gone and I knew my HDD
was empty so I proceeded to install CentOS and allowed for the distro
to completly take up the entire disk.
The CentOS installer was right in the middle of the installation and stopped with
this error message:

Code:

an unknown error has occured 
This program has encountered an unknown error
You may report the bug or quit the program.

See next post- (having trouble posting)

metaschima · 01-12-2014, 01:15 PM

Try running memtest86, let it run for at least 1 pass.

Ztcoracat · 01-12-2014, 01:36 PM

I also used a Live Voyager Linux DVD that installation failed as well.
So I used the Voyager DVD to run dmesg,lshw and lspci -vvv

I have also tried the orginal system Recovery Windows XP disk that came with this box
and it's been stuck at 77% for the last 2 hours.
After a restart this morning I had a different error message:

Code:

Windows could not start because of a software problem
Load needed for DLL's for kernel

Code:

bus error)
[  841.700536] ata1.00: status: { DRDY }
[  841.700538] ata1.00: failed command: READ FPDMA QUEUED
[  841.700543] ata1.00: cmd 60/08:08:48:09:01/00:00:12:00:00/40 tag 1 ncq 4096 in
[  841.700544]          res 40/00:08:48:09:01/00:00:12:00:00/40 Emask 0x50 (ATA bus error)
[  841.700546] ata1.00: status: { DRDY }
[  841.700549] ata1: hard resetting link
[  842.192018] ata1: softreset failed (device not ready)
[  842.192024] ata1: applying PMP SRST workaround and retrying
[  842.364025] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  842.430466] ata1.00: configured for UDMA/33
[  842.456025] ata1: EH complete
[  842.474741] ata1.00: exception Emask 0x52 SAct 0x1 SErr 0x280d01 action 0x6 frozen
[  842.474744] ata1.00: irq_stat 0x08000000, interface fatal error
[  842.474747] ata1: SError: { RecovData UnrecovData Proto HostInt 10B8B BadCRC }
[  842.474751] ata1.00: failed command: READ FPDMA QUEUED
[  842.474756] ata1.00: cmd 60/08:00:48:09:01/00:00:12:00:00/40 tag 0 ncq 4096 in
[  842.474757]          res 40/00:08:00:cc:12/00:00:00:00:00/40 Emask 0x52 (ATA bus error)
[  842.474759] ata1.00: status: { DRDY }
[  842.474763] ata1: hard resetting link
[  842.964019] ata1: softreset failed (device not ready)
[  842.964023] ata1: applying PMP SRST workaround and retrying
[  843.136027] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  843.202422] ata1.00: configured for UDMA/33
[  843.228022] ata1: EH complete
[  843.248966] ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x280900 action 0x6 frozen
[  843.248969] ata1.00: irq_stat 0x08000000, interface fatal error
[  843.248971] ata1: SError: { UnrecovData HostInt 10B8B BadCRC }
[  843.248974] ata1.00: failed command: READ FPDMA QUEUED
[  843.248978] ata1.00: cmd 60/08:00:48:09:01/00:00:12:00:00/40 tag 0 ncq 4096 in
[  843.248984]          res 40/00:00:48:09:01/00:00:12:00:00/40 Emask 0x50 (ATA bus error)
[  843.248987] ata1.00: status: { DRDY }
[  843.248989] ata1: hard resetting link
[  843.740022] ata1: softreset failed (device not ready)
[  843.740028] ata1: applying PMP SRST workaround and retrying
[  843.912025] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  843.978463] ata1.00: configured for UDMA/33
[  844.004023] ata1: EH complete
[  844.023190] ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x280900 action 0x6 frozen
[  844.023192] ata1.00: irq_stat 0x08000000, interface fatal error
[  844.023194] ata1: SError: { UnrecovData HostInt 10B8B BadCRC }
[  844.023197] ata1.00: failed command: READ FPDMA QUEUED
[  844.023201] ata1.00: cmd 60/08:00:48:09:01/00:00:12:00:00/40 tag 0 ncq 4096 in
[  844.023202]          res 40/00:00:48:09:01/00:00:12:00:00/40 Emask 0x50 (ATA bus error)
[  844.023204] ata1.00: status: { DRDY }
[  844.023207] ata1: hard resetting link
[  844.512024] ata1: softreset failed (device not ready)
[  844.512028] ata1: applying PMP SRST workaround and retrying
[  844.684020] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  844.750425] ata1.00: configured for UDMA/33
[  844.776021] ata1: EH complete
[  844.797412] ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x280901 action 0x6 frozen
[  844.797415] ata1.00: irq_stat 0x08000000, interface fatal error
[  844.797417] ata1: SError: { RecovData UnrecovData HostInt 10B8B BadCRC }
[  844.797420] ata1.00: failed command: READ FPDMA QUEUED
[  844.797424] ata1.00: cmd 60/08:00:48:09:01/00:00:12:00:00/40 tag 0 ncq 4096 in
[  844.797425]          res 40/00:00:48:09:01/00:00:12:00:00/40 Emask 0x50 (ATA bus error)
[  844.797428] ata1.00: status: { DRDY }
[  844.797430] ata1: hard resetting link
[  845.288022] ata1: softreset failed (device not ready)
[  845.288029] ata1: applying PMP SRST workaround and retrying
[  845.460031] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  845.530980] ata1.00: configured for UDMA/33
[  845.556023] ata1: EH complete
[  845.579040] ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x280901 action 0x6 frozen
[  845.579042] ata1.00: irq_stat 0x08000000, interface fatal error
[  845.579045] ata1: SError: { RecovData UnrecovData HostInt 10B8B BadCRC }
[  845.579047] ata1.00: failed command: READ FPDMA QUEUED
[  845.579052] ata1.00: cmd 60/08:00:48:09:01/00:00:12:00:00/40 tag 0 ncq 4096 in
[  845.579053]          res 40/00:00:48:09:01/00:00:12:00:00/40 Emask 0x50 (ATA bus error)
[  845.579055] ata1.00: status: { DRDY }
[  845.579058] ata1: hard resetting link
[  846.068014] ata1: softreset failed (device not ready)
[  846.068017] ata1: applying PMP SRST workaround and retrying
[  846.240032] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  846.306436] ata1.00: configured for UDMA/33
[  846.332025] sd 0:0:0:0: [sda]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[  846.332028] sd 0:0:0:0: [sda]  Sense Key : Aborted Command [current] [descriptor]
[  846.332032] Descriptor sense data with sense descriptors (in hex):
[  846.332034]         72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[  846.332040]         12 01 09 48
[  846.332043] sd 0:0:0:0: [sda]  Add. Sense: No additional sense information
[  846.332046] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 12 01 09 48 00 00 08 00
[  846.332052] end_request: I/O error, dev sda, sector 302057800
[  846.332062] ata1: EH complete
[  846.684070] EXT4-fs (sda1): ext4_da_writepages: jbd2_start: 1024 pages, ino 12063889; err -30
[  847.751804] ata1.00: exception Emask 0x52 SAct 0x1000 SErr 0x280d01 action 0x6 frozen
[  847.751808] ata1.00: irq_stat 0x08000000, interface fatal error
[  847.751812] ata1: SError: { RecovData UnrecovData Proto HostInt 10B8B BadCRC }
[  847.751816] ata1.00: failed command: READ FPDMA QUEUED
[  847.751821] ata1.00: cmd 60/08:60:c0:0e:81/00:00:14:00:00/40 tag 12 ncq 4096 in
[  847.751823]          res 40/00:60:c0:0e:81/00:00:14:00:00/40 Emask 0x52 (ATA bus error)
[  847.751825] ata1.00: status: { DRDY }
[  847.751830] ata1: hard resetting link
[  848.240013] ata1: softreset failed (device not ready)
[  848.240016] ata1: applying PMP SRST workaround and retrying
[  848.412033] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  848.478473] ata1.00: configured for UDMA/33
[  848.504024] ata1: EH complete
[  848.526010] ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x280900 action 0x6 frozen
[  848.526013] ata1.00: irq_stat 0x08000000, interface fatal error
[  848.526015] ata1: SError: { UnrecovData HostInt 10B8B BadCRC }
[  848.526018] ata1.00: failed command: READ FPDMA QUEUED
[  848.526022] ata1.00: cmd 60/08:00:c0:0e:81/00:00:14:00:00/40 tag 0 ncq 4096 in
[  848.526023]          res 40/00:00:c0:0e:81/00:00:14:00:00/40 Emask 0x50 (ATA bus error)
[  848.526026] ata1.00: status: { DRDY }
[  848.526028] ata1: hard resetting link
[  849.016015] ata1: softreset failed (device not ready)
[  849.016020] ata1: applying PMP SRST workaround and retrying
[  849.188024] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  849.254437] ata1.00: configured for UDMA/33
[  849.280021] ata1: EH complete
[ 1380.210932] journal commit I/O error
[ 1382.530895] ata1.00: exception Emask 0x52 SAct 0x3f SErr 0x280d01 action 0x6 frozen
[ 1382.530900] ata1.00: irq_stat 0x08000000, interface fatal error
[ 1382.530904] ata1: SError: { RecovData UnrecovData Proto HostInt 10B8B BadCRC }
[ 1382.530908] ata1.00: failed command: READ FPDMA QUEUED
[ 1382.530913] ata1.00: cmd 60/08:00:08:70:c0/00:00:39:00:00/40 tag 0 ncq 4096 in
[ 1382.530914]          res 40/00:28:38:70:c0/00:00:39:00:00/40 Emask 0x52 (ATA bus error)
[ 1382.530916] ata1.00: status: { DRDY }
[ 1382.530918] ata1.00: failed command: READ FPDMA QUEUED
[ 1382.530923] ata1.00: cmd 60/08:08:18:70:c0/00:00:39:00:00/40 tag 1 ncq 4096 in
[ 1382.530924]          res 40/00:28:38:70:c0/00:00:39:00:00/40 Emask 0x52 (ATA bus error)
[ 1382.530926] ata1.00: status: { DRDY }
[ 1382.530928] ata1.00: failed command: READ FPDMA QUEUED
[ 1382.530932] ata1.00: cmd 60/08:10:20:70:c0/00:00:39:00:00/40 tag 2 ncq 4096 in
[ 1382.530933]          res 40/00:28:38:70:c0/00:00:39:00:00/40 Emask 0x52 (ATA bus error)
[ 1382.530935] ata1.00: status: { DRDY }
[ 1382.530937] ata1.00: failed command: READ FPDMA QUEUED
[ 1382.530941] ata1.00: cmd 60/08:18:28:70:c0/00:00:39:00:00/40 tag 3 ncq 4096 in
[ 1382.530942]          res 40/00:28:38:70:c0/00:00:39:00:00/40 Emask 0x52 (ATA bus error)
[ 1382.530944] ata1.00: status: { DRDY }
[ 1382.530946] ata1.00: failed command: READ FPDMA QUEUED
[ 1382.530950] ata1.00: cmd 60/08:20:30:70:c0/00:00:39:00:00/40 tag 4 ncq 4096 in
[ 1382.530951]          res 40/00:28:38:70:c0/00:00:39:00:00/40 Emask 0x52 (ATA bus error)
[ 1382.530959] ata1.00: status: { DRDY }
[ 1382.530961] ata1.00: failed command: READ FPDMA QUEUED
[ 1382.530965] ata1.00: cmd 60/08:28:38:70:c0/00:00:39:00:00/40 tag 5 ncq 4096 in
[ 1382.530966]          res 40/00:28:38:70:c0/00:00:39:00:00/40 Emask 0x52 (ATA bus error)
[ 1382.530968] ata1.00: status: { DRDY }
[ 1382.530972] ata1: hard resetting link
[ 1383.020022] ata1: softreset failed (device not ready)
[ 1383.020027] ata1: applying PMP SRST workaround and retrying
[ 1383.192038] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 1383.258461] ata1.00: configured for UDMA/33
[ 1383.284032] ata1: EH complete
[ 1383.298384] ata1.00: exception Emask 0x50 SAct 0x16 SErr 0x280900 action 0x6 frozen
[ 1383.298388] ata1.00: irq_stat 0x08000000, interface fatal error
[ 1383.298392] ata1: SError: { UnrecovData HostInt 10B8B BadCRC }
[ 1383.298395] ata1.00: failed command: READ FPDMA QUEUED
[ 1383.298401] ata1.00: cmd 60/08:08:30:70:c0/00:00:39:00:00/40 tag 1 ncq 4096 in
[ 1383.298402]          res 40/00:28:08:70:c0/00:00:39:00:00/40 Emask 0x50 (ATA bus error)
[ 1383.298404] ata1.00: status: { DRDY }
[ 1383.298406] ata1.00: failed command: READ FPDMA QUEUED
[ 1383.298410] ata1.00: cmd 60/08:10:28:70:c0/00:00:39:00:00/40 tag 2 ncq 4096 in
[ 1383.298411]          res 40/00:28:08:70:c0/00:00:39:00:00/40 Emask 0x50 (ATA bus error)
[ 1383.298414] ata1.00: status: { DRDY }
[ 1383.298415] ata1.00: failed command: READ FPDMA QUEUED
[ 1383.298420] ata1.00: cmd 60/08:20:18:70:c0/00:00:39:00:00/40 tag 4 ncq 4096 in
[ 1383.298420]          res 40/00:28:08:70:c0/00:00:39:00:00/40 Emask 0x50 (ATA bus error)
[ 1383.298423] ata1.00: status: { DRDY }
[ 1383.298427] ata1: hard resetting link
[ 1383.788016] ata1: softreset failed (device not ready)
[ 1383.788021] ata1: applying PMP SRST workaround and retrying
[ 1383.960027] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 1384.026430] ata1.00: configured for UDMA/33
[ 1384.052020] ata1: EH complete
[ 1384.064303] ata1.00: exception Emask 0x50 SAct 0x6 SErr 0x280900 action 0x6 frozen
[ 1384.064306] ata1.00: irq_stat 0x08000000, interface fatal error
[ 1384.064310] ata1: SError: { UnrecovData HostInt 10B8B BadCRC }
[ 1384.064313] ata1.00: failed command: READ FPDMA QUEUED
[ 1384.064318] ata1.00: cmd 60/08:08:28:70:c0/00:00:39:00:00/40 tag 1 ncq 4096 in
[ 1384.064319]          res 40/00:10:30:70:c0/00:00:39:00:00/40 Emask 0x50 (ATA bus error)
[ 1384.064322] ata1.00: status: { DRDY }
[ 1384.064324] ata1.00: failed command: READ FPDMA QUEUED
[ 1384.064328] ata1.00: cmd 60/08:10:30:70:c0/00:00:39:00:00/40 tag 2 ncq 4096 in
[ 1384.064329]          res 40/00:10:30:70:c0/00:00:39:00:00/40 Emask 0x50 (ATA bus error)
[ 1384.064331] ata1.00: status: { DRDY }
[ 1384.064336] ata1: hard resetting link
[ 1384.560031] ata1: softreset failed (device not ready)
[ 1384.560036] ata1: applying PMP SRST workaround and retrying
[ 1384.732051] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 1384.798469] ata1.00: configured for UDMA/33
[ 1384.824041] ata1: EH complete
[ 1396.148018] journal commit I/O error

[ 1396.148057] journal commit I/O error
[ 1396.148060] journal commit I/O error
[ 1396.148062] journal commit I/O error
[ 1396.148064] journal commit I/O error
[ 1396.163753] journal commit I/O error
[ 1396.163755] journal commit I/O error
[ 1396.163757] journal commit I/O error
[ 1396.163759] journal commit I/O error
[ 1396.163761] journal commit I/O error
[ 1396.163784] journal commit I/O error
[ 1396.163787] journal commit I/O error
[ 1396.163789] journal commit I/O error
[ 1396.163791] journal commit I/O error
[ 1396.163793] journal commit I/O error
[ 1396.163794] journal commit I/O error
[ 1396.163797] journal commit I/O error
[ 1396.163798] journal commit I/O error
[ 1396.163800] journal commit I/O error
[ 1396.163802] journal commit I/O error
[ 1396.163804] journal commit I/O error
[ 1396.163806] journal commit I/O error
[ 1396.163808] journal commit I/O error
[ 1497.846001] journal commit I/O error
[ 1497.846002] journal commit I/O error
[ 1497.846004] journal commit I/O error
[ 1497.846006] journal commit I/O error
[ 1840.201061] journal commit I/O error
[ 1840.201063] journal commit I/O error
[ 1840.201065] journal commit I/O error
[ 1840.201067] journal commit I/O error
[ 1840.201069] journal commit I/O error
[ 1840.201070] journal commit I/O error
[ 1840.201072] journal commit I/O error
[ 1840.201074] journal commit I/O error
[ 1840.201076] journal commit I/O error
[ 1840.201078] journal commit I/O error
[ 1840.201081] journal commit I/O error

└─>



_________________________________________________________________-




LSHW


┌─( xubuntu ) - ( 3.2.0-23-generic ) - ( ~ )
└─> sudo lshw
xubuntu                  
    description: Desktop Computer
    product: MS-7501 (To Be Filled By O.E.M.)
    vendor: MICRO-STAR INTERNATIONAL CO.,LTD
    version: 1.0
    serial: To Be Filled By O.E.M.
    width: 64 bits
    capabilities: smbios-2.5 dmi-2.5 vsyscall32
    configuration: chassis=desktop family=To Be Filled By O.E.M. sku=To Be Filled By O.E.M. uuid=00000000-0000-0000-0000-002185667AD1
  *-core
       description: Motherboard
       product: MS-7501
       vendor: MICRO-STAR INTERNATIONAL CO.,LTD
       physical id: 0
       version: 1.0
       serial: To be filled by O.E.M.
       slot: To Be Filled By O.E.M.
     *-firmware
          description: BIOS
          vendor: American Megatrends Inc.
          physical id: 0
          version: V1.6B4
          date: 01/19/2009
          size: 64KiB
          capacity: 960KiB
          capabilities: isa pci pnp apm upgrade shadowing escd cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer int10video acpi usb ls120boot zipboot biosbootspecification
     *-cpu
          description: CPU
          product: AMD Phenom(tm) 9850 Quad-Core Processor
          vendor: Hynix Semiconductor (Hyundai Electronics)
          physical id: 4
          bus info: cpu@0
          version: AMD Phenom(tm) 9850 Quad-Core Processor
          serial: To Be Filled By O.E.M.
          slot: CPU 1
          size: 2500MHz
          capacity: 2500MHz
          width: 64 bits
          clock: 200MHz
          capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs npt lbrv svm_lock cpufreq
          configuration: cores=4 enabledcores=4
        *-cache:0
             description: L1 cache
             physical id: 5
             slot: L1-Cache
             size: 512KiB
             capacity: 512KiB
             capabilities: pipeline-burst internal varies data
        *-cache:1
             description: L2 cache
             physical id: 6
             slot: L2-Cache
             size: 2MiB
             capacity: 2MiB
             capabilities: pipeline-burst internal varies unified
        *-cache:2
             description: L3 cache
             physical id: 7
             slot: L3-Cache
             size: 2MiB
             capacity: 2MiB
             capabilities: pipeline-burst internal varies unified
     *-memory
          description: System Memory
          physical id: 29
          slot: System board or motherboard
          size: 4GiB
        *-bank:0
             description: DIMM DDR2 Synchronous 400 MHz (2.5 ns)
             product: PartNum0
             vendor: Manufacturer0
             physical id: 0
             serial: SerNum0
             slot: DIMM0
             size: 2GiB
             width: 64 bits
             clock: 400MHz (2.5ns)
        *-bank:1
             description: DIMM DDR2 Synchronous 400 MHz (2.5 ns)
             product: PartNum1
             vendor: Manufacturer1
             physical id: 1
             serial: SerNum1
             slot: DIMM1
             size: 2GiB
             width: 64 bits
             clock: 400MHz (2.5ns)
        *-bank:2
             description: DIMM SDRAM [empty]
             product: PartNum2
             vendor: Manufacturer2
             physical id: 2
             serial: SerNum2
             slot: DIMM2
        *-bank:3
             description: DIMM SDRAM [empty]
             product: PartNum3
             vendor: Manufacturer3
             physical id: 3
             serial: SerNum3
             slot: DIMM3
     *-pci:0
          description: Host bridge
          product: RS780 Host Bridge
          vendor: Hynix Semiconductor (Hyundai Electronics)
          physical id: 100
          bus info: pci@0000:00:00.0
          version: 00
          width: 32 bits
          clock: 66MHz
        *-pci:0
             description: PCI bridge
             product: RS780/RS880 PCI to PCI bridge (int gfx)
             vendor: Hynix Semiconductor (Hyundai Electronics)
             physical id: 1
             bus info: pci@0000:00:01.0
             version: 00
             width: 32 bits
             clock: 66MHz
             capabilities: pci ht normal_decode bus_master cap_list
             resources: ioport:c000(size=4096) memory:fe800000-fe9fffff ioport:d0000000(size=268435456)
           *-display
                description: VGA compatible controller
                product: RS780C [Radeon HD 3100]
                vendor: Hynix Semiconductor (Hyundai Electronics)
                physical id: 5
                bus info: pci@0000:01:05.0
                version: 00
                width: 32 bits
                clock: 33MHz
                capabilities: pm msi vga_controller bus_master cap_list rom
                configuration: driver=radeon latency=0
                resources: irq:18 memory:d0000000-dfffffff ioport:c000(size=256) memory:fe9f0000-fe9fffff memory:fe800000-fe8fffff
        *-pci:1
             description: PCI bridge
             product: RS780/RS880 PCI to PCI bridge (PCIE port 0)
             vendor: Hynix Semiconductor (Hyundai Electronics)
             physical id: 4
             bus info: pci@0000:00:04.0
             version: 00
             width: 32 bits
             clock: 33MHz
             capabilities: pci pm pciexpress msi ht normal_decode bus_master cap_list
             configuration: driver=pcieport
             resources: irq:40 ioport:d000(size=4096) memory:fea00000-feafffff
           *-network
                description: Wireless interface
                product: RTL8188CE 802.11b/g/n WiFi Adapter
                vendor: Realtek Semiconductor Co., Ltd.
                physical id: 0
                bus info: pci@0000:02:00.0
                logical name: wlan0
                version: 01
                serial: 08:10:76:6c:68:61
                width: 64 bits
                clock: 33MHz
                capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
                configuration: broadcast=yes driver=rtl8192ce driverversion=3.2.0-23-generic firmware=N/A ip=192.168.1.3 latency=0 link=yes multicast=yes wireless=IEEE 802.11bgn
                resources: irq:16 ioport:d800(size=256) memory:feafc000-feafffff
        *-pci:2
             description: PCI bridge
             product: RS780/RS880 PCI to PCI bridge (PCIE port 1)
             vendor: Hynix Semiconductor (Hyundai Electronics)
             physical id: 5
             bus info: pci@0000:00:05.0
             version: 00
             width: 32 bits
             clock: 33MHz
             capabilities: pci pm pciexpress msi ht normal_decode bus_master cap_list
             configuration: driver=pcieport
             resources: irq:41 ioport:e000(size=4096) memory:feb00000-febfffff ioport:fdf00000(size=1048576)
           *-network
                description: Ethernet interface
                product: RTL8111/8168B PCI Express Gigabit Ethernet controller
                vendor: Realtek Semiconductor Co., Ltd.
                physical id: 0
                bus info: pci@0000:03:00.0
                logical name: eth0
                version: 02
                serial: 00:21:85:66:7a:d1
                size: 10Mbit/s
                capacity: 1Gbit/s
                width: 64 bits
                clock: 33MHz
                capabilities: pm msi pciexpress msix vpd bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
                configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=N/A latency=0 link=no multicast=yes port=MII speed=10Mbit/s
                resources: irq:42 ioport:e800(size=256) memory:fdfff000-fdffffff memory:fdfe0000-fdfeffff memory:febf0000-febfffff
        *-storage
             description: SATA controller
             product: SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode]
             vendor: Hynix Semiconductor (Hyundai Electronics)
             physical id: 11
             bus info: pci@0000:00:11.0
             logical name: scsi0
             version: 00
             width: 32 bits
             clock: 66MHz
             capabilities: storage pm ahci_1.0 bus_master cap_list emulated
             configuration: driver=ahci latency=64
             resources: irq:22 ioport:b000(size=8) ioport:a000(size=4) ioport:9000(size=8) ioport:8000(size=4) ioport:7000(size=16) memory:fe7ff800-fe7ffbff
           *-disk
                description: ATA Disk
                product: ST3500410AS
                vendor: Seagate
                physical id: 0.0.0
                bus info: scsi@0:0.0.0
                logical name: /dev/sda
                version: CC34
                serial: 6VM0607J
                size: 465GiB (500GB)
                capabilities: partitioned partitioned:dos
                configuration: ansiversion=5 signature=00029eda
              *-volume:0
                   description: EXT4 volume
                   vendor: Linux
                   physical id: 1
                   bus info: scsi@0:0.0.0,1
                   logical name: /dev/sda1
                   logical name: /target
                   version: 1.0
                   serial: 2e69f251-c36b-4562-abf1-5cd1ada3fa3a
                   size: 462GiB
                   capacity: 462GiB
                   capabilities: primary journaled extended_attributes large_files huge_files dir_nlink recover extents ext4 ext2 initialized
                   configuration: created=2014-01-11 05:03:36 filesystem=ext4 lastmountpoint=/target modified=2014-01-11 05:10:38 mount.fstype=ext4 mount.options=ro,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered mounted=2014-01-11 05:03:40 state=mounted
              *-volume:1
                   description: Extended partition
                   physical id: 2
                   bus info: scsi@0:0.0.0,2
                   logical name: /dev/sda2
                   size: 3837MiB
                   capacity: 3837MiB
                   capabilities: primary extended partitioned partitioned:extended
                 *-logicalvolume
                      description: Linux swap / Solaris partition
                      physical id: 5
                      logical name: /dev/sda5
                      capacity: 3837MiB
                      capabilities: nofs
        *-usb:0
             description: USB controller
             product: SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
             vendor: Hynix Semiconductor (Hyundai Electronics)
             physical id: 12
             bus info: pci@0000:00:12.0
             version: 00
             width: 32 bits
             clock: 66MHz
             capabilities: ohci bus_master
             configuration: driver=ohci_hcd latency=64
             resources: irq:16 memory:fe7fe000-fe7fefff
        *-usb:1
             description: USB controller
             product: SB7x0 USB OHCI1 Controller
             vendor: Hynix Semiconductor (Hyundai Electronics)
             physical id: 12.1
             bus info: pci@0000:00:12.1
             version: 00
             width: 32 bits
             clock: 66MHz
             capabilities: ohci bus_master
             configuration: driver=ohci_hcd latency=64
             resources: irq:16 memory:fe7fd000-fe7fdfff
        *-usb:2
             description: USB controller
             product: SB7x0/SB8x0/SB9x0 USB EHCI Controller
             vendor: Hynix Semiconductor (Hyundai Electronics)
             physical id: 12.2
             bus info: pci@0000:00:12.2
             version: 00
             width: 32 bits
             clock: 66MHz
             capabilities: pm debug ehci bus_master cap_list
             configuration: driver=ehci_hcd latency=64
             resources: irq:17 memory:fe7ff000-fe7ff0ff
  
└─>

	
Click here to Reply or Forward
0.06 GB (0%) of 15 GB used
Manage
©2014 Google - Terms & Privacy
Last account activity: 12 hours ago
Details

ukiuki · 01-12-2014, 01:36 PM

It maybe a problem with the installation disk, how about run the installation from a pendrive just to avoid lost of CDs?
Also would be better to wipe the HDD with dd just to make sure absolutely nothing is there before install the system.

I was writing while you also was writing the second post and I didn't see it until now;

So now it is clear that your cd drive have a physical problem and is not able to read all the data on the disks. So go with a bootable pendrive with the installation files or ISO to be able to intall the desired system.

Regards

Ztcoracat · 01-12-2014, 01:37 PM

Quote:

Originally Posted by metaschima

Try running memtest86, let it run for at least 1 pass.

I'll try that and see what happens-
Be back

Ztcoracat · 01-12-2014, 01:52 PM

Quote:

Originally Posted by ukiuki

It maybe a problem with the installation disk, how about run the installation from a pendrive just to avoid lost of CDs?
Also would be better to wipe the HDD with dd just to make sure absolutely nothing is there before install the system.

I was writing while you also was writing the second post and I didn't see it until now;

So now it is clear that your cd drive have a physical problem and is not able to read all the data on the disks. So go with a bootable pendrive with the installation files or ISO to be able to intall the desired system.

Regards

You mean it's the DVD-ROM that is having the problem?
Can you show me in code tags? Please, where this is spelled out so I will know for the future.

metaschima · 01-12-2014, 01:54 PM

From the errors you just posted, I'm leaning towards HDD failure. I'm guessing you already backed up your data, as you just wiped the disk.

Try booting either:
http://www.sysresccd.org/SystemRescueCd_Homepage
and run a SMART long test 'smartctl -t long /dev/sda'
or boot:
http://www.ultimatebootcd.com/
and run the manufacturers HDD SMART long test.

If they fail, then it is the HDD that is bad.

ukiuki · 01-12-2014, 03:03 PM

Quote:

Originally Posted by Ztcoracat

You mean it's the DVD-ROM that is having the problem?...

I also used a Live Voyager Linux DVD that installation failed as well.
So I used the Voyager DVD to run dmesg...

Yes it is the cd drive.(it is dieing)
It is all over the code you posted, all those errors with ata1, that is the cd drive reading the disk,

Code:

ata1.00: failed command: READ FPDMA QUEUED
ata1.00: exception Emask 0x52 SAct 0x1 SErr 0x280d01 action 0x6 frozen
ata1.00: irq_stat 0x08000000, interface fatal error

This goes on and on in your log, it isn't rare to a cd drive goes bad and present that kind of output while reading the disk to install or running a live CD. It is strongly recommended in this case to use a pendrive for live sessions and to install systems.

On a second though also check your hard drive.
To find out out about the hard drive, from a live cd, if your cd drive manage to run it, run the gnome-disk-utility/palimpsest.

Regards

Ztcoracat · 01-12-2014, 03:28 PM

Quote:

Originally Posted by metaschima

From the errors you just posted, I'm leaning towards HDD failure. I'm guessing you already backed up your data, as you just wiped the disk.

Try booting either:
http://www.sysresccd.org/SystemRescueCd_Homepage
and run a SMART long test 'smartctl -t long /dev/sda'
or boot:
http://www.ultimatebootcd.com/
and run the manufacturers HDD SMART long test.

If they fail, then it is the HDD that is bad.

Code:

systemrescuecd-x-86-3.8.1.iso

Is now burned to a CD-
Thanks!

I'll run the rescue CD in a few min's and see what happens.
I wonder is there are bad sectors?

Ztcoracat · 01-12-2014, 03:32 PM

Quote:

Originally Posted by ukiuki

Yes it is the cd drive.(it is dieing)
It is all over the code you posted, all those errors with ata1, that is the cd drive reading the disk,

Code:

ata1.00: failed command: READ FPDMA QUEUED
ata1.00: exception Emask 0x52 SAct 0x1 SErr 0x280d01 action 0x6 frozen
ata1.00: irq_stat 0x08000000, interface fatal error

This goes on and on in your log, it isn't rare to a cd drive goes bad and present that kind of output while reading the disk to install or running a live CD. It is strongly recommended in this case to use a pendrive for live sessions and to install systems.

On a second though also check your hard drive.
To find out out about the hard drive, from a live cd, if your cd drive manage to run it, run the gnome-disk-utility/palimpsest.

Regards

Thank You for finding the exact message to show me that.

Is there another application (besides the rescue cd) that I could use to dx bad sectors?

Ztcoracat · 01-13-2014, 12:16 PM

I have been running DRevitalize v1.2 for the last 33 hours.
Sectors according to this program are bad and all but 2 so far have been recovered.

Code:

Hardisk 1 (476940 MB in 976773168 sectors)

Bad sectors found: 6848
Bad sectors recovered: 6846

This program has only made it about 1/2 way through to completion filling a white bar with blue "R's"
The "B's" that are in red are the sectors that were not able to be recovered.

Waiting at this point to see how the rest of recovery goes.

metaschima · 01-13-2014, 12:24 PM

It is clear that the HDD is bad, and you should get a new one. Bad sectors are a sign that the HDD is close to death.

Ztcoracat · 01-13-2014, 12:46 PM

Quote:

Originally Posted by metaschima

It is clear that the HDD is bad, and you should get a new one. Bad sectors are a sign that the HDD is close to death.

I found some information that is of the contrary.
Would you be willing to read the article and and make another synopsis?

metaschima · 01-13-2014, 01:22 PM

Well, here are some arguments for bad sectors = drive will fail soon:

1) SMART attributes exist for Reallocated_Sector_Ct, Runtime_Bad_Block, UDMA_CRC_Error_Count, Offline_Uncorrectable.
2) Here are some links to look through:
http://consultancomputeraplus.blogsp...ctor-part.html
http://www.techsupportforum.com/foru...or-630946.html
http://superuser.com/questions/40461...-how-to-repair
http://superuser.com/questions/40461...-how-to-repair
3) Programs that claim to "repair" bad blocks are lying and should probably be sued for false advertising. The programs mark the bad blocks so that they are not used. They does not constitute a "repair", but rather a face-saving measure, delaying the inevitable and covering up the progressive rotting of the disk.
4) Experience is a though teacher. It gives the test first, and the lesson afterwards. You can always count on it. So, if you don't believe it, then at least keep a backup of your important data, that way when it fails you won't lose much.

EDIT:
Personally, with HDDs, I err on the side of caution. I replace HDDs when I see SMART attributes getting close to 0. Say if they get to around 10, I replace the drive. I most certainly don't wait for symptoms such as bad blocks. If a SMART long test sees any bad blocks, I consider the HDD failed and replace it right away. Why ? Because I value my data over some cheap HDD. I make regular backups as well, but not daily.

Ztcoracat · 01-13-2014, 02:32 PM

I agree; metaschima:

There is false advertising out there and I can only imagine how overloaded the Federal Communications Commission is with that.

I discovered a article and it should at least be considered at least in part for one that is on a strict budget.

If I have to purchase a brand new HDD it will become evident:-
Exhausting a zero fill can't hurt. If anything I have saved on gasoline and have avoided a afernoon of sitting in bumper to bumper traffic.

A friend of mine used the sector recovery application on an old 1995 Toshiba laptop hard drive and ran a zero fill for 2 days straight. That drive now operates his new computer I recently helped him build.

The OS may have tried to read data on the HDD from a sector and found ECC (error correct code) didn't match the sector that means something is wrong.
Bad sectors are found but can be repaired by overwritting the HDD with zero's. (zero fill)

http://www.howtogeek.com/173463/bad-...n-do-about-it/