Disk problem, which size is correct?
Hi,
can sb tell me which information about free space is correct?
Screen with information from my computer https://www.dropbox.com/s/pcxws5fh7dbowfx/Zrzut%20ekranu%202014-07-22%2000.41.54 .png
How can i fix this information?
Click here and see the bottom of the article.
(109779)
Similar Messages
-
I've a problem which is: Ibelieve there's someone who knows my password in some games like "Happy Day" so, could you please help me by not letting anybody to use this game except for this IMEI 01 336000 521261 1 even if they have the correct password. Thanks alot for your help.
Change your password.
These are user forums. We can't do what you ask, in fact no one can. -
I cannot reactivate my e-reader with my existing Adobe ID and password which are both correct. I alwayss get the message "activation server error, Code: E_AUTH_NOT_READY" What kind of problem is this and what is most important, how can I solve it quickly. I am on holiday and want to read. Thanks for speedy reply.
Yes, actually I talk about Digital editions. Do you know how to solve the problem as described in my first mail for Digital Editions? Thanks for your kind assistance.
-
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. -
How do I resolve LOCKED DISKS problem ? NO ACCESS ANYMORE !
Hello everybody,
I've looked carefully where to post this topic,
and I hope it's the right place here
(I have already been warned not to post the same questions in different places).
I have actually 2 internal volumes locked, 2 external Firewire volumes locked and 2 USB external volumes locked. I'm talking about *5,7 To* with *NO ACCESS* anymore.
It happened suddenly, and I was working on Snow Leopard 10.6.3 internal drive. This volume is the *only one* that has NOT been locked, but I lost a lot of applications, documents and so on on it.
Each of the locked volumes I am talking about shows,
in *Sharing & Permissions* (Get Info window),
the same Privileges :
— everyone : Custom
— admin : Custom
— olcha (Me) : Custom
— staff : Custom
— everyone (again) : Custom
You'll notice that "System" is not there (should be there with R+W),
and "admin" should have also R+W privilege.
I don't know why "staff" is here (perhaps, one day, somebody will explain to me the difference between : wheel, staff and admin).
I also don't know why "everyone" is there two times.
If I unlock the padlock (bottom right) with my password, I can only
check or uncheck the "Ignore ownership on this volume" square (bottom left).
Doing this (apparently) offers *no interest at all* to solve the problem
(and what does this function produce, when activated or not ?).
I can't *absolutely not* :
• Change *any privilege* of any of the 5 items ;
• Remove (with "-") any of these items ;
• Add a line (for example "System" or "wheel", why not ?)
but nothing new is shown after "+" making.
• The wheel (on the right of "+" and "-") shows only "revert changes" in grey.
I phoned immediately last thursday Apple Assistance,
and I am in contact with a Level 2 Apple Adviser who gave me his e-mail.
I sent him two messages, but he replied me that perhaps MONDAY
he could find the time to call me.
Now, first, please tell me if you have any idea or solution !
Thank you very much in advance.
Secondly, I have reflected on the solving,
and would like to know what you think about what follows :
You know that, in Disk Utility, you can erase a disk or partition.
If, in "Security Options…", I choose "Don't Erase Data", and then "Erase…" :
1) Sharing and Permissions will be changed and become (reset to) correct ;
2) It's said, in "Security Options…",
that "many commonly available disk recovery applications can restore that data".
I would be very glad that you indicate me :
1) the best application to use for that recovery ;
2) I already own "Drive Genius 3.0", "Data Rescue 3.0.2" and
(I think it's the best after a try on an internal 30 Go partition)
"Stellar Phoenix Macintosh Data Recovery".
Thank you in advance for your answers and advices,
With my kind regards
Olivier Herrbach
[email protected]
PS : Dear Forum Webmaster,
I would like to know :
1) if I posted this topic in the right place ;
2) if you allow me to post it elsewhere (and in this case, where ?) ;
3) is it possible to paste images in messages,
and, if yes, which format is needed (TIFF, png, jpeg …)
Thank you very much
Olivier HerrbachDear ChazBowie,
Here is the solution I've found for *LOCKED DISKS* problem.
I'll respond the shorter I can, avoiding for the moment to talk about the complicated solutions
that Apple gave to me, which involved volume by volume (only one each time) intervention, and were working by, each time, entering one line, password, then another line in Terminal. I will communicate these instructions later, but they do not need to be publicated here with urgence.
I found two little free softwares that can modify *ALL Privileges* in Sharing and Permissions, *on ANYTHING*. You will have to be careful using them, as they even allow to act as "Root" administrator.
I'd also like everyone to *donate anything* to these helpful developers, and I'd be very pleased to have *your feedback and results*.
••• 1) — *BatChmod 1.6.2* (162), written by a compatriot, Renaud Boisjoly.
E-mail (if you have doubts or questions) : [email protected]
Free software downloading site : *http://www.macchampion.com/arbysoft*
(excuse me, but I don't know how to make a link here).
••• 2) — *FileXaminer 2.7*, recommended by Renaud himself.
Dear ChazBowie,
Here is the solution I've found for *LOCKED DISKS* problem.
I'll respond the shorter I can, avoiding for the moment to talk about the complicated solutions
that Apple gave to me, which involved volume by volume (only one each time) intervention, and were working by, each time, entering one line, password, then another line in Terminal. I will communicate these instructions later, but they do not need to be publicated here with urgence.
I found two little free softwares that can modify *ALL Privileges* in Sharing and Permissions, *on ANYTHING*. You will have to be careful using them, as they even allow to act as "Root" administrator.
I'd also like everyone to *donate anything* to these helpful developers, and I'd be very pleased to have *your feedback and results*.
••• 1) — *BatChmod 1.6.2* (162), written by a compatriot, Renaud Boisjoly.
E-mail (if you have doubts or questions) : [email protected]
Free software downloading site : Gideon Softworks : *http://www.gideonsoftworks.com/*
I won't copy here the texts that are on both sites, but it's very instructive.
Remember that the applications don't only work on files and folders,
*but also on disks attributes*.
You'll also have some work to do (I don't remember, perhaps not), by going in the Get Info windows
and changing privileges to the correct ones, that means you must know
(I'm not sure, verify please) what privileges are to be set for a volume
(YOU WILL HAVE ACCESS TO THEM, AND CHANGES YOU MAKE WON'T BE RESET TO "CUSTOM").
Does anybody know something about the "Ignore ownership on this volume" checkbox ?
*I always uncheck it*.
I would also like very much to know the differences between the two-headed iconed groups :
"staff", "wheel" and "admin", and IN THE END know *WHERE are the rules* you have to observe
when doing changes in privileges (for example, I don't want to give my password to copy something in Users folder, nor "MyName" folder. I've changed that without, I hope, having created any dysfunction).
Please tell me if you know anything about these 2 subjects above.
I'm very glad if my informations have been useful/helpful.
With my kind regards,
Olivier Herrbach -
Disk Utility no longer working correctly
I did a search and couldn't find a similar problem, so here goes.
I'm running OS 10.4.11 on a G4 PPC Dual 1.25 GHz.
I've done the regular updates the last several weeks:
QuickTime-7.5.5
iTunes- 8.0
Xserve RAID Driver Update- 1.0
Java for Mac OS X 10.4, Release 7- 1.0
Digital Camera Raw Compatibility Update- 2.2
Security Update 2008-006 (PowerPC)- 1.0
Security Update 2008-007 (PowerPC)- 1.0
Migration and DVD/CD Sharing Update- 1.1
iTunes- 8.0.1
iPhoto Update- 7.1.5
Digital Camera Raw Compatibility Update- 2.3
Safari- 3.2
iLife Support- 8.3.1
iTunes- 8.0.2
Safari- 3.2.1
Since the updating of the above, when launching Disk Utility, I get the spinning beachball as it tries to find my hard drives. It spins and spins and spins, but my drives don't show up.
Sometimes logging out and back in and then restarting will make DU work ok, but that can't be normal. It should work on each launch.
Is anyone having similar problems? Anyone know what the cause and solution may be?
Thanks in advance for any help, and Happy Thanksgiving!Hi,
Could be many things, we should start with this...
"Try Disk Utility
1. Insert the Mac OS X Install disc that came with your computer, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu. (In Mac OS X 10.4 or later, you must select your language first.)
Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.
3. Click the First Aid tab.
4. Click the disclosure triangle to the left of the hard drive icon to display the names of your hard disk volumes and partitions.
5. Select your Mac OS X volume.
6. Click Repair. Disk Utility checks and repairs the disk."
http://docs.info.apple.com/article.html?artnum=106214
Then Safe Boot , (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it finishes.
The usual reason why updates fail or mess things up, or things don't load/run, is if Permissions are not fixed before & after every update, with a reboot... you may get a partial update when the installer finds it doesn't have Permissions to change one obscure little part of the OS, leaving you with a mix of OS versions.
Some people get away without Repairing Permissions for years, some for only days.
If Permissions are wrong before applying an update, you could get mixed OS versions, if Directory is the slightest messed up, who knows!
If many Permission are repaired, or any Directory errors are found, you may need to re-apply some the latest/biggest updates again, or even do an A&I if you have enough free disk space.
The combo update for PowerPC-based Macs...
http://www.apple.com/support/downloads/macosx10411comboupdateppc.html
The combo update for Intel-based Macs...
http://www.apple.com/support/downloads/macosx10411comboupdateintel.html
Repair Permissions before & after re-install, then reboot again each time.
If all the above do not resolve the problem, then it's time for an Archive & Install, which gives you a new OS, but can preserve all your files, pics, music, settings, etc., as long as you have plenty of free disk space...
http://docs.info.apple.com/article.html?artnum=107120
Or, Might give a try with Applejack...
http://www.versiontracker.com/dyn/moreinfo/macosx/19596
After installing, reboot holding down CMD+s, (+s), then when the DOS like prompt shows, type in...
applejack AUTO
Then let it do all 5 of it's things.
At least it'll eliminate some questions if it doesn't fix it.
The 5 things it does are...
Correct any Disk problems.
Repair Permissions.
Clear out Cache Files.
Repair/check several plist files.
Dump the VM files for a fresh start. -
I am not very computer Savoy!. But every time I turn my laptop on it keeps freezing up on me and I get a massage that says I am having a Hard Disk Problem and that I should back up all my files before the computer crashes. And I would like to what I should do to fix this? I thought that I could reload my operating system but my computer did not come with that disk and I can't seem to find it here on this web site. Any idea's?
Without knowing specifically which model you have it's difficult to tell for sure, but most Toshiba's made in the past few years come with a Recovery Partition. You can invoke the Recovery Process by holding down the 0 (zero) key while turning the computer on and holding it down until the Recovery Process starts. You can also create a set of Recover Disks from the Recovery partiton by going to "Start - All Programs - Toshiba - Recovery - Recovery Disk Creator".
As for the error message about Hard Disk Problem, that could mean that the hard drive is starting to malfuncion and will soon stop functioning at all. You need to determince what brand of hard drive your's is, go to that companies support site, download their Diagnostic Program, install it, and run the most exhaustive test to determine if it is failing or not.
And please backup you important data as soon as humanly possible as there is a good chance you will lose it forever.
If you don't post your COMPLETE model number it's very difficult to assist you. Please try to post in complete sentences with punctuation, capitals, and correct spelling. Toshiba does NOT provide any direct support in these forums. All support is User to User in their spare time. -
Hi, I have the problem which iTunes cannot detect my iPhone 4s. I tried the steps you have provided in your troubleshooting, but it won't work for me because the Apple Mobile Devilce is perfectly installed on my windows. However, the driver "Microsoft teredo Tunneling adapter" has a yellow exclamation mark, which i believe means it's not installed correctly or something is wrong with it. This driver is under the Network Adapters (Please see picture below).
This is what happens when I connect my iPhone 4s to my laptop (Windows 7 Starter 32-bit)
1. The phone charges it's battery
2. I can open it in My Computer and import/export media files.
In iTunes
3. It start to sync until step 3 then stops.
4. The iPhone option with an arrow appears beside the iTunes Store, but when the arrow is clicked it disappears.
I hope you can provide me a solution for this problem.
Thanks,
RalphHi ralphagir,
Welcome to the Apple Support Communities!
For your iTunes issue with it not recognizing your iPhone, I would go ahead and suggest deleting iTunes and all of its components from your Windows computer and installing fresh.
Removing and reinstalling iTunes and other software components for Windows Vista, Windows 7, or Windows 8
http://support.apple.com/kb/HT1923
Remove iTunes and related components from the Control Panel
Use the Control Panel to uninstall iTunes and related software components in the following order and then restart your computer:
iTunes
Apple Software Update
Apple Mobile Device Support
Bonjour
Apple Application Support (iTunes 9 or later)
Important: Uninstalling these components in a different order, or only uninstalling some of these components may have unintended affects.
As far as the arrow button that you click and the iPhone disappears, it sounds like you may be clicking on the eject button. Please take a look at the following article for information on the eject button in iTunes.
Safely disconnect iPod
http://support.apple.com/kb/HT1853
Have a great day,
Joe -
I have a Macbook pro 2009 with Snow Leopard. Which system can I install without running into complicated problems which I will not be able to solve by myself- a person with limited problem solving abilities. (Mountain Lion, Mavericks, Yosemite?)
It will make it easier to help you w/ your problem to know the size and RAM installed.
"Yesterday I couldn't update the maps on my Garmin because it said the OS I had wouldn't work"
What OS will your Garmin work with? Funny there was someone else that did that and upgraded to Yosemite and regretted it.
I'd say Lion if your Garmin is compatible.
Both Lion and Mountain Lion are downloadable from the Apple Store:
http://store.apple.com/us/product/D6106Z/A/os-x-lion
http://store.apple.com/us/product/D6377Z/A/os-x-mountain-lion
The OSs will get more resource hungry the higher you go. -
Problems after force reboot. Hard disk problems
Yesterday, I ran a c program on my work station. And, the program have some big out puts, files with size 2G,7G.
And then the disk was filled. Then some problem happened.
When rebooting it shows something like:
INIT: cannot execute "/sbin/agetty"
INIT: Id "c2" respawning too fast: disabled for 5 minutes
And then, after some time. It successfully boot up. But there are still problems:
when I try to delete or mv or cp some of the big data, the /home directory file system automatically remounted as read only file system.
And I try to reboot it. It again seems ok, but still can't do any thing to the data, if I try the same thing happens again.
After some search, I thought there must be some problem on the disk. And try to fix it.
I find a unbuntu 12.04 CD, use the disk utils, I mis-formatted the swap area.
Now, it is repeating the error like:
INIT: cannot execute "/sbin/agetty"
INIT: Id "c2" respawning too fast: disabled for 5 minutes
and can't boot.
What can I do now. How to fix my disk? It a workstation for many people, and the disk is of size 1 T, the /home directory has a size about 800 GB with 780 used.
What I can do?/home partition doesn't count in this case - it can be filed 100% if it's separate partition. For system to work properly you need some space left on root partition.
Boot-up live cd and see what's your disk usage looks like.
PS did you tried cp or mv files from within live cd?
Last edited by masteryod (2012-11-21 15:47:18) -
I appear to be having hard disk problems and would appreciate any suggestions as to how to determine what the cause might be.
It began when the MBA late 2008 with 10.6.6 would not startup, just an endless cog wheel. Using the installation disk I found that the disk repair utility identified that the MBA hard disk was corrupted and the repair utility couldn't repair it.
I deleted the contents of the MBA disk verified the disk and reinstalled the system software and all my other programmes and files.
(This took about a day as I did not have a backup of the MBA but I did have the files and programmes on other disks etc. (Never again - I bought an external hard disk so that I could have a copy of the installation disc on it and also a backup of the MBA and all the system software updates.)
All has been well for a couple of weeks until today when the MBA would not start. For the first time in my life I saw a message covering most of the screen saying "Will not start up - turn the computer off by holding down the power button until it turns off and then restart the computer" or something similar.
Needless to say the computer refused to restart and again after looking at the MBA disk with the disk utility it required repair and again the repair utility said it could not complete the repair.
Wiped the MBA disk again and reinstalled and restored the programmes and files. (so much easier with the install image and backup on an external hard disk and Time Machine is tremendous).
So the MBA appears to be back to normal.
But will it stop again? It the hard disk flawed or fundamentally corrupted?
I have verified the hard disk with the apple disk utility and also with onyx. Both say it appears to be ok.
Any suggestions as to how to work out what if anything is going wrong would be much appreciated.When I said verified I meant that I ran the verify and repair command in the apple disk utility and also ran both the smart status in onyx and additionally the verification command in onyx.
Just to clarify the second occasion that the MBA would not startup falls under the category of “You need to restart your computer” which indicates a indicates a “kernel panic”. -
Windows has detected a hard disk problem
I just got a warning from windows that I have a hard disk problem then Toshiba Utility notifies me with the following:
Disk0
Your HDD has the SMART Predict Failure function which monitors the HDD operating status. Your HDD is experiencing a problem and SMART monitoring software predicts that the HDD will fail. Toshiba strongly recommends you create a back-up for your HDD data. Then contact an authorized service provider in order to check your drive and purchase a new replacement drive if necessary.
I have never had problems with a hard disk, all I know is that I should get a backup drive as soon as possible. After I back up my files and everything....what is the next step? Take it to a repair man to fix, get a new harddrive, contact about warranty, what exactly do you do with this kind of situation? Is it fixable?
System Details:
Toshiba Satellite L675D-S7052
Windows 7 Home Premium 64 BitIf you're computer is under warranty, you should contact customer support at (800) 457-7777. The hard drive will need to be replaced.
- Peter -
Recurring iMac G5 Hard Disk problem and worthless AppleCare
Hello all! I have a recurring iMac G5 2Ghz (20-inch) Hard Disk problem.
I bought my parents, aged 52 and 55, an iMac last summer. Hoping this would be their solution to a hassle free and easy computer environment, since I would leave for China for about 1 year. But last month the hard drisk crashed and could not be fixed.
At first the start up speed slowed down, then the start up process would continue infinitely, then the computer just booted into a screen with a question mark.
I have a AppleCare Protection Plan (APP) and so I called the Help Desk and they put me in touch with a Service Center (Sittard, the Netherlands). Now I thought, since I live within the proper range of at least 3 service centers (Heerlen, the Netherlands), I could get on-site support (as stated in APP), unfortunately for unknown reasons, my parents had to drag the 20 inch monster to the service center.
Normally the repair should take 2 days, but instead it took 10 working days. My dad naturally asked, if they could restore the data on the disk. This was only possible if we paid about 2000 euro. So, no deal!
After picking the iMac up again, the computer booted into the Mac OS installation. This again surprised me, since according to the APP they should at least put some effort into restoring the applications. Not even iLife was pre-installed, which was of course on the computer when we bought it. Next to that the Service Center's Mac OS installation disc was still in the drive; how careless!
They were quite sad about the lost data, but accepted it, as we all know that these things can happen to electronics. BUT today, the same problem recurred! First the start up process slowed down and now (again) it tries to start up infinitely.
The hard disk is brand new (1 month), no strange programs and no abnormal use. According to the diagnostic tools the file structure is damaged, but it seems to keep getting worse. The Apple Help Desk guy was even surprised this happened to a brand new disk and installation. He recommended reinstalling the system.
But, I'm not happy with this solution! A hard disk breaking down, is one thing. But the same problem recurring 1 month later made a couple of alarm bells go off. I'm hoping Apple will consider replacing this machine from **** with a brand new iMac. Since my parents are scared ********, that whatever document they type today might disappear again tomorrow. This is not a comfortable computing experience.
By the way: the computer has only basic software: Microsoft Office, Skype and iLife and my parents only use those programs, surf the net and send email.
Any of you had a similar bad experience with the iMac's hard disk, AppleCare or any of Apple's Service Centers? Or does anyone know how to reach Apple by email?
iMac 20 G5 2Ghz Mac OS X (10.4.6)I had a similar problem with my 20" 2Ghz iMac.
After replacing the HD and the next 'going bad' the tech realized there was a different problem.
After discussing it, and the distance to an authorized repairer he offered on-site repair.
After a lengthy parts delay I was offered an upgrade to a iSight iMac.
The tech narrowed my problem down to a faulty logic board before offering a replacement. He could have been wrong but it seemed logical with all of the same symptoms.
Press your AppleCare to replace this computer. They are going to try and repair but insist if this fix doesn't work you want a new iMac.
I hope everything works out for you.
Edit: There is a great program that Apple techs recommend called DiskWarrior. It did not fix my problem but it allowed me to get my most important info off of the computer before it went to computer heaven. Might not work for all but it works well for me as I still use it today. -
Hard Disk problem - Lenovo G470
Dear Members,
Good Day!
Over the past few days, I have being getting warning messages in Intel Raipd storage technology app that " Disk on Port 0: At risk"
I have ran a hardware scan on my Hard disk and have noticed few of the tests getting failed, I have gone through many of posts in this fourms and understood that, my HDD is having some problem and it may crash any time.
I have taken back up of my factory default recovery disks in to DVD's. However I would like get clarified on few things related to replacing the existing HDD and setting up windows 7 in my new HDD.
1) After replacing my OLD HDD , In my new hard disk do I need to create the C disk with same size as that of OLD HDD for the OKR to work and restore everything properly.
2) Will the one key recovery feature work with my new HDD as well? If not , what should I do make it work?
3) Will the OEM parition( having factory default backup )be automatically created in new HDD ?
Please find the Hardware sacn result below from Lenovo solution center.
Toshiba-TOSHIBAMK6465GSX-11AJC329T
Display name
TOSHIBA MK6465GSX - 596.17 GBs
Type
INTERNAL_STORAGE_DEVICE
Model
TOSHIBA MK6465GSX
Manufacturer
Toshiba
Serial
11AJC329T
Firmware
GJ004E
Size
596.17 GBs
Rotation Rate
5400 RPM
Cache
UNABLE_TO_OBTAIN
Temperature
45 C
Physical Sector Size
512
Logical sector size
512
Logical sectors
1250263728
Supported standards
ATA8-ACS, ATA7-ATAPI, ATA6-ATAPI, ATA5-ATAPI, ATA4-ATAPI
Spec version
VERSION_NOT_REPORTED
Partition schema
MBR
INDEX 1
PARTITION_TYPE: PRIMARY
FILESYSTEM: ntfs
LABEL: UNABLE_TO_OBTAIN
MOUNT_POINT: UNABLE_TO_OBTAIN
SERIAL: UNABLE_TO_OBTAIN
SIZE: 200.00 MBs
USED: UNABLE_TO_OBTAIN
FREE: UNABLE_TO_OBTAIN
INDEX 2
PARTITION_TYPE: PRIMARY
FILESYSTEM: ntfs
LABEL: UNABLE_TO_OBTAIN
MOUNT_POINT: C:\
SERIAL: 163D14D6
SIZE: 137.23 GBs
USED: 44.75 GBs
FREE: 92.48 GBs
INDEX 0
PARTITION_TYPE: EXTENDED
SIZE: 443.99 GBs
INDEX 3
PARTITION_TYPE: PRIMARY
FILESYSTEM: UNKNOWN
LABEL: UNABLE_TO_OBTAIN
MOUNT_POINT: UNABLE_TO_OBTAIN
SERIAL: UNABLE_TO_OBTAIN
SIZE: 14.76 GBs
USED: UNABLE_TO_OBTAIN
FREE: UNABLE_TO_OBTAIN
INDEX 4
PARTITION_TYPE: LOGICAL
FILESYSTEM: ntfs
LABEL: Madhu-Drive
MOUNT_POINT: D:\
SERIAL: FEFA510A
SIZE: 443.99 GBs
USED: 105.38 GBs
FREE: 338.61 GBs
Diagnostics
SMART status test
Failed
Targeted read test
Failed
Random seek test
Passed
Funnel seek test
Passed
SMART short self-test
Failed
SMART drive self-test
Passed
Processor : Intel core i5- 2410M CPU @ 2.30 GHZ
OS :Windows 7 Home premium SP1 , 64 bit
HDD : TOSHIBA MK6465GSX
RAM : 8GB
Kindly let me know , If you need information from my end, Waiting for your suggestions
Thanks,
Madhu,Pranay, welcome to the forum,
it certainly sounds as though you need a new hard drive Hopefully you have already saved all your important files to other media should the drive suddenly totally stop working.
You can find the support phone numbers on the following site;
Worldwide Support Center phone list - IdeaCentre, IdeaPad and 3000 G, H, K, Q,
S, U, and Y Series s...
For India, 9AM - 9PM Monday to saturday
English and 1800 3002 9929
Hindi 1800 425 9003
Alternate No: 080-39834100
Andy ______________________________________
Please remember to come back and mark the post that you feel solved your question as the solution, it earns the member + points
Did you find a post helpfull? You can thank the member by clicking on the star to the left awarding them Kudos Please add your type, model number and OS to your signature, it helps to help you. Forum Search Option T430 2347-G7U W8 x64, Yoga 10 HD+, Tablet 1838-2BG, T61p 6460-67G W7 x64, T43p 2668-G2G XP, T23 2647-9LG XP, plus a few more. FYI Unsolicited Personal Messages will be ignored.
Deutsche Community Comunidad en Español English Community Русскоязычное Сообщество
PepperonI blog -
Disk problem in MacBook Pro (hardware or corrupted files?)
I am running Mac OS X 10.6.8 on a 15" MBP 2.33 GHz Intel Core 2 Duo with 3 GB RAM (added 1 to the original setup.)
A few months ago I replaced the original 120 GB hard drive, as it was getting full and making my computer slower. The new one is a 350 GB 5400 rpm Western Digital drive. I did this myself, following the instructions in ifixit.com, as I have done it in the past with other machines, including my wife's MBP, that is working fine.
In the first OS install I used migration assistant and recreated the original user exactly as in the old disk. After a couple of months of use the computer started to get slower and presented permission problems that didn't seem serious (used Disk Utility to check). After a while, there was also a report of problems on disk verification, that at one point couldn't be repaired with Disk Utility. I was able to get rid of the problem for a while using Disk Warrior, but at some point the disk problems appeared again and I had to do a new OS install from zero.
This time I formatted the hard drive writing zeros to correct possible physical errors and did a clean install. Used migration assistant to copy only my user's documents and library. After a couple of weeks of running the laptop without problems, I am having again reports of disk errors that Disk Utility can't repair. Disk Warrior can't access the drive and Tech Tool Pro reports 72 bad sectors.
My question is:
Is this definitely a hardware problem that will be solved by replacing the hard drive again, or is it possible that this is being the result of some corrupt files on my user's library (as the problem only appears after a while)?ign wrote:
Is it normal that the drve appears to be OK after an OS install and that the physical problem only appears after a while?
If you zero it, yes. That's exactly what zeroing does, "mapping" the HD so bad sectors/blocks are not used. But if a HD is dying, more bad areas will show up. It's time to replace the HD.
Maybe you are looking for
-
Error while running Program YL_ADJUST_COMMITMENT
Error while running Program YL_ADJUST_COMMITMENT, i think it actually comes from FN8C business operation for single posting w "Message" - No account refernce could be found - Error in update to Accounting - Distribution error -CoCd 601. Please help
-
II'm trying to view ipad content on tv using a composite cable but it doesn't seem to connect. Any help gratefully received
-
Trackpad with buttons from the new E/T/W 450/550 to E/T/W 440/540
Hello, i was looking at the new 550 450 series and saw that Lenovo had returned to the old trackpoint buttons. Also i've notised for the short time i was able to take the quick look that the size of the new trackpad + buttons is the same as the track
-
Inquiry in downgrading OS for Lenovo 3000 G410
First of all... Im a newbie in this community... i just wanted to ask for anyones help... I have downgraded my OS for my Lenovo 3000 G410 from Windows Vista Starter to Windows XP... and I have been seeing this conflict in my device manager... I h
-
ESS Benefit Enrollment - No correct adjustment reasons specified
We are in ECC 60. When testing ESS benefit open enrollment (under Content Admin - Portal Content - Content Provided by SAP - End user content - ESS - Iviews - Benefit and Payment - then either test on 'Enrollment' or 'Flex Bens Enrollment)', we keep