Re: [expert] ML9.0:file system completely crashed ext3,could notfind mime type,kde3.0.3
e2fsck -f -c /dev/hdX can do it for you now, make sure you are in single user mode though and your HD is mounted ro. I already reinstalled ML9.0, but I tried on this new install e2fsck -f -c /dev/hda2: and it returned a bunch of errors. And this is after a fresh install. I'll complain about this in another thread. If they were badblock errors your HD has failed, replace it and your problems might go away. JG Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] ML9.0:file system completely crashed ext3,could notfind mime type,kde3.0.3
hi vatbier, vatbier wrote: civileme [EMAIL PROTECTED] wrote: The X66 is safe to use as you have described it. What is dangerous is overdriving. hdparm -k1 -d1 -X66 /dev/hda (66:UDMA2) I guess you mean if I change the hard drive setting with DataLifeGuard and then do hdparm -d1 X69 (69:UDMA5) that this is dangerous, or if I try to set it to UDMA6 (:133Mhz)? Mandrake 9.0 uses UDMA5 automatically (without program hdparm), is this configured on booting are is it written at installation of ML9.0 in some configuration file? mdk9 does not use UDMA5 by default. Your HD/BIOS initalise themselves to what they consider to be the fastest stable speed and setttings etc less /etc/sysconfig/harddisks You can override what mdk9 has in that file to change stuff, default is often very slow. What program in Mandrake 9.0 is responsible for this, or is it just the kernel that figures out what the highest UDMA setting is? man hdparm Also, IIRC, DataLifeGuard phones home and gives you warning if your drive is about to fail (and it works on non-WDs too). DataLifeGuard is just an utility on a floppy disk, or does it install a phone home program in Windows XP? As for the variance of speed, consider this... Ok, then I'll probably set it with hdparm to UDMA2. Hm, where is the -k1 option for hdparm written to? man hdparm doesn't talk about a configuration file. it doesnt, you have to have it in /etc/sysconfg/hardisks or somewhere like /etc/rc.d/rc.local etc a secondary cosmic ray is a significant noise source. Not much charge moves on those cables at the interface voltage in that time span. secondary cosmic ray: didn't know it was that delicate, how are IDE-cables protected on the Space Station and what speed would they have? They dont use WD drives for sure :)) i bet they use extra CRC checks on all their comms too. You can download an ATA66 disable utility (windows compatible) for your WD. I think this utility is also on the DataLifeGuard floppy disk dlgudma.exe - Data Lifeguard Ultra ATA Management I'm not sure why are considering this program as it will never work on GNU/Linux or GNU/Wine. Something else I wonder: A lot of system files (e.g. /usr/bin/play) disappeared, they were cleared because of corruption (bad mode,deleted/unused inode,illegal character device,...). Did the corruption occur with these messages in syslog: EXT3-fs error (device ide0(3,2)): ext3_new_block: Allocating block in system zone - block = 294914 ? What do these messages mean? Did you install with a search for badblocks? e2fsck -f -c /dev/hdX can do it for you now, make sure you are in single user mode though and your HD is mounted ro. Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] ML9.0:file system completely crashed ext3,could notfind mime type,kde3.0.3
snip I don't have a 40-pin cable. If I use the hdparm command hdparm -k1 -d1 -X66 /dev/hda (66:UDMA2), would this give the same effect? Can changing the UDMA setting with hdparm give problems/errors? I also downloaded from the WDC website Data Lifeguard Tools that can change the udma setting on the hard drive itself. If I used this to change the UDMA to 2, would my linux have no problems with this (I'm a a little scared to use hdparm or WDC tools, in man hdparm they state Use with extreme caution! This feature includes zero protection for the unwary, and an unsuccessful outcome may result in severe filesystem corruption!) ? /snip I have had this happen a while back with a couple of cases of ASUS boards we got in. Install the boxes load up the OS... all was fine... then suddenly the box couldn't find the hdd or if it did it reported the drive as corrupted and fsck needed to be run. IF you did run fsck the data then did become corrupt. But (as we found out by accident) you would touch the ribbon cable all would be well again. Seems that ASUS got a bad lot of ribbon cables and was very happy when we called up wanting them to replace the cables (Everyone else was blaming the whole mobo!) They did and the problems went away. The wires are thin and they are pressed by machine... alignment can be off. James Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] ML9.0:file system completely crashed ext3,could notfind mime type,kde3.0.3
On Wed, 2003-02-12 at 07:57, civileme wrote: pair was a WD. (As an aside from this, if you have enough IDE channels to do it, put one hard drive per channel and use the other (slave) side for CDROM or Zip or whatever, not only to avoid crosstalk but for efficient operation.) Hi civilme, Is this true when the slave does not function in DMA mode, or at a much lower DMA mode? I've heard that IDE defaults to the mode of the slowest device on the channel. What is you experience with this? Thanks very much, Damon -- Damon Lynch [EMAIL PROTECTED] Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] ML9.0:file system completely crashed ext3,could notfind mime type,kde3.0.3
I've had similar results but specifically when it's a maxtor drive and a non maxtor in the slave position. They didn't play nice at all. Now if I had the Maxtor paired up with another one running the same DMA level... no problem. James On Tue, 2003-02-11 at 13:11, Dave Laird wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Good afternoon, Anne... On Tuesday 11 February 2003 12:53 pm, Anne Wilson wrote: There's an old saying The faster the master, The slower the slave It wouldn't matter which way round if you were right. Actually about six months back or so I did a relative speed test using a series of different UDMA drives on an enhanced system under various O/S platforms to see if anything had changed since the last time. Under *certain* conditions, that axiom no longer applies. However, I also willingly admit, despite doing a *lot* of skull-banging, I haven't figured out why, or for that matter, what has changed in how hard drive parameters are recognized under Linux. For example, under Mandrake using a fast high-speed 40 gigabyte drive, in approximately 40% of the time it was recognized by Mandrake as a fast drive, and deployed appropriately. If the slave was *also* a UDMA drive, it, too, was configured correctly. Even a lowly Iomega Zip Drive was configured as a fast access drive. Go figure, sez I. I even tried it using several different brands of drives, since I was neither scientific nor exacting about it. sigh When it worked it was a thing of marvel. However, just now having stuck my foot so nicely into my mouth, I couldn't then account for the other 60% of the time when one or both drives were recognized and configured as pokey slow EIDE drives. I repeated this test four or five times, and even had a fast drive be recognized two *different* ways several times. I know instinctively it is in the libraries somewhere, but I don't have a clue. FWIW, I was able to replicate the same test results using Micro$oft Windoze 98 and backwards a time or two. For the most part, Windows 98 Second Edition and upwards recognizes the drive geometry correctly every time. sigh Can I buy an axiom now? grin Dave - -- Dave Laird ([EMAIL PROTECTED]) The Used Kharma Lot / The Phoenix Project Web Page: http://www.kharma.net updated 01/20/2003 Usenet News server: news.kharma.net Musicians Calendar and Database access: http://www.kharma.net/calendar.html An automatic random thought For the Minute: Reality is for people who lack imagination. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+SWccaE1ENZP1A28RApucAKCt/8hp17uC1Z7XvEXAbOcOdG/vaQCcDXAK kRoHv4eh7qTWjLR+GL/C9Lc= =VQIe -END PGP SIGNATURE- __ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] ML9.0:file system completely crashed ext3,could notfind mime type,kde3.0.3
On Wed, 2003-02-12 at 09:53, Anne Wilson wrote: It wouldn't matter which way round if you were right. It still may matter. But I don't know - that's why I am asking :-) Supposing you have a UDMA 100 as master, and a UDMA 33 as slave. Conceivably they may both drop down to UDMA 33, and the master runs a bit faster than the slave simply because it is the master. Maybe that is not what will happen. Either way, I'm curious to know what the experts think! I've heard conflicting stories from different folks (mostly off this list). Damon -- Damon Lynch [EMAIL PROTECTED] Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
