On Tue, 13 Jun 2006, Kyle Davenport wrote: > being sensitive to inadequate power supplies, so I tried it on a server > box.
you mean: you've put your faulty disk in another box? (to exclude cabling, power, controller, memory issues?) > fsck.jfs version 1.1.7, 22-Jul-2004 Please try to use a current version of jfsutils: http://jfs.sourceforge.net/project/pub/jfsutils-1.1.11.tar.gz > Unrecoverable error reading M from /dev/hdc1. CANNOT CONTINUE. > Fatal error (-10015,30) accessing the filesystem (1,2702950400,16384,0). > processing terminated: 6/13/2006 22:55:09 with return code: -10015 exit > code: 8. Are there any errors in the kernel log? If you have enough space, I'd suggest that you dd/dd_rescue your data off the disk and keep an eye on the syslog for i/o errors. as always: if there are hardware errors (disk, cabling, etc...) the filesystem can't do much about it. > there's a bunch of "READ DMA EXT" errors in SMART. Guessing it's worse > than just bad blocks... if the disk starts to die, best thing is to get a new one if the data on it is important... Christian. -- BOFH excuse #293: You must've hit the wrong any key. _______________________________________________ Jfs-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
