MBP won't boot due to hard disk problem

I have a late 2008 which just started to have problems booting up.
The trouble started a week ago, when my MBP would shut down unexpectedly while I'm working(on battery power). When I tried to reboot from battery power it didn't work. However, it's not the issue of low battery level. I had plenty juice in the battery. So I attached to the mag safe power supply, it would boot up again.
On yesterday morning after another unexpected shut down, I plugged the mag saft back in and hope it would boot up again. Never again. It will alwasy stuck at the gray screen with a spinning circle. So I did quite a few standard checks such as booting from Snow Leopard install DVD, and run DiskUtility. It tells me my MBP Hard Drive has problems and can not be repaired. So I figure it's the HD problem. Now I just want to salvage some data off from that HD, get a new HD and start over again.
I tried to boot from DiskWarrior 4.2 DVD, it didn't boot up. It boot up fine with Snow Leopard DVD. So the optical drive works fine.
The HD is the Hitachi 7200rpm travelstar 250GB.
Any advice?

I totally agree with making a Super Duper copy of the drive before proceeding with anything else--that creates an exact copy of the problem drive so that everything is preserved. It would also create a duplicate that could be used to experiment with.
One way to do this is to get the replacement drive for the MBP and place it in an enclosure, maybe even using one of OWC's kits. The MBP's drive is already mounted on the Mac Pro's desktop, and the new drive in the enclosure can also be mounted on the MacPro's desktop and properly formatted using Disk Utility. Then Super Duper can be launched and used to copy the MBP's drive to the new drive. Once that's done, the OS could be reinstalled on the new drive and we would be able to see if that cured the password problem. Since Super Duper can make a bootable clone, we could see if the MBP would boot from it by plugging it into a MBP port and trying an option boot. If everything works, you can just install the new drive in the MBP.
Doing something like this does not touch the original MBP drive and its contents, so everything is preserved.
Just about any external drive would work for this purpose--it doesn't necessarily need to be the one that you intend to use as a replacement.
I agree that we don't really know for certain just what the fault is, but I think a Super Duper copy would be in order no matter how we go about doing the troubleshooting.

Similar Messages

System freezes due to hard disk problems only on Linux (not windows)

Intro/context:
Recently i've bought (about 2 months) a new laptop, a Lenovo G50-70, which came with Windows 8.1. As i had no interest on that OS, i formatted the disk and installed only Arch Linux. During that time i experienced system freezes which i had no idea why they were happening. As time went by, i found disk errors on system logs related to hard drive. I searched those errors and almost everything i found was that my hard drive had problems, so i decided to use my warranty. But first, i installed the original OS back again. And after using it a couple of weeks, i didn't experiencie any problem with my hard drive (on Linux it was really frequent). Now i've installed Arch Linux back, along with original Windows 8.1, having dual boot. There is no disk problem when using Windows, but when on Arch, i have the same errors and problems i used to have. So i assume it may be related to kernel or some confniguration issue.
I also haven't noticed any relation between system freezes and system use. I mean, it can happen either under light or heavy use.
tl dr: system freezes randomly for some minutes when using linux due to hard drive problems. The problem doesn't happen on windows.
What i've done so far:
The first period i was on Arch, i run smart (long and short), fsck, and hdparm tests. And nothing (no errors). Searched for bad blocks, and nothing. When back on windows, i also run tests on hdd and found no problems, except some sector reallocation not-that-nice indicators. These problems occured at the end of the first arch installation period. But still i currently experience no problem on windows.
I've also tried setting libata: noncq, 3.0G, noacpi, noapic kernel parameters, and had no result.
Changed BIOS setting from AHCI to Legacy, and no result. Also updated BIOS and no result.
I found no firmware update for this hard drive.
So i don't know what other thing i can try. I want to emphasize that there is no problem, no freezing, when running Windows, so i don't think it's a hard drive issue.
Info:
Hard drive is a Toshiba 2.5" HDD MQ01ABD100 5400 rpm.
Some logs i've recollected all this time:
journalctl -xfa --system
abr 21 13:51:13 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
abr 21 13:51:24 echoes kernel: ata1.00: failed command: CHECK POWER MODE
abr 21 13:51:24 echoes kernel: ata1.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 7
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 21 13:51:24 echoes kernel: ata1.00: status: { DRDY }
abr 21 13:51:24 echoes kernel: ata1: hard resetting link
abr 21 13:51:24 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
abr 21 13:51:24 echoes kernel: ata1.00: configured for UDMA/100
abr 21 13:51:24 echoes kernel: ata1: EH complete
abr 21 14:01:40 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
abr 21 14:02:01 echoes kernel: ata1.00: failed command: SMART
abr 21 14:02:01 echoes kernel: ata1.00: cmd b0/d1:01:00:4f:c2/00:00:00:00:00/00 tag 23 pio 512 in
res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 21 14:02:01 echoes kernel: ata1.00: status: { DRDY }
abr 21 14:02:01 echoes kernel: ata1: hard resetting link
abr 21 14:02:01 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
abr 21 14:02:01 echoes kernel: ata1.00: configured for UDMA/100
abr 21 14:02:01 echoes kernel: ata1: EH complete
abr 21 14:02:01 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
abr 21 14:02:01 echoes kernel: ata1.00: failed command: SMART
abr 21 14:02:01 echoes kernel: ata1.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 22 pio 512 in
res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 21 14:02:01 echoes kernel: ata1.00: status: { DRDY }
abr 21 14:02:01 echoes kernel: ata1: hard resetting link
abr 21 14:02:01 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
abr 21 14:02:01 echoes kernel: ata1.00: configured for UDMA/100
abr 21 14:02:01 echoes kernel: ata1: EH complete
abr 21 14:02:01 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
abr 21 14:02:01 echoes kernel: ata1.00: failed command: SMART
abr 21 14:02:01 echoes kernel: ata1.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 18
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 21 14:02:01 echoes kernel: ata1.00: status: { DRDY }
abr 21 14:02:01 echoes kernel: ata1: hard resetting link
abr 21 14:02:01 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
abr 21 14:02:01 echoes kernel: ata1.00: configured for UDMA/100
abr 21 14:02:01 echoes kernel: ata1: EH complete
abr 21 14:01:51 echoes udisksd[627]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/TOSHIBA_MQ01ABD100_Y44MT611T: Error updating SMART data: sk_disk_smart_status: Input/output error (udisks-error-quark, 0)
dmesg
[55661.023028] ata1.00: exception Emask 0x0 SAct 0x8000 SErr 0x0 action 0x6 frozen
[55661.023034] ata1.00: failed command: READ FPDMA QUEUED
[55661.023040] ata1.00: cmd 60/08:78:18:08:c0/00:00:4b:00:00/40 tag 15 ncq 4096 in
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[55661.023042] ata1.00: status: { DRDY }
[55661.023046] ata1: hard resetting link
[55666.358537] ata1: link is slow to respond, please be patient (ready=0)
[55671.053813] ata1: COMRESET failed (errno=-16)
[55671.053819] ata1: hard resetting link
[55676.389438] ata1: link is slow to respond, please be patient (ready=0)
[55678.897149] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[55681.320305] ata1.00: configured for UDMA/100
[55681.320319] ata1.00: device reported invalid CHS sector 0
[55681.320349] ata1: EH complete
[55729.969443] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe A
[55729.969588] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
dmesg
[102884.889930] systemd[1]: systemd-journald.service: main process exited, code=dumped, status=6/ABRT
[102884.890305] systemd[1]: Unit systemd-journald.service entered failed state.
[102884.890333] systemd[1]: systemd-journald.service failed.
[102885.560745] systemd-coredump[28916]: Detected coredump of the journal daemon itself, diverted to /var/lib/systemd/coredump/core.systemd-journal.0.5bf9a012fed048ce8975998cf3c3c20e.6705.1427990901000000.
[102885.860957] systemd-journald[28919]: File /var/log/journal/b130c96d1371445d9ddeb40c51c77dd6/system.journal corrupted or uncleanly shut down, renaming and replacing.
[102921.797810] systemd-journald[28919]: File /var/log/journal/b130c96d1371445d9ddeb40c51c77dd6/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
[104179.117363] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
[104179.117369] ata1.00: failed command: READ FPDMA QUEUED
[104179.117375] ata1.00: cmd 60/08:00:48:88:8b/00:00:4d:00:00/40 tag 0 ncq 4096 in
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[104179.117377] ata1.00: status: { DRDY }
[104179.117381] ata1: hard resetting link
[104184.453382] ata1: link is slow to respond, please be patient (ready=0)
[104189.149114] ata1: COMRESET failed (errno=-16)
[104189.149121] ata1: hard resetting link
[104189.469276] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[104189.952982] ata1.00: configured for UDMA/100
[104189.952989] ata1.00: device reported invalid CHS sector 0
[104189.953004] ata1: EH complete
[104508.223792] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[104508.223798] ata1.00: failed command: SMART
[104508.223803] ata1.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 2
res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[104508.223806] ata1.00: status: { DRDY }
[104508.223810] ata1: hard resetting link
[104509.984601] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[104510.698126] ata1.00: configured for UDMA/100
[104510.698157] ata1: EH complete
One of the latest and worse
journalctl -xfa --system
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:00:e0:d6:75/00:00:00:00:00/40 tag 0 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:08:08:d8:75/00:00:00:00:00/40 tag 1 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:10:30:d9:75/00:00:00:00:00/40 tag 2 ncq 4096 out
res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:18:58:da:75/00:00:00:00:00/40 tag 3 ncq 4096 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:20:e8:e5:75/00:00:00:00:00/40 tag 4 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:28:80:db:75/00:00:00:00:00/40 tag 5 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:30:68:dd:75/00:00:00:00:00/40 tag 6 ncq 4096 out
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:38:90:de:75/00:00:00:00:00/40 tag 7 ncq 4096 out
res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:40:b8:df:75/00:00:00:00:00/40 tag 8 ncq 4096 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:48:90:e1:75/00:00:00:00:00/40 tag 9 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:50:98:e3:75/00:00:00:00:00/40 tag 10 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:58:c0:e4:75/00:00:00:00:00/40 tag 11 ncq 4096 out
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/c8:78:28:b9:2a/0b:00:4e:00:00/40 tag 15 ncq 1544192 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:80:b0:4b:c0/00:00:4f:00:00/40 tag 16 ncq 4096 out
res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/10:88:90:4b:80/00:00:50:00:00/40 tag 17 ncq 8192 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:90:98:22:81/00:00:50:00:00/40 tag 18 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:98:00:0e:00/00:00:5f:00:00/40 tag 19 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:a0:00:08:80/00:00:5f:00:00/40 tag 20 ncq 4096 out
res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:a8:80:08:80/00:00:5f:00:00/40 tag 21 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/10:b0:08:0b:81/00:00:5f:00:00/40 tag 22 ncq 8192 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:b8:70:c8:75/00:00:00:00:00/40 tag 23 ncq 4096 out
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:c0:20:c9:75/00:00:00:00:00/40 tag 24 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:c8:88:c9:75/00:00:00:00:00/40 tag 25 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:d0:58:ca:75/00:00:00:00:00/40 tag 26 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:d8:a0:ce:75/00:00:00:00:00/40 tag 27 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:e0:68:d3:75/00:00:00:00:00/40 tag 28 ncq 4096 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:e8:90:d4:75/00:00:00:00:00/40 tag 29 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:f0:b8:d5:75/00:00:00:00:00/40 tag 30 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1: hard resetting link
abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
abr 22 12:57:11 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
abr 22 12:57:11 echoes kernel: ata1.00: configured for UDMA/100
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x06
abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] CDB:
abr 22 12:57:11 echoes kernel: cdb[0]=0x2a: 2a 00 12 88 d7 c0 00 04 d0 00
abr 22 12:57:11 echoes kernel: blk_update_request: I/O error, dev sda, sector 310958016
abr 22 12:57:11 echoes kernel: EXT4-fs warning (device sda2): ext4_end_bio:317: I/O error -5 writing to inode 36311758 (offset 8388608 size 2695168 starting block 38869906)
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995128
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995129
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995130
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995131
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995132
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995133
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995134
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995135
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995136
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995137
abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x06
abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] CDB:
abr 22 12:57:11 echoes kernel: cdb[0]=0x2a: 2a 00 4b dd 39 88 00 01 78 00
abr 22 12:57:11 echoes kernel: blk_update_request: I/O error, dev sda, sector 1272789384
abr 22 12:57:11 echoes kernel: EXT4-fs warning (device sda2): ext4_end_bio:317: I/O error -5 writing to inode 34999445 (offset 0 size 192512 starting block 159098720)
abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x06
abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] CDB:
abr 22 12:57:11 echoes kernel: cdb[0]=0x2a: 2a 00 4e 2a b3 e8 00 05 40 00
abr 22 12:57:11 echoes kernel: blk_update_request: I/O error, dev sda, sector 1311421416
abr 22 12:57:11 echoes kernel: EXT4-fs warning (device sda2): ext4_end_bio:317: I/O error -5 writing to inode 35001016 (offset 0 size 2232320 starting block 163927845)
abr 22 12:57:11 echoes kernel: ata1: EH complete
abr 22 12:57:11 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
abr 22 12:57:11 echoes kernel: ata1.00: failed command: CHECK POWER MODE
abr 22 12:57:11 echoes kernel: ata1.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 25
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1: hard resetting link
abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
abr 22 12:57:11 echoes kernel: ata1: COMRESET failed (errno=-16)
abr 22 12:57:11 echoes kernel: ata1: hard resetting link
abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
abr 22 12:57:11 echoes kernel: ata1: COMRESET failed (errno=-16)
abr 22 12:57:11 echoes kernel: ata1: hard resetting link
abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
abr 22 12:57:11 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
abr 22 12:57:11 echoes kernel: ata1.00: configured for UDMA/100
abr 22 12:57:11 echoes kernel: ata1: EH complete
Current smart status:
smartctl 6.3 2014-07-26 r3976 [x86_64-linux-4.0.1-1-ARCH] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Toshiba 2.5" HDD MQ01ABD...
Device Model: TOSHIBA MQ01ABD100
Serial Number: Y44MT611T
LU WWN Device Id: 5 000039 5e1a80e85
Firmware Version: AX1P5E
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Sun May 3 16:42:06 2015 ART
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
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
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: ( 120) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
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: ( 234) minutes.
SCT capabilities: (0x003d) 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 0x000b 100 100 050 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1671
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 306
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 152
7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 699
10 Spin_Retry_Count 0x0033 106 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 300
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 216
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 14
193 Load_Cycle_Count 0x0032 099 099 000 Old_age Always - 14140
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 34 (Min/Max 16/44)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 19
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 0
222 Loaded_Hours 0x0032 099 099 000 Old_age Always - 515
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
226 Load-in_Time 0x0026 100 100 000 Old_age Always - 190
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 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 Vendor (0x50) Completed without error 00% 611 -
# 2 Short offline Completed without error 00% 611 -
# 3 Short offline Completed without error 00% 597 -
# 4 Vendor (0x50) Completed without error 00% 583 -
# 5 Short offline Completed without error 00% 583 -
# 6 Vendor (0x50) Completed without error 00% 575 -
# 7 Short offline Completed without error 00% 575 -
# 8 Short offline Completed without error 00% 547 -
# 9 Extended offline Completed without error 00% 529 -
#10 Short offline Completed without error 00% 355 -
#11 Short offline Completed without error 00% 355 -
#12 Extended offline Aborted by host 70% 355 -
#13 Short offline Completed without error 00% 319 -
#14 Vendor (0x50) Completed without error 00% 13 -
#15 Short offline Completed without error 00% 13 -
#16 Short offline Completed without error 00% 12 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
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.
Kernels used have been from 3.9 to current: Linux echoes 4.0.1-1-ARCH #1 SMP PREEMPT Wed Apr 29 12:00:26 CEST 2015 x86_64 GNU/Linux
Last edited by jesu (2015-05-03 19:42:53)

Something i'd noticed both the first time i was on arch and now i've reinstalled it, was that at first i didn't have this problem. I mean, when Arch was just installed. While i was installing and setting up everything.
Now, i'm not 100% sure about this, but i think problems began when using my current user. Disk is partitioned the following way:
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931,5G 0 disk
├─sda1 8:1 0 1000M 0 part
├─sda2 8:2 0 260M 0 part /boot
├─sda3 8:3 0 207,7G 0 part
├─sda4 8:4 0 25G 0 part
├─sda5 8:5 0 14,8G 0 part
├─sda6 8:6 0 80,5G 0 part /
├─sda8 8:8 0 599G 0 part /home
└─sda9 8:9 0 2G 0 part [SWAP]
So, i believe problems, for some reason, are related (and were related), both before and now, to the /home partition, /dev/sda8 in this ocassion.
Because of this, i booted into systemd rescue mode, like root, rw, and unmounted /home partition. Despite root-only limitations, i used the system for a couple of hours, started lxqt, browsed the web mainly, and experienced no problem at all.
Now i booted normally, with my regular user, and these problems are experienced just like before (and almost instantly, like 3 or 5 minutes after starting system use).
dmesg this time showed a some different log, though it's not the first time i see this. I just didn't saved that kind of log before.
[ 653.821719] ata1.00: exception Emask 0x0 SAct 0x100 SErr 0x0 action 0x6 frozen
[ 653.821726] ata1.00: failed command: READ FPDMA QUEUED
[ 653.821732] ata1.00: cmd 60/08:40:60:25:43/00:00:1b:00:00/40 tag 8 ncq 4096 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 653.821735] ata1.00: status: { DRDY }
[ 653.821739] ata1: hard resetting link
[ 659.156760] ata1: link is slow to respond, please be patient (ready=0)
[ 663.851604] ata1: COMRESET failed (errno=-16)
[ 663.851610] ata1: hard resetting link
[ 669.186591] ata1: link is slow to respond, please be patient (ready=0)
[ 673.881456] ata1: COMRESET failed (errno=-16)
[ 673.881462] ata1: hard resetting link
[ 679.216481] ata1: link is slow to respond, please be patient (ready=0)
[ 702.743982] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 703.012578] ata1.00: configured for UDMA/100
[ 703.012584] ata1.00: device reported invalid CHS sector 0
[ 703.012599] ata1: EH complete
[ 714.097642] systemd[1]: systemd-journald.service watchdog timeout (limit 1min)!
[ 742.443488] sd 0:0:0:0: [sda] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
[ 742.443494] sd 0:0:0:0: [sda] tag#18 CDB: opcode=0x2a 2a 00 28 c3 c6 40 00 00 10 00
[ 742.443497] blk_update_request: I/O error, dev sda, sector 683918912
[ 742.443503] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489866)
[ 742.443506] Buffer I/O error on device sda8, logical block 9323208
[ 742.443508] Buffer I/O error on device sda8, logical block 9323209
[ 742.443515] sd 0:0:0:0: [sda] tag#19 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
[ 742.443518] sd 0:0:0:0: [sda] tag#19 CDB: opcode=0x2a 2a 00 28 c3 c6 80 00 00 10 00
[ 742.443520] blk_update_request: I/O error, dev sda, sector 683918976
[ 742.443522] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489874)
[ 742.443524] Buffer I/O error on device sda8, logical block 9323216
[ 742.443526] Buffer I/O error on device sda8, logical block 9323217
[ 742.443531] sd 0:0:0:0: [sda] tag#20 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
[ 742.443534] sd 0:0:0:0: [sda] tag#20 CDB: opcode=0x2a 2a 00 28 c3 c6 d0 00 00 10 00
[ 742.443536] blk_update_request: I/O error, dev sda, sector 683919056
[ 742.443538] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489884)
[ 742.443540] Buffer I/O error on device sda8, logical block 9323226
[ 742.443542] Buffer I/O error on device sda8, logical block 9323227
[ 742.443547] sd 0:0:0:0: [sda] tag#21 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
[ 742.443549] sd 0:0:0:0: [sda] tag#21 CDB: opcode=0x2a 2a 00 28 c3 c7 10 00 00 10 00
[ 742.443551] blk_update_request: I/O error, dev sda, sector 683919120
[ 742.443553] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489892)
[ 742.443555] Buffer I/O error on device sda8, logical block 9323234
[ 742.443557] Buffer I/O error on device sda8, logical block 9323235
[ 756.187685] systemd[1]: systemd-journald.service: main process exited, code=dumped, status=6/ABRT
[ 756.187986] systemd[1]: Unit systemd-journald.service entered failed state.
[ 756.188116] systemd[1]: systemd-journald.service failed.
[ 756.188474] systemd[1]: systemd-journald.service has no holdoff time, scheduling restart.
[ 756.189106] systemd[1]: Stopping Flush Journal to Persistent Storage...
[ 756.189143] systemd[1]: Listening on Journal Audit Socket.
[ 756.189801] systemd[1]: Starting Journal Service...
[ 757.525493] systemd-coredump[1038]: Detected coredump of the journal daemon itself, diverted to /var/lib/systemd/coredump/core.systemd-journal.0.b8610e85f9074a418534aaee0adbac56.141.1430763073000000.lz4.
[ 758.133944] systemd-journald[1050]: File /var/log/journal/f646626ba4b647f48501020bf12ca33b/system.journal corrupted or uncleanly shut down, renaming and replacing.
[ 758.503041] systemd[1]: Started Journal Service.
[ 759.180771] systemd-journald[1050]: File /var/log/journal/f646626ba4b647f48501020bf12ca33b/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
[ 974.867721] ata1.00: exception Emask 0x0 SAct 0x3f80 SErr 0x0 action 0x6 frozen
[ 974.867732] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867742] ata1.00: cmd 61/08:38:68:d3:c5/00:00:1a:00:00/40 tag 7 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867747] ata1.00: status: { DRDY }
[ 974.867751] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867759] ata1.00: cmd 61/08:40:88:d3:c5/00:00:1a:00:00/40 tag 8 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867763] ata1.00: status: { DRDY }
[ 974.867767] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867774] ata1.00: cmd 61/08:48:a0:d3:c5/00:00:1a:00:00/40 tag 9 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867778] ata1.00: status: { DRDY }
[ 974.867781] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867789] ata1.00: cmd 61/20:50:c0:d3:c5/00:00:1a:00:00/40 tag 10 ncq 16384 out
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867793] ata1.00: status: { DRDY }
[ 974.867796] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867803] ata1.00: cmd 61/10:58:f0:d3:c5/00:00:1a:00:00/40 tag 11 ncq 8192 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867807] ata1.00: status: { DRDY }
[ 974.867810] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867817] ata1.00: cmd 61/08:60:10:d4:c5/00:00:1a:00:00/40 tag 12 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867821] ata1.00: status: { DRDY }
[ 974.867824] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867831] ata1.00: cmd 61/18:68:28:d4:c5/00:00:1a:00:00/40 tag 13 ncq 12288 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867835] ata1.00: status: { DRDY }
[ 974.867841] ata1: hard resetting link
[ 980.202774] ata1: link is slow to respond, please be patient (ready=0)
[ 984.900902] ata1: COMRESET failed (errno=-16)
[ 984.900908] ata1: hard resetting link
[ 990.236024] ata1: link is slow to respond, please be patient (ready=0)
[ 994.930829] ata1: COMRESET failed (errno=-16)
[ 994.930836] ata1: hard resetting link
[ 996.798104] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 997.014012] ata1.00: configured for UDMA/100
[ 997.014020] ata1.00: device reported invalid CHS sector 0
[ 997.014023] ata1.00: device reported invalid CHS sector 0
[ 997.014025] ata1.00: device reported invalid CHS sector 0
[ 997.014026] ata1.00: device reported invalid CHS sector 0
[ 997.014028] ata1.00: device reported invalid CHS sector 0
[ 997.014030] ata1.00: device reported invalid CHS sector 0
[ 997.014031] ata1.00: device reported invalid CHS sector 0
[ 997.014065] ata1: EH complete
There are some sda8 (home) related messages. I also found these messages first time Arch was installed (i think also related to home partition).
root and home partitions are both ext4.

Mac Mini Not booting due to hard disk being full

Hello All,
I have a Mini and has worked well for the past 12 months, last week i upgraded to the OSX Lion which also went very smoothly. However yesterday i had a message on my screen stating the my startup disk was full and i needed to make space. finding this a little odd as I have a TB external hard drive that everything goes to.
the mini frose during the deletion process after leaving for approx an hour i attempted to reboot. from this point i have only been able to access the disk utility through the DVD that came with the mini I have done a disk check and repair, also check permission all are ok exept for only having 49mb of hd space left.
I cant access safe mode as this will not boot either (tried to load for 8 hours) re install will also not work due to the amount of hd space available
has anyone got any ideas how i can clean the hard disk without formatting as ideally i would like to know what is causing the problem.
like a not very bright thing i left the time machine turned off so this isnt an option either??

Ok, basically it would involve the following
Boot from the DVD
Launch the Terminal.app probably from a Utilities menu which also lists Disk Utility
In Terminal you would need to type cd /Users/accountname/.Trash followed by pressing the return key
Then you would type ls -l and again press return
It would then list what is in the trash for that user account. If it begins with a D it is a folder, otherwise it is likely a file. The big number before the data would give an idea of the size of the item.
When you have found the one you want to delete (remember you cannot undo this) you would type the following to delete a file rm filename and then press return again.
The do ls -l again to see if the file has gone.
If you want to delete a folder that is in the trash then the command would be rm -r foldername and then again press return. Using rm -r is a particularly dangerous command if you do it in the wrong place or the wrong way you could delete everything on the hard disk.
Normally in single user mode (which you said was not working) you have to type some other commands beforehand to allow modifying the contents of the hard disk. I have not tried this via the DVD so I do not know if the same applied. If it does it is likely to refuse to delete the file and you should come back to me and we can work out the process.

Windows HP laptop won't boot Windows - possible hard disk failure!

Hi there!
A month ago my HP Pavilion dv6-6b57sa completely froze mid-use, and was unable to move the mouse or get any sort of response.
Naturally I held the power button to hard shutdown and restarted. Ever since then I have been unable to boot Windows 7 (the original OS) properly, and all I could get to was a Startup repair which took days to try to fix the issues, eventually coming up with a message saying it was unable to fix the errors.
Today I decided to ditch the data I had stored and do a fresh install - using the HP wizard by pressing F11 on boot and using a newly created USB Windows 7 install drive. After getting to the point of install process of Windows just loading the files, after choosing a hard drive partition successfully etc. the installation quit, citing a number of issues (screenshots link are below).
So I then try to restart the computer, and get a 'SMART Hard disk error' (screenshot link below) and when I select continue startup from there, it says Windows failed to start (screenshot link below) and then leads to me to the Startup repair manager again - which fails again - (screenshot link also below!)
So after doing a hard drive test, it says it has failed (screenshot link also below).
So what can I do? Is there a serious hardware related issue linked with the hard drive (which is bound to cost lots of £££ I bet), or are there further steps I can take?
Screenshot links: http://1drv.ms/1jnjviU
Many thanks for your help in advance,
Max

Yes and you had to at the moment since you won't have a key unless you buy one from Microsoft for about 99 dollars.
Try you best to get the key readble I mean try to read it, good luck!
Sorry because of different timezone I might not be able to help/reply you right away.IF that happens I deeply apologize!
**Click the White thumb if you like the answer.**
**Please mark Accept As Solution if it solves your problem and only solves your problem, if you have any more questions please ask, this also helps others to solve related issues.**
Feel yourself like home here, we are all happy to help, if you have an question reply or start a topic or pm me or an expert.

Old MBP won't boot, not even Target disk mode

Hi all,
My 2009 MacBook Pro was being used by a student to prepare some material for me while I worked on my new(ish) Retina MBP. The system was sluggish, despite numerous attempts to use disk repair on it, throw out unused programs, etc. It finally got so slow (we were scanning large files, and even the attempt to open Finder on a directory with the large files would cause it to freeze) that we re-installed the operating system. That didn't help, so we reformatted the disk (losing a lot of work) and started again. Things were working just fine (although it was getting slower again) and then out of the blue it would not boot.
We tried everything: Safe boot, single user, resetting *RAM, the whole kit and kaboodle.
We then set it us as a Target disk - and were happy to see some files. But happiness was only short lived. Two files could be copied before the disk refused to continue, noting errors. We turned it off and back on in Target mode - the firewire symbol appears, but it is not seen in the Finder. The disk utility can see it, but as soon as we try to verify or repair it, it disappears.
I've tried connecting it to a Windows machine - it dings, but does not appear. I've tried booting with the Install CD (won't move), I've tried booting with Linux (I get an error). Every now and then after a looooong time, it gets mounted as a Target disk. I've managed to scrape 3 (three) files from the disk, it is soon unresponsive, and then it won't mount again. Every now and they I can use the disk utility to access the disk, verify says I need to repair it, repair says I need to re-format the disk. I've done that a few weeks ago.
Any ideas for something else I can try? Thanks!

You have a hardware problem. Probably the drive has failed. But if the system does not turn on at all, no sounds of any kind, then the problem is more serious. Like the logic board has failed.
Connecting a mac hard drive to a windows system wouldn't work unless you have a program that will allow windows to read mac formatted drives. Windows can't do that itself. You need something like macdrive (I think it is called) or some other program that can read mac formatted drive on a windows pc.
But from reading your whole post the drive has completely failed. If the system still starts up, you hear the startup chime, all you have to do is replace the failed hard drive and reinstall the os and program to get the system working again.

MBP won't boot from HD or disk drive

After using my MBP daily since I got it in Feb, this morning it refused to boot. It got as far as the gray screen with the logo and the spinning cog. The cog would spin for a while then stop. Then nothing. This has happened a time or two when I'd installed a program that the computer didn't like, and I'd always been able to use the install disk.
This time it didn't work! I tried starting while holding the "C" --didn't work. Same thing..cog stuck.
Next I tried holding down the Option key while booting. This gave me a choice of HD or Disk drive. HD booted and immediately froze before I could do anything.
Rebooted and tried chosing the disk drive...nothing.
This has gone on all day with intermittent breaks to scream and punch pillows.
Next, I found a TechTools disk in my Warranty pack. I somehow managed to eject the install disk and put in the TechTools disk according to direction on the front of the disk, with C key depressed...nothing. I took out the battery and reset the power settings. No help. I've tried every key combination that is physically possible with only 10 fingers and nothing has helped.
I'm embarassed to say that I'm typing this on my husband's Fujitsu Lifebook. I'll never hear the end of this.
Please help!
MacBook Pro Mac OS X (10.4.6) 2gig

The genius is wrong. As long as you have the latest version of OS X on a PowerPC Mac it will work fine.
Here is a document from Apple that discusses the issue: Intel-based Macs: "You have inserted a disk containing no volumes that Mac OS X can read" alert message
You can't format a disk in an Intel-based Mac from a PowerPC Mac and have it boot successfully but you can access the disk or repair it.

My MBP won't boot anymore after "repair disk" and "repair disk permission"

My 2011 MBP 15 with Lion stopped working after I attempted to use Disk Utility to "repair disk" and "repair disk permission".
It was having weird issues before I attempted the repairs, it was freezing every few seconds no matter what I am doing, the whole thing would freeze with only the mouse movable. then after a few seconds it goes back to normal again. This happened after I downloaded and installed some updates from Apple. I don't know if the updates would cause this or it's something else.
In Disk Utility, "Repair Disk Permission" took 5 hours. While "Repair Disk" resulted in "Disk utility can't repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed up files".
Now when it boots, there's a loading bar under the Apple logo, it loads half way and shuts down itself.
I can still get into CMD+R Utilities though.
Any idea how I can extract the data out of the disk? I'm going to format and do a clean install.

mike2016 wrote:
This happened after I downloaded and installed some updates from Apple. I don't know if the updates would cause this or it's something else. Now when it boots, there's a loading bar under the Apple logo, it loads half way and shuts down itself.
A stopped loading bar is indicative of a failed firmware install that didn't complete, it's trying to install and is failing.
Do a PRAM reset
https://support.apple.com/kb/HT1379
Reboot into Safe Mode, (shift key down) then reboot normally and see if that fixes the issue.
https://support.apple.com/kb/TS2570
You may have to try to reinstall your firmware manually, you'll need another disk burning Mac
Find your exact firmware(s) here (or on Apple Downloads page)
https://support.apple.com/kb/HT1237
Apply instructions here
https://support.apple.com/kb/HT2213
Lastly it could be your boot drive is failing or something wrong happened with the update and accounting for all the to the other issues.
A OS X "overwrite" may solve the issue, may not.
See 10.5, 106. 10.7 OS X "overwrite" here
https://discussions.apple.com/message/16276201#16276201

MBP won't boot without power adapter also problem when waking from sleep

Hi guys,
I have a MBP 2.8 GHz Intel Core 2 Duo with 4GB 1067 HHz DDR3
I have had this issue for a while now and done a lot of research to solve the problem, but not got anywhere...
I can't boot the mac without the magsafe attached. Also, I'm not sure it is a related issue, but if I close the lid on the computer, it goes to sleep fine, but when I lift the lid to begin working again, the screen is like an opaque white and I get a blocked loading bar at the bottom that takes an age to clear and then when the screen wakes up it take a while to become life again. I also had an issue with the motion sensor. When I moved it, It would send itself to sleep. The battery icon also displays an X in it and has done for a while.
To try and solve this I have:
• Reset the PRAM
• Reset the SMC
• Booted from disc and repaired permissions and made sure the disc was OK
• Bought an new official Apple battery
• And pretty much everything else I can think of and have read about.
A while a go (Whilst in warranty) I had a problem with the USB board thingy (The board that runs keyboard, tracker pad and USB etc). Not sure if that helps.
I am starting to think it is hardware (RAM maybe??).
Can anyone help??
Thanks in advance.

As an update...
I have now tried:
Erasing the HD and installing SL from scratch and then used Time Machine to put back my files and apps.
Guess what... No joy.
Can anyone actually help with this? I take it I am on my own in this 'Support' forum?
If anyone has any further suggestions that I might be able to try that would be wonderful. My head is getting quite sore now from banging it against the brick wall.
Thanks in advance

Should I boot from external hard disk and how do I achieve this?

I'm in a downward spiral and need advice about if booting off of an external hard disc is the right thing to do and how to go about it. How I got into this mess I'll write below. My immediate problem is that I want to be able to install a copy of osx 10.5 from the original disks that came with my computer onto a usb hard drive. Then I want to boot from that drive and install software such as disk warrior on the same external hard drive in order to repair and recover the files on my internal hard disk. Not sure if this is easy to do with the install disk that came boxed with my macbook. So is what I want to do feasible and how do I do it? Thanks.
How did I get into this mess?
For those with time to read more. A downward spiral (and my macbook was working fine)::
I have been backing up my work documents onto a 20 GB pendrive waiting to get the money to buy an nas to work with time machine for the two macbooks we have at home as a place to backup photos and video. I bought a network drive but it wouldn't work with my macbook; my time machine backup freezing at 3 gb, but works fine with wife's macbook pro.
I tried to do TM backup on a usb hard disk and got the same problem. Support forums indicated that hard disk problems could confuse TM, so although I was experiencing problem free computing I ran disk utility from internal osx. This indicated an <invalid node structure - file system verify or repair failed> at the checking catalog file stage. So I followed instructions to run disk utility and repair from the installation disk. When I ran disk utility from installation disk I get exactly the same <invalid node structure - file system verify or repair failed>. It gets worse.
After failing with install disk utility, I could not then boot from my hard disk (I had had trouble free computing up to my attempts to use TM) or eject the disk. At first attempt I had no option but to boot from dvd again as hd not offered as an option. Second attempt hd option available but fails. By reading advice given to others I managed to eject the dvd and have tried:
safe boot - it won't
boot in verbose mode and single user (indicates I have disk0s2:I/O error) and won't boot
try to use disk utility from install disk to create disk image on external hd, it won't (cites i/o error)
If I can boot from an external I will try to repair with Disk Warrior as forums indicate that this software has been able to solve <invalid node structure> issues (but am open to recommendations of other products). I also hope that I may be able to try again to burn a disk image sucessfully if this repair works. I'm still trying to save my photos and videos that aren't backed up.
I plan to try an archive and install installation but first I want to try a repair with disk warrior as I fear that archive and install won't work and I'll end up having to erase and repair my hard disk.
I feel like some perverse god is punishing me for trying to do the right thing and back up my hard disk.
Macbook 5.1 late 2008
Intel Core 2 Duo
OSX Leopard 10.5.8
85 GB of a 150GB hard disk needs backing up (saving)

I am not sure about this, but my memory is that if you try to partition the drive (in OS 10.5.8) it will erase the data.
But you can try. Go through the Add a partition steps, but watch for any warnings. If my memory is correct there will be a message to the effect that everything will be erased. If you see that, do not proceed. This page has info about how to do it, if it can be done: http://www.macworld.com/article/1164643/live_partition.html
With respect to DW on an external, I do that. I have a 80 GB external - I call it Emergency - with an OS, DW and TechTool Pro on it. (Since I have is a recovery partition built in with all new OS, Emergency would be of use only if I need to run DW or TTP.) I have never yet had to use it, but it's there. It is not usually connected - I just did that for this screen shot.

MBP won't boot - "GRUB_" - tried installing ubuntu on an external drive

so i tried installing ubuntu netbook remix onto an external drive, and upon restarting my MBP won't boot to my internal HDD, once it displayed "GRUB_" with a blinking cursor, but is otherwise unresponsive.
now i just get the folder with the ? on it.
I've run disk util, repair permission, repair disk and still no luck.
i can boot the MBP into target disk mode and see the HDD on my other system and all appears to be good, and if i boot to the install dvd, the HDD shows up under the "startup disk" menu, but it just doesn't boot.
any thoughts on how to fix this?

So I have an imac that I have had for about 3yrs. About several months ago, it started acting a little strange, it wouldnt pick up the mouse or the keyboard at times even thought they were plugged in properly to the usb port, sometimes both would work sometimes one or the other would work and other times they worked fine. About a month or 2 ago, I went to turn my imac on and it got to the screen where the little circular icon pops up implying it is loading, stayed that way for 2-3min then turned of and turned itself back on and did the same thing, made the apple sound got to the load screen turned of after 2-3min then turned back on, it has been doing that for the past month. What do I do?

Transporting MBP: Sleep, Hibernation and dangers to hard disk

I used to transport my MBP by closing the lid and putting it in my backpack. Recently, however, it started to overheat when I do that. At first I thought it was some bug, maybe it hadn't gone to sleep properly. But then it happened again. I started to manually putting it to sleep before closing the lid, but no luck. It happened again. It happened 3 or 4 times in about 2 months and then the computer stopped working properly and I had to take it to professionals. They said I should NEVER put it in my backpack in sleep mode. Maybe if it's a 5min trip only, but not otherwise. They said the hard disk is not completely shut off in this mode and so carrying it around in movement may damage it. They checked my computer and said that indeed it was a hard disk problem, and that now that it was changed it's working fine. They said I should always shut it down before transporting it, which is a pain. (I live in Rio and it's above 30ºC most of the year, maybe that contributes to these heating problems, don't know…)
What annoys me is that I haven't found any official statement about it by Apple. I know people who never turn it off and even I did it without any problem for years with my previous MBP (well, in fact it died one day out of the blue and I have no clue why). Actually I can only assume based on discussions that the computer actually goes to sleep mode when I shut the lid, and I can only speculate about what this actually means because I haven't found any official information regarding it. I found that there's a mode called "hibernationmode 25" which is supposed to be essencially the same as shutting down the computer and saving the current RAM data to the hard disk. But I haven't found any official statement confirming this. I don't know if it really is as safe to carry it shut down as in this mode. Does anybody know where I can find official information about this? Or if there's any reliable way to contact Apple itself and actually get a reply?
Thanks!

The Expert, Professional, you spoke to has NO clue. When any computer is put to Sleep, irrespective of what OS is installed (OS X or Windows) and what version of that OS, the only part that is supposed to be kept alive is the RAM and even that will go to sleep and dump it's contents onto the hard drive after an extended period of time if the system also has the hibernation mode set to do so. It then goes into a Deep Sleep state basically turning off completely.
I suspect what you are seeing it the system is trying to go from standard sleep mode to the Deep Sleep Hibernate mode and when that happens it must partially wake up to write the RAM data to the hard drive. At that point your system is not going back into either sleep mode or the Deep Sleep mode and that is when it heats up.
There are also many reports of Mac's of all ages crashing when trying to wake up from sleep and most of the time this is after it has gone into the Deep Sleep state and when you try to wake it the system doesn't or can't put back into the RAM the data that was written to the hard drive causing the system to hang and force a hard shutdown and restart.
I personally solve that problem by turning off the Hibernate system and deleting the Sleep Image file that is used to store the RAM data. So my MBP never going into that Deep Sleep state and I have never had a problem waking it whether after a few minutes or a day or so of being asleep. And it has never woken up on its own in my computer bag.
But to answer your question, statement from that Professional, the hard drive turns off completely when the system is put to sleep.

Yet another "won't boot from a certain disk" issue

My Sawtooth G4 just got a new second drive, which seems to work fine. At first it wouldn't boot OS 9 (there are multiple partitions on it) but after some messing with the OS 9 install disk and changing the Startup Disk in the control panel I got that sorted out. The real problem is with OS X. I'm running 10.3.9 on my primary HD and I wanted another OS X system on the new HD so I CCC'd my first disk to the new HD's first partition (which worked fine on the old drive's second partition, now erased) but the Mac won't boot from it. It showed up under the boot options menu (hold option down) but simply wouldn't boot from it no matter what. Finally, I erased the partition and installed OS 10.3 then upgraded it to 10.3.9 (still won't boot from it) but the problem continues. I get the spinning wheel followed by the circle with the bar through it.
It looks to me like there are tons of possible causes for this after reading through several similar threads here. Could somebody tell me what the most logical approach is to fixing this? Or maybe there's some stupid obvious thing I forgot?
Thanks!

Haven't you ever had a system crash or something that messed up your startup disk or some portion of the OS? And what if your prefs or anything custom has been affected? If you only have one startup drive and it gets hosed you are really in a world of hurt, as then it's up to recovery methods to salvage things. And if you don't have unlimited time to sort all this out? It seems obvious why I would want two startup disks - I've used this system for fifteen years and it just works, thats all. Under OS 9 everything was a lot simpler - you just copied the files to another disk and if they were there, you got a boot disk; everything is a lot more complex in X and I don't really understand it even now.
Then there's the issue of why the other startup disk, while recognized as such, won't boot. That's a puzzle to me. I can't imagine how the Carbon Copy Cloned disk wouldn't work for this - that's what I did before and it worked fine.
The new drive is a SATA drive with an OWC card, but since the partitions with OS9 boots work fine I don't know what to think. (I have to have OS 9 because I still use Vision for my sequencing and audio recording, and because 9 crashes more often than X I always have at least two boot disks of my main system - just in case.)
Thanks.

How to boot Linux USB Hard Disk from Windows Machine?

*Dears,,*
I have XP windows Machine . . .
My laptop is Qosmio F20 155
I need to boot Linux USB Hard Disk .
I tried to enter setup menu to arrange the boot perority to make The USB Hard Disk FIRST but i cannot enter setup menu
Please, help me ASAP
*Many Thanks & Regards,,*
Message was edited by: eng_mohammedmostafa

*Dear,,*
FYI , , ,
We have another laptop (VAIO) and we can enter BIOS and edit the priority boot and it run successfully . . .
But in laptop (Toshiba) We can't make it.
*Thanks & Regards,,*
*Eng Mohammed Mostafa*

ZEN EXTRA EAX FREEZES"HARD DISK PROBLEM" AND WON'T RESCUE:HOW I FIX

Well nobody tried to help me so I got on the web.first if you try to paperclip reset and nothing,try this:hold the paperclip(you need both hands) and hold play/pause at the same time and disengage paperclip and you get rescue mode this is how I fixed it once,their are four options:clean disk,reboot and two more.CLEAN DISK AND RE-BOOT ONLY!Because the second option will clean out your library!If that does'nt work and if it says:"hard dri've problem" after trying several times you have to smack it on the palm of your hand and after three smacks it went back to normal!(By the way it fell off the countertop with the protecti've case and that's when this night time nitemare began,milk and cookie insomnia cure!). It just skipped,the hard dri've looks like a little record player and I guess it(like a needle on a record it jumped?)But now it works perfect again. I have "THREE WARRENTY",(TWO YEARS LEFT) but I would lose my 2,800 library if replaced repaired! A chance I did'nt want to take.PLMK if this works,SANSOO..........

A few weeks ago I dropped my Extra and had the same problem, it was now out of warranty so I figured I had a paperweight, so when I ran into this thread I figured I had nothing to lose., and gave it firm whacks on my palm, (the first one didn't work) To my surprise it powered back on, and now seems to work. I transferred new songs to it and it is now charging up again. I admit this has all occurred in the past hour so I don't know how permanent this is, but it does give me hope. I would like to emphasize though that this was a last ditch effort. I had tried going into the recovery mode and got a hard disk problem error so none of the regular options would work.

Hard disk problems after full upgrade [SOLVED]

After a full upgrage (pacman -Suy) last monday, My system denied to boot:D:D:D:D:D.
So to fix it I have to go to /boot/grub/menu.list and change from hda3 to sda3. Everything seems to be Ok but when the system is booting and scan the the hard disk to check bad, It drops me to the shell with the error that there is something wrong with my hard disk and it suggest me to set the superblock to 8139.
So to fix it I boot my PC from Arch live CD, use the following command:
#fsck.ext3 -c -f /dev/sda3
#fsck.ext3 -b 8139
Everything seems to be Ok, there is no bad in my hard disk.
When I boot my system again, I got the same error again, I came back to live CD, check the hard disk, set the superblock as It told me and again, I got the error when I boot from the hard disk.
This is the second PC with the same error.
Three months ago, I upgraded my Server and got exactly the same problem. Because this is the server, I need it run ASAP, so I modified the rc.sysinit script so that the system will not check my hard disk when It boots. :P:P. And my Server can run without any problems since then.
I don't have time much to spend on this error and my PC is in the Lab now so I can't provide the detail of the error until next Monday. Sorry for that.
Any idea how to fix this error?
Cheers.
Last edited by hungsonbk (2008-06-25 10:26:35)

tigrmesh wrote:Did you review and merge any .pacnew files after the upgrade?
:D:D I am a kind of lazy guy so when I did pacman -Suy, I just leave it running without reading information on the terminal.
milan wrote:I guess you didn't change entries in /etc/fstab (hda->sda).
Yes, you are right. I changed from hda to sda in /boot/grub/menu.lst but I forgot to do the same in /etc/fstab files. On Monday I will check again if it is set correctly or not
:D:D. I have just taken a quick look into the fstab file in my Server, The One with the same problem three months ago, and the fstab file is set correctly with sda partitions. I don't want to touch this server again or my services will be down. So this seems not the correct solution, but anyway, I will take a look at it next week.
Thanks for your replies.

MBP won't boot due to hard disk problem

Similar Messages

Maybe you are looking for