| PLEX86 | ||
|
resize a bad patch out of a parbreastion 7151Jules wrote (in part): Help! Proliferation of applications! 7152 Snip... Rare IMO is buried so many pages deep I have to use a search to find it... I do not have a statistically valid sample, but in my desktop machines (I have had three, but the oldest one has been donated to the deserving poor) had some of each. The oldest came with a 1.6 GByte Western Digital Caviar IDE drive. About 18 months later, I added a 4.3 GByte Western Digital Caviar IDE drive to put Red Hat Linux 5.0 on it. The 1.3 drive was still running 7 years later, but the 4.3 quit after about 5 years. Can someone help me debug my sound setup Hi Using hotplug (and hence not udev) with a 2.6.14.3 custom compiled kernel with modular alsa support. Modules loaded : sndseqdummy 3844 0 sndseqoss 36224 0 sndseqmidi 10528... The next machine came with two 10,000rpm SCSI hard drives in early 1990. They are still in there running fine 5 years later. A year or so ago, I took a slightly used (by me) Maxtor 80GByte Diamond Max 9 drive and put it in there too. I have never been able to get one of these Diamond Max 9 drives to pbutt the Linux badblocks test, even when right out of the box. But they seem to run OK. Makes me nervous, though. This machine has 4 SCSI hard drives and two of those Maxtor 80GByte Diamond Max 9 hard drives. But since I first powered it up in about March 2004, there are not enough hours on it to conclude anything. One of the Diamond Max 9 hard drives got two errors: Help! Proliferation of applications! 7153 On Fri, 09 Dec 2005 15:11:57 +0000, Gordon I've used Pan for Usenet for the last few years and been very happy with it - by... SMART Error Log Version: 1 ATA Error Count: 2 DCR = Device Control Register FR = Features Register SC = Sector Count Register SN = Sector Number Register CL = Cylinder Low Register CH = Cylinder High Register D-H = Device-Head Register CR = Content written to Command Register ER = Error register STA = Status register Timestamp is seconds since the previous disk power-on. Note: timestamp "wraps" after 2^32 msec = 49.710 days. Error 2 occurred at disk power-on lifetime: 2715 hours When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER:40 SC:07 SN:3e CL:cb CH:91 D-H:e1 ST:51 Sequence of commands leading to the command that caused the error were: DCR FR SC SN CL CH D-H CR Timestamp 08 00 08 3e cb 91 e1 c8 1407214.384 08 00 08 a8 b7 db e4 ca 1407214.368 08 00 10 98 b7 db e4 ca 1407214.368 08 00 08 68 fa eb e4 ca 1407214.368 08 00 08 90 b7 db e4 ca 1407214.368 Error 1 occurred at disk power-on lifetime: 2715 hours When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER:40 SC:07 SN:3e CL:cb CH:91 D-H:e1 ST:51 Sequence of commands leading to the command that caused the error were: DCR FR SC SN CL CH D-H CR Timestamp 08 00 08 3e cb 91 e1 c8 1407212.992 08 00 08 16 9e 91 e1 c8 1407212.992 08 00 08 06 9e 91 e1 c8 1407212.992 08 00 08 f6 9d 91 e1 c8 1407212.992 08 00 20 ae 8d 91 e1 c8 1407212.992 But that was long ago, and it seems OK now. -- .~. Jean-David Beyer Registered Linux User 85642. V PGP-Key: 9A2FC99A Registered Machine 241939. ^^-^^ 09:30:00 up 12 days, 20:00, 5 users, load average: 4.18, 4.21, 4.18
|
||||
Help! Proliferation of applications! 7152 Linux groups from Newsgroups The #1 Usenet Provider on the Internet
|
||||