Disk problem again
Hey guys...What does this mean....should I start worring?
I converted some akai files to my desktop then when I tried to move them to my exs drive i noticed that the copying was very slllooowww. So, I ran disk utility that i got the message below...should I start worring?
Thanks
Verifying volume “TIGER”
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Incorrect size for file S&S Grand Low.exs
(It should be 0 instead of 9256)
Incorrect size for file 027 LPFsoft2.exs
(It should be 0 instead of 8592)
Incorrect size for file 029 EQ+LPF MORPH.exs
(It should be 0 instead of 8592)
Incorrect size for file STACCATO MEDIUM.exs
(It should be 0 instead of 11388)
Checking multi-linked files.
Checking Catalog hierarchy.
Checking Extended Attributes file.
Checking volume bitmap.
Checking volume information.
The volume TIGER needs to be repaired.
Error: The underlying task reported failure on exit
1 HFS volume checked
Volume needs repair
Hi Allen,
Yea worry a little, then go straight and boot to another drive / or disk and run disk warrior asap... Sounds like your directory is going south..
and if not rebulit repaired it will just get worse. (and more filepaths become damaged)
DW is a great tool for this and has bailed me out of simular situations many a time..
good luck,
Daniel
G5 Dual2.0 5Gig ram 1TB Logic Pro 7.1.1 Mac OS X (10.4.4) RME FF800, UAD-1, US2400, LA2A, Neve5422, Fatso...
Similar Messages
-
I have an iMac mid 2010. After Disk utilities said the drive was corrupt, I ran the hardware test (extended) 3 times. No problems. I than ran Disk utility again and got 2 messages in red…keys out of order, and ……Volume corrupt, can't be repaired.
I tried to do a system install, but message said…disk can't be changed. Will a complete erase and install fix this ?
Everything is backed-up.There's hardware and software.
Your drive could physically be in good condition but something has caused the file structure to be messed up (it just happens sometimes). The directory that keep track of files is corrupt. Disk Utility can help determine if that is the issue. In some cases it can repair the problem but it cannot do it to a drive that is being used to boot the system while you are doing that. You have to boot from another drive. Some things DU cannot repair and you need to try a stronger utility such as Diskwarrior.
A failing hard drive (one with mechanical issues) can be a cause of file structure issues but this is by no means always the case. Apart from looking at the SMART diagnosis feature of Disk Utility (and smart isn't totally reliable) there often isn't a way to tell if a drive is failing until it suddenly happens, which is why you need to maintain backups.
In your situation it does sound serious and not just minor directory corruption. You can try erasing (formatting) the drive, You may need to do this if it is really corrupt, in which case there could be underlying physical issues. I use old technology but if you have the patience you can try erasing the drive with the security option of writing zeros once (don't do more unless you are going on a 3 week vacation). This makes the drive not simply assume everything is okay by forcing it try every part of the drive by writing data. If something is gong wrong you may find it marks a lot of bad sectors, or flat out refuses to format. Then you know you need a new drive. -
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. -
Mid 2009 MBP Boot and Target Disk problem
Hello all.
I'm trying to help a friend get his Mid 2009 MBP back on its legs. He dropped it at some point and its condition has been deteriorating since. It has finally come to the fact that his computer simply won't boot into OS X. It has Leopard installed on it still.
We decided to try and get his data off of his computer and when we connect with firewire using target disk mode, it can see his hard drive, but it seems every couple minutes, the disk mounts again. After a while, the longest we've had it on (15 minutes) has had 6 copies of his "Macintosh HD" connected to my computer. You can only access data on the latest mounted drive, and if you try to transfer data, the transfer fails when the drive gets re-mounted the next time.
We've run the hardware diagnostics, both the quick and the extended and neither have found problems with anything, so that's why we figured we could just get his data off the computer and then reload Leopard or Snow Leopard onto it.
Any guesses as to what's happening? Any possible solutions?
I was thinking maybe the hard drive cable, but I don't think that would keep multiple "Macintosh HD"s connected to my computer all at once.
Thanks for your time.
Message was edited by: jondyIs a Genius Bar diagnosis free?
My understanding is that the diagnosis is free. Go to "Got a technical question? Step up to the Genius Bar" (http://www.apple.com/retail/geniusbar/) to read more about their services and how to make an appointment.
Of note is:
How should I prepare for my appointment?
First, back up your data. (We’re happy to show you how to back up, but remember we’re not responsible for data loss.)
I don't know how this will actually play out in your situation (i.e. they might give same advice as above, have a different approach, or they might ask to do diagnosis - that would likely answer your question as to if data retrieval is possible / practical - just keep in mind that they are not responsible for data loss).
Given that the MBP was dropped and the problems as stated, I would make an appointment. Would like to hear how it all works out.
Best of luck. -
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 -
Snow Leopard and hard disk problems?
This may just be a coincidence but I and several colleagues have had problems with Macs over the past week.
a) My Macbook Pro lost the date/time and wi-fi settings. Next reboot wi-fi was still lost. Now seems OK again.
b) At times my 24" iMac is running slowly when nothing seems to be hogging resources (eg just copying a 3Gb file to an external hard disk). Time Machine also seems to be taking much longer to backup.
c) Hard disk failed on a Macbook Pro of a colleague
d) iMac 27" seems to be having severe hard disk problems for another colleague - Applecare will be visiting after trying numerous fixes over the phone.
On my machines I have run the Cocktail suite (permissions, scripts and caches) Disk Utility Repair and Techtools Deluxe (no reported problems) but the iMac problems seem to creep back.
It is like a disk caching process (or Spotlight?) is not cleaning up properly and is clagging up the system. Or maybe a hard disk is close to failure but the problem is not severe enough to show up in diagnostics? In any case I am diligent about backing up at the moment!Or maybe a hard disk is close to failure but the problem is not severe enough to show up in diagnostics?
Common symptoms of a dying hard drive
Hard drive is making a clicking, whirring, grinding, ping pong ball noise or any other type of unusal noises.
Hard drive is not spinning.
Computer is not recognizing the hard drive.
Sluggish loading of applications.
System freezes and hangs.
An interesting site - Hard Drive Sounds by drive manufacturer.
How much hard drive space do you have left?
Disk Inventory X
OmniDiskSweeper
WhatSize
SpaceControl
Disconnect all peripherals from your computer. Boot from your install disc & run _*Repair Disk*_ from the utility menu. To use the Install Mac OS X disc, insert the disc, and restart your computer while holding down the C key as it starts up.
Select your language.
Once on the desktop, select Utility in the menu bar.
Select *Disk Utility.*
Select the disk or volume in the list of disks and volumes, and then click *First Aid.*
Click _*Repair Disk.*_
Restart your computer when done.
Repair permissions after you reach the desktop-http://docs.info.apple.com/article.html?artnum=25751 -
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”. -
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. -
I have installed Windows 7 64 bit version in my MacBook Pro Retina(13") late 2013 model . It was working fine from last 8 months but recently popup window showing as "Windows detected a hard disk problem" once login. Please check the following image.
I have contacted Apple Support team. They have tested the hard disk while booting from Mac OS and all the reports showing as hard disk is fine. Then I thought might be it was some virus and removed the Bootcamp partition and re-installed Windows 7 Operating System. But once updated Windows 7 with latest updates. This message showing again.
Would you please help me out to fix this issue. Anybody faced similar issue?No I think that all drive are really on failure
I've boot with an ubuntu livecd and smartmontools see also the failure.
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x001a 200 200 000 Old_age Always - 0
5 Reallocated_Sector_Ct 0x0033 100 100 000 Pre-fail Always - 0
9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 1872
12 Power_Cycle_Count 0x0032 099 099 000 Old_age Always - 762
169 Unknown_Attribute 0x0013 253 253 010 Pre-fail Always - 4003597393408
173 Unknown_Attribute 0x0036 100 100 100 Old_age Always FAILING_NOW 12124890467160
174 Unknown_Attribute 0x0022 099 099 000 Old_age Always - 7469954
175 Program_Fail_Count_Chip 0x0022 099 099 000 Old_age Always - 4989854
192 Power-Off_Retract_Count 0x0012 099 099 000 Old_age Always - 31
194 Temperature_Celsius 0x0022 064 064 000 Old_age Always - 36 (Min/Max 11/75)
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0
199 UDMA_CRC_Error_Count 0x001a 200 199 000 Old_age Always - 0
240 Unknown_SSD_Attribute 0x0022 100 100 000 Old_age Always - 0
When I use the Mac disk tools from the startup menu, it see also the problem.
Now the big question is : Why I've this type of issue with 2 MBA and 1 Macbook pro 15".
Their configurations are the same : windows 7 with truecrypt.
Maybe Windows drastically reduces the lifetime of the Apple SSD drive.
The 3 Mac are used for less than 6 month !!!! -
Will TM-restore just recreate permission and disk problems I was having?
My tale of woe, that of course happens the day before I need by machine for a meeting:
Last night, when I ran check permissions, and then repair permissions on my MacBook Pro, I got the message that permissions could not be repaired. After this, I made my first and only Time Machine backup.
This morning, I could not start-up my MacBook Pro. I just got a blue-gray screen containing a spinning wheel and a progress bar that got to maybe 10% (the progress bar was not numbered) before shutting down. I tried a few more times, but the same thing happened.
I was able to run Verify Disk using the Snow Leopard install disks, but when I ran Repair Disk, it could not repair, and indicated that I must reinstall the OS.
However, I was able to use a Firewire cable and Target Disk mode to get some recent files off of the MBP, which suggests to me that the hard drive is okay, and it's just something with permissions, and/or other disk errors.
I'm trying to figure out how I can restore my system (including settings) without restoring the same permissions errors and disk errors that seemed to have caused this problem in the first place.
My time machine backup was made AFTER the permissions problems. Does this mean that if I do a clean install of Snow Leopard, and then try to restore my system from the Time Machine back-up, that I will end up restoring those permissions errors and disk errors that I had before?
(I also have an older bootable clone (made with Carbon Copy Cloner) of my hard drive from a couple of months ago, but I assume it would be the same issue - that it would recreate the old errors.)
Any help or suggestions would be much-appreciated!Mike_Rsch wrote:
Hi, and welcome to the forums.
I was able to run Verify Disk using the Snow Leopard install disks, but when I ran Repair Disk, it could not repair, and indicated that I must reinstall the OS.
I'm trying to figure out how I can restore my system (including settings) without restoring the same permissions errors and disk errors that seemed to have caused this problem in the first place.
My time machine backup was made AFTER the permissions problems. Does this mean that if I do a clean install of Snow Leopard, and then try to restore my system from the Time Machine back-up, that I will end up restoring those permissions errors and disk errors that I had before?
No. Permissions aren't the problem, some sort of directory corruption is. And since Time Machine backups are done file-by-file, rather than disk-sector-by-disc-sector, the exact condition wasn't copied. But if the problem prevented something from getting backed-up, there might be missing or incomplete items.
Your best bet is to boot up from your Install disc again, select Disk Utility again, but this time use it to reformat your internal HD. See #1, especially the yellow box, in Formatting, Partitioning, Verifying, and Repairing Disks. That will only take a few moments.
Then quit Disk Utility, return to the Installer, and install OSX. When your Mac restarts, use +Setup Assistant+ to transfer everything from your backups, per #19 in Time Machine - Frequently Asked Questions (or use the link in *User Tips* at the top of this forum). That will take longer, of course, depending on how much data you have.
When your Mac starts up again, download and install the 10.6.4 "combo" update. Info and download available at: http://support.apple.com/kb/DL1048 Be sure to do a +Repair Permissions+ afterwards.
Once this is sorted out, continue making regular backups! You might want to review the Time Machine Tutorial and perhaps browse the rest of the FAQ. -
[MBA original] startup and disk problems
My old faithful Air has started to have some serious problems.
A couple of months ago, it started to behave sluggishly, beachballing in all applications, and then when I tried to restart, it wouldn't get past the logo/catherine wheel screen. I could get it to boot into Lion Recovery, where disk utility said that the disk could not be repaired. At this point I zeroed the disk (level one secure erase), restored from my Time Machine backup, and was up and running again - for a couple of days. Then the same symptoms recurred again, with the same results.
I began to suspect a failing hard drive, and had it replaced with a new one.
The Air worked fine since then, until a couple of days ago, when the sluggishness and beachballing recurred, followed by failure to start up. Again, I booted into Lion recovery, and ran Disk Utility again. This time it found many many problems with missing catalog entries, invalid nodes etc, and told me the disk could not be repaired. Once again I erased it (the new disk this time) and restored from a back. Last night, the symptoms recurred again. This time, though, when I got into Disk Repair, it found a similar list of errors, and it claimed to have repaired the disk (green status), but still it would not restart. I tried starting in safe mode, and the progress bar got about 1/3 of the way across, then disappeared and the machine would not start up. I tried starting with the D key held down but couldn't get hardware diagnostics running.
I'm beginning to suspect sofware causing disk issues rather than the disk itself, so I tried performing a clean install of Lion from Recovery. The machine started up OK after the clean install, (with my user account and files still intact, which suprised me - I was expecting to have to use Migration Assistant to get them back). At this point, I plugged in my Western Digital USB drive into the Air and copied all my documents and files onto it, in case I need to get at them without using the Time Machine backup. Then I shut the machine down.
This morning it has started up OK again, and I'm typing this on it right now.
Does this sound familiar to anyone? Any advice if you managed to fix it permamently?
Is it possible to run the hardware diagnostic from the original install disks for the Air system software? _Should_ I be able to get to hardware diagnostics by holding down D on startup on this model? If I've got Lion up to date installed, can I get to the internet version of hardware diagnostics via Lion Recovery, like on newer Airs?
If it happens again, my last ditch effort is going to be zeroing the disk, doing a clean Lion install on the erased disk, then just copying back my documents and reinstalling key applications (Office, Photoshop) from the original install disks/images. Does that sound like a sensible approach?
Otherwise, I'll have to try and talk my boss into letting me get a new one!
best regards,
MattIf DU reports errors it cannot repair you will
need to use a utility like Tech Tool Pro or Disk
Warrior
DU can't repair and I got these errors:
"Invalid B-tree node size"
"Error: The underlying task reported failure on exit (-9972)"
DU didn't show the SMART status. But I saw it in Disk Warrior and it said the disk was ok.
I tried Disk Warrior and it's just be stuck at the same place. This never goes away and so I just killed it:
"Rebuilding directory ...
Step 5: Locating directory data ..."
In DU when I highlight disk0s3, I get this in the lower left hand corner:
"Mount Point: not mounted"
So maybe I just need to re-mount disk0s3?
Anymore ideas, guys? Thanks. -
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. -
There seem to be a lot of threads going on about connectivity problems regarding disks connected to Airport Extreme base stations. This http://discussions.apple.com/thread.jspa?threadID=1155412 is probably the biggest. Since this really is a large issue, I thought I'll post a report of my findings.
Today was the first time I encountered the fact that I couldn't connect from my iMac G5 to my Airport Disk anymore , Finder gave me the following message:
+*Connection failed*+
+The server may not exist or it is not operational at this time. Check the server name or IP address and your network connection and try again.+
I went to my MacBook pro (waking from sleep) and it gave me the same message.
Restarting the Airport Extreme brought my disk back on my Macs.
I simulated this scenario, to see where it was failing:
*Case 1: let macbook pro sleep*
1. Fresh reboot of Airport
2. Mount disk on all macs and one windows xp machine
3. Put MacBook Pro to sleep (disk still working on other mac)
4. Wake MacBook Pro
5. Everything still works on all machines
*Case 2: let imac sleep*
1. Fresh reboot of Airport
2. Mount disk on all macs
3. Put iMac G5 to sleep
4. Wake up iMac G5
5. Disk doesn't work on Macs (AFP), but still works on windows machine (SMB)
In last scenario it looks like the AFP service on the Airport Extreme Base Station crashed. You can manually check this by doing this in Finder menu: *Go -> Connect to server*.
And type this:
afp://ip.of.your.basestation/ (you can find the ip of your basestation via airport utility)
You will get an "Connection failed", that means the server is not responding. At this point you can still connect to the Airport Disk via the SMB protocol. In the Finder menu: *Go -> Connect to server*
And type this:
smb://ip.of.your.basestation/
Use your username and password and you'll be able to connect to the airport disk.
Another way to check if the AFP service is still running on the airport, is to use an portscanner. You can use the one provided by apple in Network Utility. I used nmap.
After a fresh restart the following ports were opened:
21/tcp open ftp
53/tcp open domain
139/tcp open netbios-ssn
445/tcp open microsoft-ds
*548/tcp open afpovertcp*
554/tcp open rtsp
7070/tcp open realserver
10000/tcp open snet-sensor-mgmt
After waking the iMac from sleep the following ports were opened:
21/tcp open ftp
53/tcp open domain
139/tcp open netbios-ssn
445/tcp open microsoft-ds
554/tcp open rtsp
7070/tcp open realserver
10000/tcp open snet-sensor-mgmt
You can see that there is no AFP server (afpovertcp) listening on the Airport anymore.
I have the following setup:
MacBook Pro Core 2 Duo 2,33 Ghz
Mac OS X 10.5.1 (fresh install)
iMac G5 2,1Ghz
Mac OS X 10.5.1 (upgraded from 10.4.11)
Airport Extreme Basestation (fast ethernet)
- 802.11n (802.11b/g compatible)
- wpa2 personal
- file sharing with accounts
- no guest access allowed
Currently the only workaround I found, is by using the SMB protocol. (Finder -> Go -> Connect to server). This works on all machines, even after waking from sleep.
The problem as far as I can see is twofold:
1. AFP service on Airport Extreme Basestation is buggy, it justs crashes after it recieves info it doesn't expect.
2. Leopard sends stuff It shouldn't send.
Tiger never had this problem.My AEBS network, internet connection and Airport Disk are all (finally) holding connections. It's been about a day now, so I guess it's going to be ok next week.
Here's some of my story/thoughts in case this helps anyone else who is still struggling with the madness:
First, I bought a TC and connected a USB disk. This was a cacophony of dropped connections, followed by the messages Frodo posted, lost internet connections, etc. A lot of resets, channel changes, restarts, two reformatting of the Airport Disk (via hardwire connection to one of my computers and then reconnecting it to the AEBS), etc. etc. later, I returned the TC for an exchange and bought a simple AEBS and connected that to the Airport Disk.
Same sort of problems again, but this time I don't usually lose my internet or network connection. New problems enter - glacial speed on some/most computers and ok on others. The Airport Disk keeps disappearing and can't reconnect. More restarts.
This is what seems to be working now:
I have every single client computer set to never sleep and that includes turning off the "Put HD to sleep when possible" button. I also set my WPA2 Personal timeout to 500 days. The default is 1 hr. Also, I took the Airport Disk down and connected it to a computer and ran Disk Utility. Found a header problem and fixed it. Followed that with Disk Warrior. More problems, this time an assortment. DW fixed those. Then reconnected the Airport Disk to the AEBS. Now it all works.
I did a bit of reading on WPA2 on Wikipedia and it turns out this scheme sends out some sort of key to the client computers and does it dynamically as the network is up. (This might explain the "unexpected ACL" message I was getting in Disk Utility when checking client computers - there are 3 of them. I assume these are an Access Control List generated by my AEBS; I certainly didn't put them there). Anyway, I got to wondering if the AEBS is trying to generate a new key for the 'group' that hat connected to it and since one or more of the 'group' has nodded off, it is unable to do so and this results in the lost connection followed by 'not operational' message. Maybe it thinks it was being hacked?
Anyway, with both those settings my network is stable, internet is stable and the Airport Disk has been mounted on various desktops now since yesterday. I'll worry about faster speeds later. None o my computers will sleep until an update is released. They don't mind. I have no inclination to spend any more hours fighting with this thing.
FYI, I have eight 10.5.2 computers and three 10.4.11. They are all happy this morning - although for a time yesterday the 10.4.11 client computers were real slow. I shut those down for a while last evening and concurrently changed to Channel 9. I'm using the 802.11n (b/g compatible) setting and I know that is in the 2.4 frequency, which is pretty crowded these days. I think the higher channels are probably less crowded. Anyway, the 10.4.11 computers were ok when restarted last evening and are still ok this morning. All connections held. Ditto for the 10.5.2 clients.
I don't know where the faults came from with the Airport Disk (fixed as described above yesterday), but I do know I did not "Disconnect All Users" in Airport Utility before resetting/restarting the AEBS while the Airport Disk was connected and (perhaps) still shared despite the dropped connection messages. I'm not even sure that disconnect button was available since I never looked.
Wheew!
Not sure what I'm going to do when the replacement TC arrives. It's a heckuv'n idea and I hate to walk away without at least another trip into the twilight zone. I've lost files before and would have been SOOoooo happy to be able to fish back in time to find them. -
Windows Detected a hard disk problem Toshiba Satellite L505-S5988
It has been about 2 months since I had my new laptop and first I coudnt get the flash cards to work so I finally fixed that and now everytime I start windows an error message comes up and keeps coming up every 10 minutes saying:
Windows detected a hard disk problem
Back up your files immediately to prevent information loss, then contact computer manufacturer to determine if you need to repair or replace the disk.
-> Start the back u process
-> Ask me again later
Show details
Which disk is failing?
The following hard disk are reporting failure:
Disk Name: Toshiba MK3263GSX
Volume: C:\
Please tell me how I can fix this because I called Toshiba support and the guy couldnt even figure out the drivers name for flash card.
Toshiba Satellite L505-S5988
Thanksyour hard drive is failing. you need to do what it says. back up everything and then either call toshiba to have it replaced under warranty or buy a new one and change it yourself. this is where all of your info and files are saved so if it fails without you backing it up you lose everything.
-civicman4-
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Post all info about your laptop and version of windows. We are working on it but still do not have the powers to read your mind. -
Im my lap has hard disk problem,how to resolve the problem,pls help me...
Hello,
I have hp pavilion dv4 lap,in this lap has some hard disk problem,when i am turn on the lap that screen shows this message "The smart hard disk check has detected an imminent failure.To ensure not data loss,please backup the content immediately and run the hard disk test in system diagnostics".
After that i was diagnostics the system but no changes in the lap,,again again lap shows hard disk error(301).
Then i am chosen the enter option to start up the lap it take long time for openning the windows,after enter the windows that also shows about the hard disk error in within few minitues,
What can i do?
This lap bought at 12-oct-2012 from malasiya,now im in tamil nadu,how to solve the problem please help me.Hello srhk. Thank you for posting on the HP Forums.
I understand the hard disk is experiencing issues. Error 301 indicates the hard disk possesses a hardware defect. I would contact HP Phone Support for assistance, or purchase an equivalent hard disk.
If you choose to contact HP, their options will be based on the warranty status of the computer. If you do not have this information, you can locate it at this website: http://h20566.www2.hp.com/portal/site/hpsc/public/wc/home?ac.admitted=1384280905804.876444892.199480...
You can utilize this website to learn how to contact HP appropriately, based on your region: http://www8.hp.com/us/en/contact-hp/ww-contact-us.html
Please let me know if you have any other questions or concerns.
Mario
I worked on behalf of HP.
Maybe you are looking for
-
Error connecting applet with oracle database
hi all, here i m running the following code . it executes the following query "Select * from emp"; the number in the text filed decides the column number to be displayed. import java.awt.*; import java.applet.*; import java.sql.*; /*<applet code=proj
-
Trouble with a Dell Printer on a network with PCs.
I've searched the forum and found only trouble with people getting their files to print on a mac, but I can print, only it's terrible quality while the PCs are printing out high-quality. It's a Dell 5100cn, and I've installed the updated driver from
-
I can't get adobe bridge to open on my iMac... CS6 works perfect. Any ideas of what I need to do?
I can't get adobe bridge to open on my iMac... CS6 works perfect. Any ideas of what I need to do? Thanks Judy
-
How do I link a report to an external style sheet?
-
Best way to set up homesharing via airport express and NAS
Hi, I've just bought an Airport express and was wondering what the best way to set it up would be so that I can play music stored on my NAS, controlled by my iphone / ipad. I have itunes match as well, and don't want my phone to be streaming the mus