Razvantin 2009-09-22 04:13:09 UTC Description of problem: When i boot a live CD, just before the start screen i get ata3: SRST failed (errno=-16) This way i can't find my HDD when trying to install. Downloaded ISO's checksum is ok. Burned at 8x speed. RAID is disabled. HDD is on ata1 slot. HDD has no 'cable select' jumper setting.

Jumper on 1.5gb/s has no effect. Version-Release number of selected component (if applicable): i just guessed the component as suggested by the site.

I am guessing the component has to do with finding HDDs. How reproducible: 100% Steps to Reproduce: 1.boot Fedora 11 Live CD 2. Actual results: Failing to detect my HDD Expected results: ata3: SRST failed (errno=-16) Additional info: I made Fedora work at a point. I had two windows xp partitions, c and d, with the system being installed on D:. I used C: to make the whole linux partition structure. Before the installation finished, i chose D: with WinXP on, as path for the boot loader. This way i lost my Xp system but Fedora was looking good.

I've update it and reboot it several times. I set up some widgets and turned the computer off.

Next thing in the morning i got that SRST failed again. I formated all partitions into one big chunk using Xp install CD, at that point, the only CD that could detect my HDD. I was suggested to try and switch off HDD's powersave feature with hdparam -Z but this only returns: disabling Seagate auto powersaving mode HDIODRIVECMD(seagatepwrsave) failed: Invalid exchange At this moment, my HDD has one partition with a fully operational WinXP but my live CD does not see my HDD anymore. My hardware configuration is PCC: Pentium D 945 3400mhz, fsb 800mhz MB: nForce 680i RAM: 2x A-data 1gb ddr2 @800mhz VB: 9800 GT 1gb HDD: Seagate Barracuda 7200.10 sata2 320gb. Razvantin 2009-09-23 00:05:38 UTC Can someone change The Severity to 'High': 'Severity Two issues are defined as high-impact issues.' Fedora 11 is unusable.

'The customer's operation is disrupted,' I lost data trying to recover the partition, and time installing programs that got lost due to this error. 'but there is some capacity to produce.' Only live CD'ing. Don't mean to annoy anyone nagging. I know you are pretty busy being involved in this project. And most of all you are doing it for 'free as in freedom'. More over, i do intend to commit and contribute to fedora project by promoting your work and expose it to my local business environment in any way i can.

Razvantin 2009-09-24 20:30:54 UTC I now checked the Live CD after you asked me to on IRC. This time i didn't received the SRST failed and Installer found my HDD. I will fresh install fedora 11 on my hdd. But i am expecting the OS to fail again after a while. I already stated i made Fedora work once before, only to have it SRST failed crush again. I did the same with xubuntu several month ago The thread reached 2900 views by now and no one is being able to solve this problem i am experiencing:( xp linux srst eror xp linux and so on. My system is in the linux phase since the live CD started to see my HDD again.

I only installed Windows XP and some drivers/programs since my last SRST failed under live CD. Razvantin 2009-09-29 02:08:40 UTC Further findings: Guaranteed things that trigger the bug: Powering off HDD for less then 1 minute. Suspending to Disk Suspending to RAM Partial Solution 1.Have a fail-safe Windows XP Operating System installed on a separate partition. 2.Each time the Error occurs, boot Windows XP and install 'NVIDIA Storage Driver' that came with the Mother Board, weather you have it installed already or not. 3.Reboot windows Xp so that the changes can take effect.

Sleep Issues 17 Month Old

Fedora 11 will now boot once again without any loss of data. The only problem is that you will repeat this actions each time you power off/suspend to Disk/Suspend to RAM Also, Bootloader Menu might go blank though not jam itself and you would have to guess witch boot you chose. Will a proper hotfix come in a new update soon? Razvantin 2009-10-03 15:41:56 UTC I posted the entire kernel boot log during all cycles of this bug. As requested by Chuck Ebbert.

Also, Kevin Fenzi mentioned something about re-assigning the issue over to kernel. The component in question on this bug log was selected to 'kernel'. Was i suggested to head over to a new forum witch is new to me or all checks are go and i should wait for a reply soon? I mean i check this thread about 3 times a day and i only got a reply from those guys. Is anything happening?

It took me one night and a day to repeat the cycles until i figured out what was going on. I narrowed the guesses down as much as i could. This bug is now 100% probable giving the system configuration above.