Disk Problem please ans
Hey, i have a Nombad Jukebox Zen Xtra.. and it stopped working. when i tried reformating it, it says the theres a problem with the disc.... what do i have to do?
thx
You can try the advice here in the Zen FAQ at Nomadness.net at your OWN RISK. If you don't want to try this or are under warranty then contact Creative Support.
If you aren't under warranty you can contact Creative Support to see if they will repair it. If you want to try repairing it yourself, taking the risk the hard disk is at fault, then you can follow Rudi Cheow's excellent guide. There's also a thread here at the Zen Nomadness.net forum on compatible dri'ves, and the last page of Rudi's guide also has information on this.
Similar Messages
-
I have an ipad3(wifi +cellular). Now i want to upgrade my iOS5.1 to ios 7. But download speed in our country is too slow(100kbps). It can be disconnected anytime. Is there any problem if net connection get disconnected while upgrading ios? Please ans me.
haha, so now i'm thinking. I'm learning the terminal as fast as i can but there are several lines of codes and commands in there that throws up red flags to me that i don't fully understand. It just looks fishy too me. It would be highly appreciated if someone could just check this out just to tell me that i don't need to worry about it. Or point me in the right direction. I just feel un easy about this. ha.
-
Windows - No Disk Error - Please help!
Windows - No Disk Error - Please help!
Hi,
I have the following set up:
* Lenovo T-61p
* Windows XP Pro, SP 3
* HP Photosmart 8250 printer (with nothing plugged into the various card readers, and USB slot in the printer)
I am getting the following error:
Windows - No Disk
Exception Processing Message 0xc0000013 Parameters 0x75CE023C
0x84C40C84 0x75CE023C
I have done a lof experimenting and thru process of elimination, and believe I have determined that this only happens when the HP Photosmart 8250 printer is plugged in to the USB slot of the computer.
I can stop it from happening by safely removing hardware, and removing the drive that the 8250 creates on your computer when you plug it in. In my case, this is drive E. I'm guessing if there was something in the the various card readers, and USB slot in the printer, that's what those would be, but I don't those use those functions of the printer.
I understand there is more at work than simply the printer, because I did not used to get this error, so some software changed as well, that is scanning all ports, and finding a drive that has no disk, and producing the error.
A simple google search finds a lot people all over the world having this problem, and are solving it in different ways, because the suspected source is different: Norton, HP, etc.
I have tried everything I have read, and the only thing that works was my own idea, of manually safely removing the drive the printer creates each time I plug in the printer.
Anyone every any better, more permanent solutions? Or know what the real root of the problem is? What is scanning all the drives and being showing an error message because it found an empty drive?
Thanks and Happy Holidays/New Year!I've been getting the same error on my 4G nano for the past week. I've had my nano for about a month and the first few weeks were fine. Tried it on 2 different computers (Vista and XP) and same problem. Tried it on a 3rd (XP) and it started ok. Problem started coming back after a day.
I was able to find a quick fix though. I noticed that sometimes the message says something like "iexplore.exe... no disk..." even if I don't even use IE. What I do is end iexplore.exe on task manager before running iTunes and syncing my nano. I don't get the error whenever I do this, but one drawback is that the contents of my nano suddenly pops up in a window - even when disk use is not enabled.
I've reset/restored my nano dozens and dozens of times to make sure it's clean. Leads me to believe it's a driver issue. Either that or I have a friggin malware problem I can't seem to find.
I'll be posting updates every now and then. I'm no expert so I'm hoping an Apple expert also steps in to give some input. -
System freezes due to hard disk problems only on Linux (not windows)
Intro/context:
Recently i've bought (about 2 months) a new laptop, a Lenovo G50-70, which came with Windows 8.1. As i had no interest on that OS, i formatted the disk and installed only Arch Linux. During that time i experienced system freezes which i had no idea why they were happening. As time went by, i found disk errors on system logs related to hard drive. I searched those errors and almost everything i found was that my hard drive had problems, so i decided to use my warranty. But first, i installed the original OS back again. And after using it a couple of weeks, i didn't experiencie any problem with my hard drive (on Linux it was really frequent). Now i've installed Arch Linux back, along with original Windows 8.1, having dual boot. There is no disk problem when using Windows, but when on Arch, i have the same errors and problems i used to have. So i assume it may be related to kernel or some confniguration issue.
I also haven't noticed any relation between system freezes and system use. I mean, it can happen either under light or heavy use.
tl dr: system freezes randomly for some minutes when using linux due to hard drive problems. The problem doesn't happen on windows.
What i've done so far:
The first period i was on Arch, i run smart (long and short), fsck, and hdparm tests. And nothing (no errors). Searched for bad blocks, and nothing. When back on windows, i also run tests on hdd and found no problems, except some sector reallocation not-that-nice indicators. These problems occured at the end of the first arch installation period. But still i currently experience no problem on windows.
I've also tried setting libata: noncq, 3.0G, noacpi, noapic kernel parameters, and had no result.
Changed BIOS setting from AHCI to Legacy, and no result. Also updated BIOS and no result.
I found no firmware update for this hard drive.
So i don't know what other thing i can try. I want to emphasize that there is no problem, no freezing, when running Windows, so i don't think it's a hard drive issue.
Info:
Hard drive is a Toshiba 2.5" HDD MQ01ABD100 5400 rpm.
Some logs i've recollected all this time:
journalctl -xfa --system
abr 21 13:51:13 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
abr 21 13:51:24 echoes kernel: ata1.00: failed command: CHECK POWER MODE
abr 21 13:51:24 echoes kernel: ata1.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 7
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 21 13:51:24 echoes kernel: ata1.00: status: { DRDY }
abr 21 13:51:24 echoes kernel: ata1: hard resetting link
abr 21 13:51:24 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
abr 21 13:51:24 echoes kernel: ata1.00: configured for UDMA/100
abr 21 13:51:24 echoes kernel: ata1: EH complete
abr 21 14:01:40 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
abr 21 14:02:01 echoes kernel: ata1.00: failed command: SMART
abr 21 14:02:01 echoes kernel: ata1.00: cmd b0/d1:01:00:4f:c2/00:00:00:00:00/00 tag 23 pio 512 in
res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 21 14:02:01 echoes kernel: ata1.00: status: { DRDY }
abr 21 14:02:01 echoes kernel: ata1: hard resetting link
abr 21 14:02:01 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
abr 21 14:02:01 echoes kernel: ata1.00: configured for UDMA/100
abr 21 14:02:01 echoes kernel: ata1: EH complete
abr 21 14:02:01 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
abr 21 14:02:01 echoes kernel: ata1.00: failed command: SMART
abr 21 14:02:01 echoes kernel: ata1.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 22 pio 512 in
res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 21 14:02:01 echoes kernel: ata1.00: status: { DRDY }
abr 21 14:02:01 echoes kernel: ata1: hard resetting link
abr 21 14:02:01 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
abr 21 14:02:01 echoes kernel: ata1.00: configured for UDMA/100
abr 21 14:02:01 echoes kernel: ata1: EH complete
abr 21 14:02:01 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
abr 21 14:02:01 echoes kernel: ata1.00: failed command: SMART
abr 21 14:02:01 echoes kernel: ata1.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 18
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 21 14:02:01 echoes kernel: ata1.00: status: { DRDY }
abr 21 14:02:01 echoes kernel: ata1: hard resetting link
abr 21 14:02:01 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
abr 21 14:02:01 echoes kernel: ata1.00: configured for UDMA/100
abr 21 14:02:01 echoes kernel: ata1: EH complete
abr 21 14:01:51 echoes udisksd[627]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/TOSHIBA_MQ01ABD100_Y44MT611T: Error updating SMART data: sk_disk_smart_status: Input/output error (udisks-error-quark, 0)
dmesg
[55661.023028] ata1.00: exception Emask 0x0 SAct 0x8000 SErr 0x0 action 0x6 frozen
[55661.023034] ata1.00: failed command: READ FPDMA QUEUED
[55661.023040] ata1.00: cmd 60/08:78:18:08:c0/00:00:4b:00:00/40 tag 15 ncq 4096 in
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[55661.023042] ata1.00: status: { DRDY }
[55661.023046] ata1: hard resetting link
[55666.358537] ata1: link is slow to respond, please be patient (ready=0)
[55671.053813] ata1: COMRESET failed (errno=-16)
[55671.053819] ata1: hard resetting link
[55676.389438] ata1: link is slow to respond, please be patient (ready=0)
[55678.897149] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[55681.320305] ata1.00: configured for UDMA/100
[55681.320319] ata1.00: device reported invalid CHS sector 0
[55681.320349] ata1: EH complete
[55729.969443] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe A
[55729.969588] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
dmesg
[102884.889930] systemd[1]: systemd-journald.service: main process exited, code=dumped, status=6/ABRT
[102884.890305] systemd[1]: Unit systemd-journald.service entered failed state.
[102884.890333] systemd[1]: systemd-journald.service failed.
[102885.560745] systemd-coredump[28916]: Detected coredump of the journal daemon itself, diverted to /var/lib/systemd/coredump/core.systemd-journal.0.5bf9a012fed048ce8975998cf3c3c20e.6705.1427990901000000.
[102885.860957] systemd-journald[28919]: File /var/log/journal/b130c96d1371445d9ddeb40c51c77dd6/system.journal corrupted or uncleanly shut down, renaming and replacing.
[102921.797810] systemd-journald[28919]: File /var/log/journal/b130c96d1371445d9ddeb40c51c77dd6/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
[104179.117363] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
[104179.117369] ata1.00: failed command: READ FPDMA QUEUED
[104179.117375] ata1.00: cmd 60/08:00:48:88:8b/00:00:4d:00:00/40 tag 0 ncq 4096 in
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[104179.117377] ata1.00: status: { DRDY }
[104179.117381] ata1: hard resetting link
[104184.453382] ata1: link is slow to respond, please be patient (ready=0)
[104189.149114] ata1: COMRESET failed (errno=-16)
[104189.149121] ata1: hard resetting link
[104189.469276] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[104189.952982] ata1.00: configured for UDMA/100
[104189.952989] ata1.00: device reported invalid CHS sector 0
[104189.953004] ata1: EH complete
[104508.223792] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[104508.223798] ata1.00: failed command: SMART
[104508.223803] ata1.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 2
res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[104508.223806] ata1.00: status: { DRDY }
[104508.223810] ata1: hard resetting link
[104509.984601] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[104510.698126] ata1.00: configured for UDMA/100
[104510.698157] ata1: EH complete
One of the latest and worse
journalctl -xfa --system
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:00:e0:d6:75/00:00:00:00:00/40 tag 0 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:08:08:d8:75/00:00:00:00:00/40 tag 1 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:10:30:d9:75/00:00:00:00:00/40 tag 2 ncq 4096 out
res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:18:58:da:75/00:00:00:00:00/40 tag 3 ncq 4096 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:20:e8:e5:75/00:00:00:00:00/40 tag 4 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:28:80:db:75/00:00:00:00:00/40 tag 5 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:30:68:dd:75/00:00:00:00:00/40 tag 6 ncq 4096 out
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:38:90:de:75/00:00:00:00:00/40 tag 7 ncq 4096 out
res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:40:b8:df:75/00:00:00:00:00/40 tag 8 ncq 4096 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:48:90:e1:75/00:00:00:00:00/40 tag 9 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:50:98:e3:75/00:00:00:00:00/40 tag 10 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:58:c0:e4:75/00:00:00:00:00/40 tag 11 ncq 4096 out
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/c8:78:28:b9:2a/0b:00:4e:00:00/40 tag 15 ncq 1544192 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:80:b0:4b:c0/00:00:4f:00:00/40 tag 16 ncq 4096 out
res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/10:88:90:4b:80/00:00:50:00:00/40 tag 17 ncq 8192 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:90:98:22:81/00:00:50:00:00/40 tag 18 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:98:00:0e:00/00:00:5f:00:00/40 tag 19 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:a0:00:08:80/00:00:5f:00:00/40 tag 20 ncq 4096 out
res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:a8:80:08:80/00:00:5f:00:00/40 tag 21 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/10:b0:08:0b:81/00:00:5f:00:00/40 tag 22 ncq 8192 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:b8:70:c8:75/00:00:00:00:00/40 tag 23 ncq 4096 out
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:c0:20:c9:75/00:00:00:00:00/40 tag 24 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:c8:88:c9:75/00:00:00:00:00/40 tag 25 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:d0:58:ca:75/00:00:00:00:00/40 tag 26 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:d8:a0:ce:75/00:00:00:00:00/40 tag 27 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:e0:68:d3:75/00:00:00:00:00/40 tag 28 ncq 4096 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:e8:90:d4:75/00:00:00:00:00/40 tag 29 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:f0:b8:d5:75/00:00:00:00:00/40 tag 30 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1: hard resetting link
abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
abr 22 12:57:11 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
abr 22 12:57:11 echoes kernel: ata1.00: configured for UDMA/100
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x06
abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] CDB:
abr 22 12:57:11 echoes kernel: cdb[0]=0x2a: 2a 00 12 88 d7 c0 00 04 d0 00
abr 22 12:57:11 echoes kernel: blk_update_request: I/O error, dev sda, sector 310958016
abr 22 12:57:11 echoes kernel: EXT4-fs warning (device sda2): ext4_end_bio:317: I/O error -5 writing to inode 36311758 (offset 8388608 size 2695168 starting block 38869906)
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995128
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995129
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995130
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995131
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995132
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995133
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995134
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995135
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995136
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995137
abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x06
abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] CDB:
abr 22 12:57:11 echoes kernel: cdb[0]=0x2a: 2a 00 4b dd 39 88 00 01 78 00
abr 22 12:57:11 echoes kernel: blk_update_request: I/O error, dev sda, sector 1272789384
abr 22 12:57:11 echoes kernel: EXT4-fs warning (device sda2): ext4_end_bio:317: I/O error -5 writing to inode 34999445 (offset 0 size 192512 starting block 159098720)
abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x06
abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] CDB:
abr 22 12:57:11 echoes kernel: cdb[0]=0x2a: 2a 00 4e 2a b3 e8 00 05 40 00
abr 22 12:57:11 echoes kernel: blk_update_request: I/O error, dev sda, sector 1311421416
abr 22 12:57:11 echoes kernel: EXT4-fs warning (device sda2): ext4_end_bio:317: I/O error -5 writing to inode 35001016 (offset 0 size 2232320 starting block 163927845)
abr 22 12:57:11 echoes kernel: ata1: EH complete
abr 22 12:57:11 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
abr 22 12:57:11 echoes kernel: ata1.00: failed command: CHECK POWER MODE
abr 22 12:57:11 echoes kernel: ata1.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 25
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1: hard resetting link
abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
abr 22 12:57:11 echoes kernel: ata1: COMRESET failed (errno=-16)
abr 22 12:57:11 echoes kernel: ata1: hard resetting link
abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
abr 22 12:57:11 echoes kernel: ata1: COMRESET failed (errno=-16)
abr 22 12:57:11 echoes kernel: ata1: hard resetting link
abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
abr 22 12:57:11 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
abr 22 12:57:11 echoes kernel: ata1.00: configured for UDMA/100
abr 22 12:57:11 echoes kernel: ata1: EH complete
Current smart status:
smartctl 6.3 2014-07-26 r3976 [x86_64-linux-4.0.1-1-ARCH] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Toshiba 2.5" HDD MQ01ABD...
Device Model: TOSHIBA MQ01ABD100
Serial Number: Y44MT611T
LU WWN Device Id: 5 000039 5e1a80e85
Firmware Version: AX1P5E
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Sun May 3 16:42:06 2015 ART
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 120) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 234) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1671
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 306
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 152
7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 699
10 Spin_Retry_Count 0x0033 106 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 300
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 216
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 14
193 Load_Cycle_Count 0x0032 099 099 000 Old_age Always - 14140
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 34 (Min/Max 16/44)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 19
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 0
222 Loaded_Hours 0x0032 099 099 000 Old_age Always - 515
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
226 Load-in_Time 0x0026 100 100 000 Old_age Always - 190
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Vendor (0x50) Completed without error 00% 611 -
# 2 Short offline Completed without error 00% 611 -
# 3 Short offline Completed without error 00% 597 -
# 4 Vendor (0x50) Completed without error 00% 583 -
# 5 Short offline Completed without error 00% 583 -
# 6 Vendor (0x50) Completed without error 00% 575 -
# 7 Short offline Completed without error 00% 575 -
# 8 Short offline Completed without error 00% 547 -
# 9 Extended offline Completed without error 00% 529 -
#10 Short offline Completed without error 00% 355 -
#11 Short offline Completed without error 00% 355 -
#12 Extended offline Aborted by host 70% 355 -
#13 Short offline Completed without error 00% 319 -
#14 Vendor (0x50) Completed without error 00% 13 -
#15 Short offline Completed without error 00% 13 -
#16 Short offline Completed without error 00% 12 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
Kernels used have been from 3.9 to current: Linux echoes 4.0.1-1-ARCH #1 SMP PREEMPT Wed Apr 29 12:00:26 CEST 2015 x86_64 GNU/Linux
Last edited by jesu (2015-05-03 19:42:53)Something i'd noticed both the first time i was on arch and now i've reinstalled it, was that at first i didn't have this problem. I mean, when Arch was just installed. While i was installing and setting up everything.
Now, i'm not 100% sure about this, but i think problems began when using my current user. Disk is partitioned the following way:
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931,5G 0 disk
├─sda1 8:1 0 1000M 0 part
├─sda2 8:2 0 260M 0 part /boot
├─sda3 8:3 0 207,7G 0 part
├─sda4 8:4 0 25G 0 part
├─sda5 8:5 0 14,8G 0 part
├─sda6 8:6 0 80,5G 0 part /
├─sda8 8:8 0 599G 0 part /home
└─sda9 8:9 0 2G 0 part [SWAP]
So, i believe problems, for some reason, are related (and were related), both before and now, to the /home partition, /dev/sda8 in this ocassion.
Because of this, i booted into systemd rescue mode, like root, rw, and unmounted /home partition. Despite root-only limitations, i used the system for a couple of hours, started lxqt, browsed the web mainly, and experienced no problem at all.
Now i booted normally, with my regular user, and these problems are experienced just like before (and almost instantly, like 3 or 5 minutes after starting system use).
dmesg this time showed a some different log, though it's not the first time i see this. I just didn't saved that kind of log before.
[ 653.821719] ata1.00: exception Emask 0x0 SAct 0x100 SErr 0x0 action 0x6 frozen
[ 653.821726] ata1.00: failed command: READ FPDMA QUEUED
[ 653.821732] ata1.00: cmd 60/08:40:60:25:43/00:00:1b:00:00/40 tag 8 ncq 4096 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 653.821735] ata1.00: status: { DRDY }
[ 653.821739] ata1: hard resetting link
[ 659.156760] ata1: link is slow to respond, please be patient (ready=0)
[ 663.851604] ata1: COMRESET failed (errno=-16)
[ 663.851610] ata1: hard resetting link
[ 669.186591] ata1: link is slow to respond, please be patient (ready=0)
[ 673.881456] ata1: COMRESET failed (errno=-16)
[ 673.881462] ata1: hard resetting link
[ 679.216481] ata1: link is slow to respond, please be patient (ready=0)
[ 702.743982] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 703.012578] ata1.00: configured for UDMA/100
[ 703.012584] ata1.00: device reported invalid CHS sector 0
[ 703.012599] ata1: EH complete
[ 714.097642] systemd[1]: systemd-journald.service watchdog timeout (limit 1min)!
[ 742.443488] sd 0:0:0:0: [sda] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
[ 742.443494] sd 0:0:0:0: [sda] tag#18 CDB: opcode=0x2a 2a 00 28 c3 c6 40 00 00 10 00
[ 742.443497] blk_update_request: I/O error, dev sda, sector 683918912
[ 742.443503] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489866)
[ 742.443506] Buffer I/O error on device sda8, logical block 9323208
[ 742.443508] Buffer I/O error on device sda8, logical block 9323209
[ 742.443515] sd 0:0:0:0: [sda] tag#19 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
[ 742.443518] sd 0:0:0:0: [sda] tag#19 CDB: opcode=0x2a 2a 00 28 c3 c6 80 00 00 10 00
[ 742.443520] blk_update_request: I/O error, dev sda, sector 683918976
[ 742.443522] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489874)
[ 742.443524] Buffer I/O error on device sda8, logical block 9323216
[ 742.443526] Buffer I/O error on device sda8, logical block 9323217
[ 742.443531] sd 0:0:0:0: [sda] tag#20 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
[ 742.443534] sd 0:0:0:0: [sda] tag#20 CDB: opcode=0x2a 2a 00 28 c3 c6 d0 00 00 10 00
[ 742.443536] blk_update_request: I/O error, dev sda, sector 683919056
[ 742.443538] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489884)
[ 742.443540] Buffer I/O error on device sda8, logical block 9323226
[ 742.443542] Buffer I/O error on device sda8, logical block 9323227
[ 742.443547] sd 0:0:0:0: [sda] tag#21 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
[ 742.443549] sd 0:0:0:0: [sda] tag#21 CDB: opcode=0x2a 2a 00 28 c3 c7 10 00 00 10 00
[ 742.443551] blk_update_request: I/O error, dev sda, sector 683919120
[ 742.443553] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489892)
[ 742.443555] Buffer I/O error on device sda8, logical block 9323234
[ 742.443557] Buffer I/O error on device sda8, logical block 9323235
[ 756.187685] systemd[1]: systemd-journald.service: main process exited, code=dumped, status=6/ABRT
[ 756.187986] systemd[1]: Unit systemd-journald.service entered failed state.
[ 756.188116] systemd[1]: systemd-journald.service failed.
[ 756.188474] systemd[1]: systemd-journald.service has no holdoff time, scheduling restart.
[ 756.189106] systemd[1]: Stopping Flush Journal to Persistent Storage...
[ 756.189143] systemd[1]: Listening on Journal Audit Socket.
[ 756.189801] systemd[1]: Starting Journal Service...
[ 757.525493] systemd-coredump[1038]: Detected coredump of the journal daemon itself, diverted to /var/lib/systemd/coredump/core.systemd-journal.0.b8610e85f9074a418534aaee0adbac56.141.1430763073000000.lz4.
[ 758.133944] systemd-journald[1050]: File /var/log/journal/f646626ba4b647f48501020bf12ca33b/system.journal corrupted or uncleanly shut down, renaming and replacing.
[ 758.503041] systemd[1]: Started Journal Service.
[ 759.180771] systemd-journald[1050]: File /var/log/journal/f646626ba4b647f48501020bf12ca33b/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
[ 974.867721] ata1.00: exception Emask 0x0 SAct 0x3f80 SErr 0x0 action 0x6 frozen
[ 974.867732] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867742] ata1.00: cmd 61/08:38:68:d3:c5/00:00:1a:00:00/40 tag 7 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867747] ata1.00: status: { DRDY }
[ 974.867751] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867759] ata1.00: cmd 61/08:40:88:d3:c5/00:00:1a:00:00/40 tag 8 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867763] ata1.00: status: { DRDY }
[ 974.867767] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867774] ata1.00: cmd 61/08:48:a0:d3:c5/00:00:1a:00:00/40 tag 9 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867778] ata1.00: status: { DRDY }
[ 974.867781] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867789] ata1.00: cmd 61/20:50:c0:d3:c5/00:00:1a:00:00/40 tag 10 ncq 16384 out
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867793] ata1.00: status: { DRDY }
[ 974.867796] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867803] ata1.00: cmd 61/10:58:f0:d3:c5/00:00:1a:00:00/40 tag 11 ncq 8192 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867807] ata1.00: status: { DRDY }
[ 974.867810] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867817] ata1.00: cmd 61/08:60:10:d4:c5/00:00:1a:00:00/40 tag 12 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867821] ata1.00: status: { DRDY }
[ 974.867824] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867831] ata1.00: cmd 61/18:68:28:d4:c5/00:00:1a:00:00/40 tag 13 ncq 12288 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867835] ata1.00: status: { DRDY }
[ 974.867841] ata1: hard resetting link
[ 980.202774] ata1: link is slow to respond, please be patient (ready=0)
[ 984.900902] ata1: COMRESET failed (errno=-16)
[ 984.900908] ata1: hard resetting link
[ 990.236024] ata1: link is slow to respond, please be patient (ready=0)
[ 994.930829] ata1: COMRESET failed (errno=-16)
[ 994.930836] ata1: hard resetting link
[ 996.798104] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 997.014012] ata1.00: configured for UDMA/100
[ 997.014020] ata1.00: device reported invalid CHS sector 0
[ 997.014023] ata1.00: device reported invalid CHS sector 0
[ 997.014025] ata1.00: device reported invalid CHS sector 0
[ 997.014026] ata1.00: device reported invalid CHS sector 0
[ 997.014028] ata1.00: device reported invalid CHS sector 0
[ 997.014030] ata1.00: device reported invalid CHS sector 0
[ 997.014031] ata1.00: device reported invalid CHS sector 0
[ 997.014065] ata1: EH complete
There are some sda8 (home) related messages. I also found these messages first time Arch was installed (i think also related to home partition).
root and home partitions are both ext4. -
How do I resolve LOCKED DISKS problem ? NO ACCESS ANYMORE !
Hello everybody,
I've looked carefully where to post this topic,
and I hope it's the right place here
(I have already been warned not to post the same questions in different places).
I have actually 2 internal volumes locked, 2 external Firewire volumes locked and 2 USB external volumes locked. I'm talking about *5,7 To* with *NO ACCESS* anymore.
It happened suddenly, and I was working on Snow Leopard 10.6.3 internal drive. This volume is the *only one* that has NOT been locked, but I lost a lot of applications, documents and so on on it.
Each of the locked volumes I am talking about shows,
in *Sharing & Permissions* (Get Info window),
the same Privileges :
— everyone : Custom
— admin : Custom
— olcha (Me) : Custom
— staff : Custom
— everyone (again) : Custom
You'll notice that "System" is not there (should be there with R+W),
and "admin" should have also R+W privilege.
I don't know why "staff" is here (perhaps, one day, somebody will explain to me the difference between : wheel, staff and admin).
I also don't know why "everyone" is there two times.
If I unlock the padlock (bottom right) with my password, I can only
check or uncheck the "Ignore ownership on this volume" square (bottom left).
Doing this (apparently) offers *no interest at all* to solve the problem
(and what does this function produce, when activated or not ?).
I can't *absolutely not* :
• Change *any privilege* of any of the 5 items ;
• Remove (with "-") any of these items ;
• Add a line (for example "System" or "wheel", why not ?)
but nothing new is shown after "+" making.
• The wheel (on the right of "+" and "-") shows only "revert changes" in grey.
I phoned immediately last thursday Apple Assistance,
and I am in contact with a Level 2 Apple Adviser who gave me his e-mail.
I sent him two messages, but he replied me that perhaps MONDAY
he could find the time to call me.
Now, first, please tell me if you have any idea or solution !
Thank you very much in advance.
Secondly, I have reflected on the solving,
and would like to know what you think about what follows :
You know that, in Disk Utility, you can erase a disk or partition.
If, in "Security Options…", I choose "Don't Erase Data", and then "Erase…" :
1) Sharing and Permissions will be changed and become (reset to) correct ;
2) It's said, in "Security Options…",
that "many commonly available disk recovery applications can restore that data".
I would be very glad that you indicate me :
1) the best application to use for that recovery ;
2) I already own "Drive Genius 3.0", "Data Rescue 3.0.2" and
(I think it's the best after a try on an internal 30 Go partition)
"Stellar Phoenix Macintosh Data Recovery".
Thank you in advance for your answers and advices,
With my kind regards
Olivier Herrbach
[email protected]
PS : Dear Forum Webmaster,
I would like to know :
1) if I posted this topic in the right place ;
2) if you allow me to post it elsewhere (and in this case, where ?) ;
3) is it possible to paste images in messages,
and, if yes, which format is needed (TIFF, png, jpeg …)
Thank you very much
Olivier HerrbachDear ChazBowie,
Here is the solution I've found for *LOCKED DISKS* problem.
I'll respond the shorter I can, avoiding for the moment to talk about the complicated solutions
that Apple gave to me, which involved volume by volume (only one each time) intervention, and were working by, each time, entering one line, password, then another line in Terminal. I will communicate these instructions later, but they do not need to be publicated here with urgence.
I found two little free softwares that can modify *ALL Privileges* in Sharing and Permissions, *on ANYTHING*. You will have to be careful using them, as they even allow to act as "Root" administrator.
I'd also like everyone to *donate anything* to these helpful developers, and I'd be very pleased to have *your feedback and results*.
••• 1) — *BatChmod 1.6.2* (162), written by a compatriot, Renaud Boisjoly.
E-mail (if you have doubts or questions) : [email protected]
Free software downloading site : *http://www.macchampion.com/arbysoft*
(excuse me, but I don't know how to make a link here).
••• 2) — *FileXaminer 2.7*, recommended by Renaud himself.
Dear ChazBowie,
Here is the solution I've found for *LOCKED DISKS* problem.
I'll respond the shorter I can, avoiding for the moment to talk about the complicated solutions
that Apple gave to me, which involved volume by volume (only one each time) intervention, and were working by, each time, entering one line, password, then another line in Terminal. I will communicate these instructions later, but they do not need to be publicated here with urgence.
I found two little free softwares that can modify *ALL Privileges* in Sharing and Permissions, *on ANYTHING*. You will have to be careful using them, as they even allow to act as "Root" administrator.
I'd also like everyone to *donate anything* to these helpful developers, and I'd be very pleased to have *your feedback and results*.
••• 1) — *BatChmod 1.6.2* (162), written by a compatriot, Renaud Boisjoly.
E-mail (if you have doubts or questions) : [email protected]
Free software downloading site : Gideon Softworks : *http://www.gideonsoftworks.com/*
I won't copy here the texts that are on both sites, but it's very instructive.
Remember that the applications don't only work on files and folders,
*but also on disks attributes*.
You'll also have some work to do (I don't remember, perhaps not), by going in the Get Info windows
and changing privileges to the correct ones, that means you must know
(I'm not sure, verify please) what privileges are to be set for a volume
(YOU WILL HAVE ACCESS TO THEM, AND CHANGES YOU MAKE WON'T BE RESET TO "CUSTOM").
Does anybody know something about the "Ignore ownership on this volume" checkbox ?
*I always uncheck it*.
I would also like very much to know the differences between the two-headed iconed groups :
"staff", "wheel" and "admin", and IN THE END know *WHERE are the rules* you have to observe
when doing changes in privileges (for example, I don't want to give my password to copy something in Users folder, nor "MyName" folder. I've changed that without, I hope, having created any dysfunction).
Please tell me if you know anything about these 2 subjects above.
I'm very glad if my informations have been useful/helpful.
With my kind regards,
Olivier Herrbach -
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 !!!! -
I deleted unwanted photos from my iPhoto library, emptied iPhoto trash & Finder trash... this did not free up disk space. please help!
I have a 15-inch MacBook Pro (Late 2011) with OS X Mavericks 10.9.5
Last week, my 500 GB Harddrive had 120 GB free space. I was feeling crumby and decided to make productive use of taking a day off to lounge around. I snuggled up with my laptop and dedicated hours to meticulously combing through my iPhoto Library. I had 13,000 pictures, and I got rid of those I didn't want. Having said "sayōnara" to about 6,500 pictures, I then emptied the iPhoto trash and the Finder trash. I took delight in the iconic paper crumpling sound of them vanishing into the digital void.
Everything seemed perfect: the photos I loved were still there, the photos I loathed were gone, both trashes were beautifully empty. Having thrown away all of those awful, boring, and unflattering images of poorly light lunches and selfies gone wrong, my iPhoto library was half the size as before! I felt renewed, a little lighter, somehow more free, and I expected my hard drive to be a bit different to.
I eagerly checked my storage stats. My heart sank to see that my 120 GB of free space, was still only 120 GB of free space. I restarted my MacBook; this did not help. I restarted it the next day; this also did not help. It's been 5 days and the hard drive still has 120 GB free space. This is not an emergency and it will probably be a good while before I clutter my laptop to the brim. Yet while I am glad I don't have to see cringeworthy pictures of my ex's unmentionables every time I'm showing off things I do want to remember, I'm still disappointed and now obsessed with solving this mystery.
What is going on? I don't see them, so where are they hiding? How do I get the free space I should have earned from throwing away 1,000's of photos?!Thank you, Terence!
Yes, I only emptied the trash when it was really full, once I waited until the trash cans contained 2,600 photos and then I emptied them - Oooops! In the future, I'll keep in mind your suggestion of deleting less than 100 photos at a time.
I downloaded the iPhoto Library Manager and used it to rebuild my iPhoto. After a few hours of rebuilding, it generated a new copy of my iPhoto Library. This versions was nearly identical to the original (it was missing 5 photos and was therefore only 5 mb smaller). I guess my Library wasn't defective.
I checked my storage stats, and interestingly, using iPhoto Library Manager did help with the problem that developed after I re-indexed my hard drive. My hard drive is able to properly recognize data categories again, instead of listing almost everything as "Other". Understandably, my free disk space changed from 120 GB to about 60 GB, because my hard drive now contained a second copy of my iPhoto Library as well as iPhoto Library Manager. It seemed like all I needed to do was throw these away, but when I emptied the trash, my problem was not solved. My Hard drive now looked like this:
It appears to me that when I empty the trash, the things I throw away are just hanging around as backups instead of leaving! I went into System Preferences and turned of my time machine OFF. Now my hard drive looks likes this:
The back ups of the iPhoto files, and the program which I deleted, are still on my hard drive some where but now they are listed as "Other" instead of "Backups". Do you know where they might be and how I can delete them for good? -
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. -
Satellite L55-A5299 Hard Disk Problem
My laptop has a pop-up saying Windows detected a hard disk problem, I have already backed up my stuff. I also did a complete restore of the laptop and that still didn't make it go away. What do I have to do?
Hi Ishaan,
I have already backed up my stuff. I also did a complete restore of the laptop and that still didn;t make it go away.
I just want to verify the word "complete restore" does it mean wiping the entire computer back to factory settings?
On my own option this is something to do about the internal hdd that is to became failing. So I would suggest if you still have warranty of your laptop contact toshiba # 1800.457.7777 business time 8am-2am the following day EST. Or if the laptop doesnt have warranty anymore, better buy a new hdd.
Hope this will work for you. ^_^
BTW IF YOU THINK IT HELPS ALOT. PLEASE DONT BE AFRAID TO CLICK KUDOS star ^_^
- cokies -
IMovie 09 problems PLEASE help!!! so frustrating!!
iMovie was working fine before, until I started a new project and when I tried to playback, it only plays the audio in the viewer... I tried viewing in fullscreen, but it was just a black screen, with audio playback only and to make matters worse, it would not exit fullscreen playback mode. I literally had to unplug my iMac to shut it down, and it DID NOT AUTOSAVE ANYTHING! I also notice most of the menu items are greyed out. I can't add themes, transitions... nothing... I can't even select project properties.. and the project is there, at least the first few clips are there... but the hours of work after is lost. I tried editing AGAIN, and it is not saving any of the new changes I made, even if I shut it down properly. I KNOW how to use iMovie, I've read endless forums, no proposed solutions are working for me.. I am NOT upgrading to '11 PLEASE HELP! This is very frustrating!! - thanks
Hi
Un-plugging the Mac is a dangerous action and nearly always adds small errors on the hard disk - With luck it starts again - if unlucky it doesn't and eventually need repair by pro - to be back in action.
Just to mention it.
If this happens to me I do
• Run Disk Util tool and Repair Permissions
• Start Mac from DVD that came with it and now orient to Disk Util tool on this and - Repair Hard Disk
(This must be done when Mac runs on DVD or external Hard Disk - Can not do Brain Surgery on one self.)
• Then I would re-start from Main Mac OS Hard Disk - usually named Macintosh HD - then trash the pref file/s associated to Application that behaves Badly (usually in the User Account Library / Preferences
Else see my long list of what to do
When in Trouble
When iMovie doesn't work as intended this can be due to a lot of reasons
• iMovie Pref files got corrupted - trash it/they and iMovie makes new and error free one's
• Creating a new User-Account and log into this - forces iMovie to create all pref. files new and error free
• Event or Project got corrupted - try to make a copy and repair
• a codec is used that doesn't work
• problem in iMovie Cache folder - trash Cache.mov and Cache.plist
• version miss match of QuickTime Player / iMovie / iDVD
• preferences are wrong - Repair Preferences
• other hard disk problem - Repair Hard Disk (Disk Util tool - but start Mac from ext HD or DVD)
• External hard disks - MUST BE - Mac OS Extended (hfs) formatted to work with Video
( UNIX/DOS/FAT32/Mac OS Exchange - works for most other things - but not for Video )
• USB-flash-memories do not work
• Net-work connected hard disks - do not work
• iPhoto Library got problems - let iPhoto select another one or repair it. Re-build this first then try to re-start iMovie.
This You do by
_ close iPhoto
_ on start up of iPhoto - Keep {cmd and alt-keys down}
_ now select all five options presented
_ WAIT a long long time
• free space on Start-Up (Mac OS) hard disk to low (<1Gb) - I never go under 25Gb free space for SD-Video (4-5 times more for HD)
• external devices interferes - turn off Mac - disconnect all of them and - Start up again and re-try
• GarageBand fix - start GB - play a few notes - Close it again and now try iMovie
• Screen must be set to million-colors
• Third-party plug-ins doesn't work OK
• Run "Cache Out X", clear out all caches and restarts the Mac
• Let Your Mac be turned on during one night. At about midnight there is a set of maintenance programs that runs and tidying up. This might help
• Turn off Your Mac - and disconnect Mains - for about 20-30 minutes - at least this resets the FireWire port.
• In QuickTime - DivX, 3ivx codec, Flip4Mac, Perian etc - might be problematic - temporarily move them out and re-try
(I deleted the file "3ivxVideoCodec.component" located in Mac HD/Library/Quicktime and this resolved my issue.)
buenrodri wrote
I solved the problem by removing the file: 3ivxVideoCodec.component. after that, up-dated iMovie runs ok.
Last resort: Trash all of iMovie and re-install it
Yours Bengt W -
990fxa gd80 raid 0 problem please help me i am begging you
so i will start with my set up
990fxa dg80 mb
fx 8350 cpu
780ti
8 gig of ram
256 hdd
2x samsung 850 evo
750 hybrid drive
So at this stage all my data is on the 750 hdd and the disk is stored away. my problem started with me buyng 2 mx100 256 ssds . If my bios is set to ide or ahci they work fine i had my windows instaled on 1 of them all woks fine. Once i switch my bios to raid ( before i set up my raid 0) boot up win 7 instalation i do not see any drives ( i know is normal) load the drivers for the raid controler (sb950 for w7 as it says in themanual) and only my 256 hdd shows up but not the ssds . Than i set them up in ld raid 0 same problem . Tryed on another 2 mbs ... 1 same and a gygabite same problem. So i was sure there is a problem with ssds. I got rid of them got 2 new 850 evo 250 gb same problem. please help me i am so desparate i am willing to pay woth body organs for helpI..have a few questions...
1. You set BIOS to the RAID mode, and under that option there's a Board SATA RAID ROM, do you set it as Legacy ROM?
2. Did you enter Ctrl+F to initialize the drives/Delete Array(If they're used SSDs) and create RAID0?
3. Is your Win7 64 bit or 32 bit?
4. I assume it's 64 bit, did you copy the W764 folder for driver loading?
And make sure you get the driver from here:
http://www.msi.com/support/mb/990FXAGD80.html#down-driver&Win7 64 -
Urgent Problem please Help(hayat)
Hello Hi,
I want to Install Form 6.0 With Oracle 8i on Server
mean not personal oracle,
if i install first oracle 8i and then form 6.0 then
they overwrite their homes and vice versa.
What method i use to control this problem.
please help me so that i install form 6.0 on oracle 8i server.
thanks
hayatOk, I have read the sun site and downloaded the JDK and saved it to disk in the C:\ drive.
However I still get the same error so I think I must be very stupid and I think the computer knows that. -
I am not very computer Savoy!. But every time I turn my laptop on it keeps freezing up on me and I get a massage that says I am having a Hard Disk Problem and that I should back up all my files before the computer crashes. And I would like to what I should do to fix this? I thought that I could reload my operating system but my computer did not come with that disk and I can't seem to find it here on this web site. Any idea's?
Without knowing specifically which model you have it's difficult to tell for sure, but most Toshiba's made in the past few years come with a Recovery Partition. You can invoke the Recovery Process by holding down the 0 (zero) key while turning the computer on and holding it down until the Recovery Process starts. You can also create a set of Recover Disks from the Recovery partiton by going to "Start - All Programs - Toshiba - Recovery - Recovery Disk Creator".
As for the error message about Hard Disk Problem, that could mean that the hard drive is starting to malfuncion and will soon stop functioning at all. You need to determince what brand of hard drive your's is, go to that companies support site, download their Diagnostic Program, install it, and run the most exhaustive test to determine if it is failing or not.
And please backup you important data as soon as humanly possible as there is a good chance you will lose it forever.
If you don't post your COMPLETE model number it's very difficult to assist you. Please try to post in complete sentences with punctuation, capitals, and correct spelling. Toshiba does NOT provide any direct support in these forums. All support is User to User in their spare time. -
Running Mavericks on an iMac 2.7 GHz Intel Core i5, I've been trying to install Adobe CS3 Design Premium. All components install except InDesign. Is this an installation disk problem, or is there a compatibility problem with the OS?
I fear that you are trying to download OLDER Software on a newer Operating Sysytem Meaning that you need to Install the Latest Version of Adobe on the Newer Operating System for it to work Properly. Be sure to always check the minimum System Requirements.
Maybe you are looking for
-
HT201335 iPad Mini and Apple TV issue
My iPad mini will change to Apple TV when requested, but will only pause playback on device and then the check mark returns to iPad. My 4s works perfect with my Apple TV. Any ideas? I doubt it is linked, but I am also not able to stream Sirius XM on
-
Can't startup the database through "isqlplusdba"
I have connectd as sysdba to the oracle 9i database through iSQLPLUSDBA. My database was initially in started mode. Then I did a normal shutdown(successfully). But When I try to startup it gives me following error. LRM-00101: unknown parameter name '
-
Its very urgent ...Rfc deffinately rewarded with 10 points....
Hi Experts....this is my requirement...plz help me in this ...case here we have TWO Databases: Db1 , db2 (this intereact with the Third Party), In SE38 ABAP Editor : we have to write a programme in this we have to SELECT-OPTION is Used Four Fields an
-
ORA-01545: rollback segment 'R01' specified not available, after disk crash
After a disk problem, when I try to open the database I receive the error 0ra-01545.What can I do resolve this? It seems that the rollback segment is marked for recover. I an only mount the database.
-
Create SDO_GEOMETRY from existing adding SRID
Hi, I have a SDO_GEOMETRY without an SRID in it, and I need to call like in the following statement : SELECT A.G3E_FID, SDO_UTIL.TO_WKTGEOMETRY( SDO_LRS.CONVERT_TO_STD_GEOM( SDO_CS.transform( a.g3e_geometry, 28992))) g3e_geometry, 28992 srid FROM las