Air Disk Problems: either miniStack v2.5 or Western Digital's 1.0TB Green?

Anyone still having Air Disk problems with either the miniStack 2.5 or the WD10EADS?
Using it as a Air Disk/hub with AEBSn (firmware 7.4.2) connecting to MBP1.83 running 10.4.10. It worked fine in this configuration for almost 2 months. The drive does not appear in finder or disk utility even when connected directly through USB or Firewire, so I'm sending the ministack back to OWC. I was just checking here to make sure that it wasn't something on Apple's end before I head to the local UPS store.

Sorry, I'm using 10.4.11

Similar Messages

Problems with the WD2GO app from Western Digital

I have a Western Digital Mybooklive and have downloaded the WDPhoto and WD2Go apps.
The WDPhto app works perfectly, however the WD2Go app doesnt.
I have been in discusson with WD and they have put forward numerous suggestions but I have found nothing that works.
They belive the proble is with the Ipad, although I am not convinced.
When I launch the app, I get a Mybooklive icon to sekect.
After selecting the mybooklive I can see all my public shares.
If I click on one I see the next level in the folder structure but after this when I click on a folder the Ipad gives the busy circle and eventaually I get the message
"Device Offline".
If I the come out of the app and go back in I get the "Device offline " message when I click on the Mybooklive icon.
I can get access to the Mybooklive from my andcroid phone both within my own wifi neetwork and using 3G.
So I know that port forwarding on the Mybooklive is working properly as the android phone and router and mybooklive all talk to each other.
Has anyone got a reason why the Ipad has these issues.

I had exactely the same problems you have described! No useful help from WD assistance but the problem is quite well known between the users and not so rare.
I have found the solution of my problems following the suggestions you can find here http://community.wd.com/t5/WD-Mobile-Apps/WD-2Go-App-iPad-amp-iPhone/m-p/538735# M2125
Now everything is OK!
Bye

Air disk problems.

Hello, i just bought an airport extreme to use on my home network, everything is working fine networking wise... but i connect my 500 gb la cie Drive ( usb/fw etc..) and the airport says it needs repair so i back it up to my computer, format/repair it ( using hsfs) and put all the data back in, then i plug it into my AEBS. Now no problems are detected, the drive is detected properly, with the capacity and used sized beeing correct. But when i try to open the drive on finder, it doesnt list anything on it
its kind of stuck reading it.. ( spinner at the bottom right of the window).. Could this be because of the format? should this be on FAT 32?

Well still looking for solutions, and have seen that this is a rather usual thing. and that it needs to be fixed. Well here is to hoping that MWSF2008 will bring us a solution..

HT3275 message: "Your Time Machine backup disk can't be found." Mountain Lion. Western Digital "MY Book" "Home edition"

Intalled Mountain Lion. Now get message: "Time machine backup disk can't be found. Using Western Digital "My Book" "Home Edition"

Wow, I feel really stupid. I spent a couple of days trying to troubleshoot this problem.
1. Open TM prefs.
2. Click "Select Disk..."
3. Select "None" and apply changes.
4. Click "Select Disk..." Select your disk and apply changes.
*5. When the password prompt appears, MAKE SURE THE NAME IS THE NAME OF THE AIRPORT BASESTATION, and not the name of your Mac.
6. Run a backup.

Air Disk disconnection

Hi everyone,
I've just bought a Airport Extreme N, and I already have a problem with AirDisk.
I can see the shares on the network, mount them, but none can remain mounted more than a few minutes.
The logs just say: "Disk sd0 (...) plugged in" oi "Disk sd0 (...) unlugged".
When I plug the usb drive right to my iBook, everything is just... well... working as expected.
The hard drive has been formated in HFS+, its usb enclosure is a generic one, but brand new also.
Thanks in advance,
Xavier Cambar

I have the same problem I think. My air disk is there for a little bit then disappears (if I'm reading your post correctly). The problem with mine is my drive going to sleep. Network drives can not go to sleep. If they do your AEBS will not be able to wake it up the same way pluging it directly into your computer would. It will simply disappear (or lock up your finder for a nice amount of time). Good luck finding a way to stop your HD from sleeping. I've been working on it for 2 weeks now and can not find a way to do it. If anyone has any suggestions please let me know. but in the meantime I either have to get a new enclosure. Or wait for Apple to solve it.

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.

Hard Disk Problems

I've had my laptop for about a year and a half now, with no problems. Sometime along the way I lost the cover to my hard drive on the back, and a few months ago the laptop managed to fall off my coffee table - onto a soft coat - and the hard drive popped out and now the laptop doesn't work at all. It starts, and runs the regular booting stuff, but then it gets to a certain point and gets stuck. I've had some computer gurus in the family take a look at it and they just figure that my hard drive is broken somewhere. Is this something that I can resolve with a simple purchase of a new something, or do I need to take it somewhere to get it repaired, or do I just need to forget the whole thing and get a new one?
Here's all the details, in case someone needs it. The actual laptop is a Satellite L305-S5921. I have it on Windows XP, it broke before Windows 7 came out. The laptop boots without a problem until it gets to the black screen with white text, where it says "Intel UNDI, blah blah, Product covered by the following patents, blah blah" and then it says
"Realtek PCI Express Fast Ethernet Controller Series v1.15 (090224)
PXE-E61: Media test failure, check cable
PXE-M0F: Exiting PXE ROM.
No bootable device -- insert boot disk and press any key"
As far as I can tell, the hard drive falling out is the only thing that would have caused this, so I can't imagine that it would have been anything else. As far as I can tell, the hard drive is sitting in there as securely as it has been at every other point, and nothing I can wiggle around or anything helps at all. I don't know if I need a new hard drive, or just some recovery software for something. Any helpful advice would be appreciated. Thanks.

Sounds like either the hard drive itself is damaged or the connector between the motherboard and the hard drive is damaged. The only way to know or sure would be to replace the hard drive. It should be fairly simple to do this, but unless you get the hard drive cover replaced there is no guarantee how long it will last. You can pick up a hard drive online from Newegg, ZipZoomFly, or any number of other outlets. I recommend a Western Digital Scorpio Blue due to it's combination of reasonable price, good performance, and reliability.
Here are two good sources for Toshiba parts to order the drive cover from.
National Parts Depot
Spare Parts Warehouse
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.

[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,
Matt

If 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.

Macbook Retina Disk Problems?

I received a MacBook as a gift a while ago. It was used before it was given to me and using everymac I determined it to be the 2012 15 inch core i7 MacBookPro retina.
Recently my Windows OS on macbook, installed a la bootcamp, started crashing (no blue screen, just hang and reset). I tried re-installing Windows (7 and 8). When I installed Win 8 I had the same problem. Then while installing Win 7, the installer gave me the BSOD (page fault on non-page something error). Then I booted back into Mavericks and it is exhibiting the same behavior. I took it to a computer guru pal of mine and he told me it is probably a fault with the SSD. I have heard of SSD failures on the MacBook Air, but not on the Retina.
What do you think it is and what do you suggest? Is there a tool I can use to detect disk problems or something else to localize the failed component? I do not want to spend $200 on a replacement SSD to find out the RAM is the problem. Also I think the warranty has probably expired.

I entered the internet recovery mode after boot, and after it loaded up (the progress bar was filled), I got a message saying my computer restarted because of an error ... press a key to continue (written in a couple of other languages in a gray background). Then I pressed a key, it restarted, showed the classic Apple logo on the gray background, and shortly after the Apple logo turns into a no entry logo and its frozen.
The fact that the progress bar was able to fill before seeing this error message is peculiar. Any more ideas? If the entire SSD is wrecked, do I have to ship the Macbook in for service or can I replace the SSD even though there wont be a recovery partition. If I put in a new SSD, can I install Windows 7 or 8 (I have original ISO images) over a USB stick (no optical drive on this model)?

Suddenly, my wireless connection (including Air Disk) is acting all screwy.

My airport express sometimes shows three of four airport bars and my connection becomes very intermittent. When the signal is full strnegth, everything seems to work, with the exception of my Air Disk. It simply won't mount anymore. I have never had these problems until the most recent updates. However, under a wired cnnection, everything works fine.
Is there some sort of a bug going on with all the latest Apple-latest wireless and airport drivers? This is pretty annoying.

I just had the same problem. Downgrading the airport firmware from 7.2 to 7.1 fixed it for me.
Message was edited by: J Moore

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
Thanks

your 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.

Protecting Air Disk

Loving my new AEBSn with AirDisk, and figuring out all the capabilities. But one problem I encountered was this:
The data on my AirDisk feels very insecure. When I delete an item, it gives a warning message and then deletes it forever! Is there any way to set up protections on my disk so that I can add to the disk, use files on the disk, but have extra protection against accidental deletion of files?

With a Mirrored RAID, if you delete a file, it is deleted from both disks. So that wouldn't solve this particular issue.
Perhaps a solution would be attaching two disks to the AEBs, then creating a special folder on the computer you are using. You could write an applescript that copies anything added to that folder to both drives simultaneously, then removes it from that folder. You could then use the Mac OS folder action feature to make sure the script ran whenever a file was saved there.
Not super convenient, but it does save the file redundantly. When you open a file from an Air Disk you would then have to remember to do a 'Save As' to save it to the scripted folder.

Major External USB Disk problem

I noticed today that an external drive I have had connected to my MacBook Pro for several months seemed to have no data on it. While showing no files or folders in the Finder view, it showed that only 222GB or so was still free though the drive is a 500GB unit. In Disk Utility it does show the additiona 243GB or so as "Used".
I have tried running Verify Disk and got a message saying
"First Aid Failed / Disk Utility stopped verifying "VMG 001" because the following error was encountered / File System verify or repair failed"
I then tried Repair Disk and got this message:
"Verify and Repair volume "VMG 001" / The disk "VMG 001" could not be unmounted"
I then tried Erasing the drive (to restore from my Time Machine backup on a Time Capsule) but I can't do that either. Finally, when I try to eject the drive to unplug it I get a message saying it could not be ejected and I should "Try quitting applications and try again"
Neddless to say that I've tried that and it still won't eject.
Do I have a virus, a major disk problem or a combination of the two. ANd is there a way to recover the drive or am I going to have to get another drive. If I do, and I give it the sam volume name will I be able to recover my data with Time Machine?
Thanks for any help you can offer.
- Vikas

One possibility is that if you regularly drag lareg numbers of files to it, Spotlight is constantly trying to catch up with what you deleted and what you brought over.
I drag 10GB to a LaCie once or twice a month and it does take a few hours to stop rattling.

IBook does not see Air Disk on AirPort Extreme

We have a few macs in my house (G5 desktop, MBP CD2, and an iBook G4). Both the G5 and the MBP see the Air Disk connect to the AE network but the iBook doesn't. iBook is running 10.3.9 and I use the "go" menu to connect to the server (IP address for the AE basestation). It worked last night with a different drive that I was testing. I purchased a new enclosure (Newer Tech's miniStack). The HD is a WD 250 GB. The AE basestation is set up to connect to the disk via the basestation's password.
Thanks.
Tom

To access the disk attached to the AirPort Extreme base station (AEBS) your iBook must be upgraded to OS 10.4.8 or better. See AirPort Extreme (802.11n) - Technical Specifications.

Has your Macbook Air overheating problems been solved?

Hi All,
Has there been a solution to the Macbook Air overheating problem for you?
I'm considering selling my MBA but want to see first if there has been any new updates on this issue.
I have a Macbook Air with the specifications as follows:
Model: MacBook Air 1.6GHz Intel Core 2 Duo
Production year: 2008
Production week: 15 (April)
OS X Version 10.5.7
Have had the computer for about a year now and it has been constantly overheating and becoming more or less unusable when doing so. Have been hoping upgrades to the software would solve this eventually but that does not seem to have happened.
As I'm writing this room temperature is about 20 degrees celcius. Laptop sits on a table with power cable plugged in. Not running any external screen. There is no video streaming or music playing. Only the Firefox browser and a few more idle apps are active such as Mail and Skype (in the background). Even under these conditions the fan is currently running loud at 6100rpm and the Macbook Air is very hot underneath.
CPU temperature is currently 54 degrees Celsius. Both cores seem to be active.
Now, as an experiment I will head over to YouTube to watch a video and open up Microsoft Word in the background, a perfectly normal usage for a computer this new. This is what happens:
The computer starts to become painfully slow. After for example clicking an item in the browser there is a 1-3 second delay before the click actually becomes effective. It's now so hot underneath that I would not want to keep it in my lap. It is hard to use the mouse pointer properly as it does not update in realtime, I have to assume where it will land based on my movements. When scrolling, the spinning wheel icon becomes active. Everything is now happening in slow motion.
Video is lagging heavily. I can only see probably 1 out of every 10 frames or less of the video. All applications running are very slow. CPU temperature is now 64 degrees celsius. Fan is at 6200. Computer is now unusable for me. When I scroll a page in the browser it takes about 2-3 seconds before anything happens. Changing tabs takes 5-6 seconds after I click them. I will have to shut it down before re-starting and resuming work. When room temperature is even higher on a hot day needless to say everything gets a lot worse quicker.
Is this normal for Macbook Air's? If that is the case they are more or less unusable for most types of normal 2009 year usage (video, audio, browsing, office work etc).
What solutions have you found? Coolbook? Software/Firmware updates? Hardware changes? Please let me know if you have been able to make your MBA not overheat under normal usage.

Hi Everybody,
Thanks for your replies to start with.
I have tried to install Coolbook now and has it running. When using 'throttling' and letting it change CPU speeds (I think..) the problem still remains. When watching a video or other demanding task the temperature goes way up. Running a CPUTest (small or big) gets CPU temperatures of up to 84-85 C. Fan of course at 6200rpm all the time.
Right now, I have Coolbook set to 800Mhz and 0.9V. Apps running are Firefox, Skype, Mail and iTunes with no audio playing. CPU temperature at 56 c and fan speed (as usual) at 6200rpm. I can use the computer now. It is still lagging and not very fast at all. Sometimes text appear 1-2 seconds after I have written it on the keyboard.
So Coolbook has made a difference for me, but only when putting the CPU speed down to 800MHz. I wouldn't call reducing the CPU speed to half a 'solution' though and will not keep that as a long term solution. Reducing voltages for higher CPU-speeds 0.9875V for 1600MHz does not work, it still heats up massively.
Have used the MBA for the whole day today and can't recall a single time the fan has not been around 6200rpm except right after boot.
Thanks for the tips on upgrading to 10.5.8. I will try that right away and let you know how it works out.
Have also considered buying some cooling device but just as you say that feels like a bit of a last thing to resort to.
I'm surprised Apple hasn't responded stronger to this. Had this happened in the car industry we would have seen thousands of cars being sent back to the garage to be fixed.
If this only has to do with some specific production weeks then the right thing to do would be for Apple to let those people have their computers either fixed or replaced.

Air Disk Problems: either miniStack v2.5 or Western Digital's 1.0TB Green?

Similar Messages

Maybe you are looking for