Hugo van der Kooij wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Todd and Margo Chester wrote:
| Since upgrading top CentOS 5.2, twice now while cutting a data
| dvd with k3b-0.12.17-1.el5, my system has frozen. Mouse
| disappeared, no keyboard, cap-locks and scroll-locks lights blink
| at a one second interval. And, my file system gets corrupted.
|
| B-A-D C-O-R-R-U-P-T-E-D.
|
| I have had to do a complete remake and restore. Very, very serious.
| My whole business is on this computer. IT CAN NOT GET CORRUPTED AGAIN!
| (Yes, I have great backup. I am tired of using it!)
I think it is extremely unlikely that the k3b version is relevant at all
with the issue you are reporting. The fact that it happens while you use
k3b is propably just coincidence as well.
My first hunch is defective hardware which just happens to be called
upon by k3b. If yo use another similar program it will likely occur just
as well.
At this point the quest for a k3b update is propably just as fruitful as
~ most other quests. It's just searching for the wrong problem.
Hi Hugo,
At this point, we should separate the request into two.
1) An RPM for Sebastian's latest efforts (1.0.5 fixes
the door eject/inject problem where the verify tells you
there is no disk in the drive).
2) My kernel panic problems with writing to a SATA burner.
At this point, I do believe K3B/growisofs is off the hook.
But that still does not mean that it would not be a "Capital
Idea" to have access to Sebastian's latest work.
I am remembering that I had a few CentOS 4.x servers out there
with Plextor SATA drives in them. If you wrote "anything"
to them with any program, you got a kernel panic. I had
the replace them all with PATA drives at my own expense.
When CentOS 5.0 came along, the problem disappeared. I
have one Plextor SATA drive left out there: mine. It
seems that whatever kernel changes were made between
CentOS 5.1 and 5.2, the problem came back in spades.
I should probably take a trip over to http://bugzilla.kernel.org/
and see if this has already been reported.
I do believe that at this point, I should dump my SATA
Plextor drive with something that has a good track record
with CentOS 5.2. Any suggestions?
And, as issue number 2) is off topic for this discussion group,
I like to thank everyone for indulging me. I had some
pretty scary stuff happens to me over the last couple of
weeks.
Many thanks,
--T
_______________________________________________
users mailing list
[email protected]
http://lists.rpmforge.net/mailman/listinfo/users
