Hi Carl On Wednesday 31 May 2006 23:16, Carl Hartung wrote:
On Wednesday 31 May 2006 14:31, Kevin Donnelly wrote:
While experimenting with editing video with Kino on 9.3, I moved some files and the machine froze.
What size were the files? What format(s)? From the desktop in Konqueror or from the command line?
I was moving 1.6Gb of raw DV files via Konqueror from one location to another.
How long did you wait to see if the system would 'gather it's wits?'
Quite a while!
Were you able to reach a console? (Ctl+Alt+F1 to F6)? Did you check the kernel messages screen (Ctl+Alt+F10)?
No, couldn't reach any of them - the whole system had frozen.
A reboot halted at the GRUB announcement. Rebooting into Installation -> Rescue Installed System said sda2 (root dir) and sda7 (a data dir) were corrupt, and suggested repairs, which I accepted. It also said that sda10 (another data dir) had an unknown filesystem on it.
Just a comment:
All dirs on the disk use Reiserfs.
Try not to confuse "directories" with "partitions". Drives contain partitions which contain filesystems that are organized into directories which hold files. :-) (10 points will be deducted from your score if you slip and utter the word "folder".)
Yes, I meant to say partitions.
However, the app then hung at the stage where it attempts to mount fstab dirs.
Keep a notepad at your desk so you can write down error messages when you can't copy/paste them into a text file. The actual messages convey a lot more information than imprecise 'paraphrased' descriptions.
No, that's all it said. If you run Rescue Installed System on your own PC, you'll see it checks the partitions, then checks the fstab. With this, it says it has found x number of partitions, and then says it's attempting to mount them. I suspect it can't mount sda2, because it's so badly scrambled, and that's why it hangs.
Accessing the system via Rescue System from the CD allowed me to mount all
partitions
except sda2 and sda10, and the data on them *appears* to be OK
In other words, all partitions *but* sda2 and sda10 appear to be OK.
Yes.
Reiserfsck --check /dev/sda2 just gives up and says there must be bad blocks on the disk.
Again, exact error messages would be preferable to paraphrased remarks.
It's quite a long paragraph that says that it is unlikely that this disk is worth your time or money trying to repair, so just get a new one!
The fact that sda2 was already "repaired" (a few steps back) and still reads bad is not a good sign at all. Please tell me /home is on it's own partition? If not, this is the reason why organizing your system that way is a good idea.
I don't keep /home on a separate partition, because of possible issues with old config files when I upgrade. But I do keep all my data in /home/data, which is a symlink to another partition. Except for mail, which I should have symlinked in there, and of course the small database, which a separate /home wouldn't have dealt with anyway.
you can grab images of sda2 and sda10 *if* you've got space on another drive.
dd if=/dev/sda2 of=/path/sda2.img noerror dd if=/dev/sda10 of=/path/sda10.img noerror
Then you can try to repair/recover the originals while keeping the images as backups.
I may try that, though I think they're both so comprehensively trashed that it'll be pointless.
Have you ruled out basic hardware problems like a marginal power supply or lower quality memory? When a system generally runs OK but suddenly 'stumbles' during high data transfer rates and/or high volume ram/swap utilization, two common causes are insufficient supply voltages and marginal memory.
No, I think these are OK. It has pretty good Crucial memory, and a 450W power supply. I suspect I just have to bite the bullet and reinstall, but thanks anyway. Kevin -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com