1 |
On 01/02/12 22:19, Dale wrote: |
2 |
> Colleen Beamer wrote: |
3 |
>> On 01/02/12 14:42, Michael Mol wrote: |
4 |
>>> On Mon, Jan 2, 2012 at 2:32 PM, Colleen |
5 |
>>> Beamer<colleen.beamer@×××××.com> wrote: |
6 |
>>>> On 01/02/12 04:57, Mick wrote: |
7 |
>>>>> On Monday 02 Jan 2012 02:25:45 Colleen Beamer wrote: |
8 |
>>>>>> On 01/01/12 20:29, Mark Knecht wrote: |
9 |
>>>>>>> On Sun, Jan 1, 2012 at 5:20 PM, Colleen Beamer |
10 |
>>>>>>> <colleen.beamer@×××××.com> |
11 |
>>>>> wrote: |
12 |
>>>>>>>> On 01/01/12 20:13, Mark Knecht wrote: |
13 |
>>> [snip] |
14 |
>>> |
15 |
>>>>> Since there were no updates/upgrades immediately prior to this |
16 |
>>>>> error, this |
17 |
>>>>> could well have been a result of fs corruption, or memory |
18 |
>>>>> problems. It |
19 |
>>>>> would |
20 |
>>>>> make sense to check what smartctl -a /dev/sda shows just in case. |
21 |
>>>> I'd be willing to try this, but what is smartctl a part of? |
22 |
>>> "smartctl -a" asks the hard disk device for diagnostic information. |
23 |
>> Yes, but when I ran 'smartctl -a /dev/sda' it tells me the command isn't |
24 |
>> found. I did a search for this command and it was found in |
25 |
>> /usr/share/bash-completion/ but if I run it (and it is executable to |
26 |
>> owner (root)), using the full path to the command, it tells me the |
27 |
>> command isn't found. I also tried creating a symlink to it in /usr/bin |
28 |
>> and I get the message: |
29 |
>> /usr/bin/smartctl: line 3: have: command not found. |
30 |
>> |
31 |
>> Regards, |
32 |
>> |
33 |
>> Colleen |
34 |
>> |
35 |
> |
36 |
> emerge smartmontools |
37 |
> |
38 |
> then when that is done, do this: |
39 |
> |
40 |
> smartctl -t long /dev/sd<drive letter here> |
41 |
> |
42 |
> When you do that, it should print a message that tells when the test |
43 |
> will complete. It is usually a 24 hour format thing too. This can |
44 |
> run while the drive is in use too. Sometime after that time, run this |
45 |
> command: |
46 |
> |
47 |
> smartctl -l selftest /dev/sd<drive letter here> |
48 |
> |
49 |
> That should tell you the results of the test. If it says it passed, |
50 |
> this is good. If it reports a problem, well it is not good. If you |
51 |
> are lucky, it will be like a recent problem I had and reformatting |
52 |
> will fix it. It was a weird problem but beats replacing a drive. |
53 |
|
54 |
Thanks, Dale. I'll try this. Don't know if I'll get to it tonight .... |
55 |
unfortunately, it was back to work to day and I have a bunch of stuff to |
56 |
do tonight. |
57 |
|
58 |
To everyone else, thanks ... I'll keep googling to see if I can figure |
59 |
this out and I'll shout again if I need assistance. |
60 |
|
61 |
Regards, |
62 |
|
63 |
Colleen |
64 |
|
65 |
|
66 |
-- |
67 |
|
68 |
Registered Linux User #411143 with the Linux Counter, http://counter.li.org |