Re: Interpreting smartctl data -

2017-03-16 Thread Denis Leroy


I had one batch of drives that needed a firmware update.  The drives 
were all in USB cases, but to apply the firmware updates using the 
vendor's utility I had to remove each drive from the USB case and 
install in an old PC.




Yes, that sounds familiar :-)

I did manage to update a couple of Seagates here through USB with 
hdparm, but it took a bit of trickery to figure out the right options 
and to extract the actual firmware binary file from the manufacturer 
downloadables.


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Interpreting smartctl data -

2017-03-16 Thread Denis Leroy

The output looks good to me.


You should be able to run the long test, even through the USB interface. 
Good point about the firmware update, although a quick look on the web 
doesn't indicate an update is available. Many disk drives firmware can 
be updated from Linux with the hdparm tool (hdparm --fwdownload), 
although it may be easier to use the Windows or mac tools provided by 
the manufacturer, if you have those OSes available to you.



On 03/16/2017 11:28 AM, George N. White III wrote:
On 15 March 2017 at 22:09, Bob Goodwin > wrote:


+
Once more, I can read this on my browser, probably should have
tested it that way first time around.

https://da.gd/UTWv ->

https://paste.fedoraproject.org/paste/uz9uxrIQusCNoM9L95xrjl5M1UNdIGYhyRLivL9gydE=/




No cause for concern in this, but the USB interface isn't giving all 
the information.   I'd connect the drive with the
native interface (e.g., put it in a spare system) and run the long 
test.  Another concern is that the drive may have
some custom firmware.  See if you can download a data sheet -- drives 
manufactured to OEM specs for
a specific application seldom have data sheets -- and check for 
firmware updates on the vendor's support site.


--
George N. White III mailto:aa...@chebucto.ns.ca>>
Head of St. Margarets Bay, Nova Scotia


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Interpreting smartctl data -

2017-03-15 Thread Denis Leroy
smartctl is your friend when it comes to evaluating a disk drive health. 
Keep in mind, though, that SMART is not fool proof. Some disk damage may 
not be caught by SMART, but if SMART says your drive is damaged, then it 
probably is.


First, check the overall health status ((replace /dev/sda with the 
approriate disk device in your case):


# smartctl -H /dev/sda

will give you a PASSED or FAILED test. Note that I've seen disks that 
make helicopter sounds and still have a PASSED status. This is not very 
accurate, but the attributes do give interesting values, like the power 
cycle count, or overall power on hours.


A much better overall indicator is the error log. A non-empty error log 
is a huge read flag:


# smartctl -l error /dev/sda

Finally, the best thing to do is to have the disk firmware run a 
self-test. There are two types: short (a few minutes) and long (maybe an 
hour). Run a short test first, then a long test if that passes, to be sure:


# smartctl -t short /dev/sda

Then monitor the result with

# smartctl -l selftest /dev/sda

To run the long test,

# smartctl -t long /dev/sda


Hope this helps.

Denis
(works in storage)

On 03/15/2017 06:37 PM, Bob Goodwin wrote:
I just salvaged the hard drive from an abandoned DirectTV box that 
"smoked." Note: With their approval ...


I'm just trying to determine how much confidence I can have in it. It 
was interesting to see that it was formatted Linux XFS initially. I 
reworked it with gparted and ext4 to test it. Presently it is in a USB 
adapter connected to a USB2 port on this computer. It appears to have 
been running for 2.6+ years, I have a number of drives with at least 
that much time on them and they are still going.


Any thoughts on making sense of smrtctl are appreciated.

Thanks,

Bob



smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.9.13-201.fc25.x86_64] 
(local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, 
www.smartmontools.org


=== START OF INFORMATION SECTION ===
Model Family: Seagate Pipeline HD 5900.2
Device Model: ST3500312CS
Serial Number:5VV9WJQQ
LU WWN Device Id: 5 000c50 0490e4346
Firmware Version: SC13
User Capacity:500,107,862,016 bytes [500 GB]
Sector Size:  512 bytes logical/physical
Rotation Rate:5900 rpm
Device is:In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 2.6, 3.0 Gb/s (current: 1.5 Gb/s)
Local Time is:Wed Mar 15 13:01:12 2017 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled


  9 Power_On_Hours  0x0032   074   074   000Old_age 
Always   -   23096
 10 Spin_Retry_Count0x0013   100   100   097Pre-fail 
Always   -   0
 12 Power_Cycle_Count   0x0032   100   100   020Old_age 
Always   -   85





___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Fedora 25 upgrade woes

2016-11-28 Thread Denis Leroy

On 11/27/2016 11:33 PM, Denis Leroy wrote:

On 11/27/2016 11:20 PM, Matthew Miller wrote:

On Sun, Nov 27, 2016 at 08:48:42PM +0100, Denis Leroy wrote:

Problem still occurs on a fresh install, and /etc/gdm/custom.conf
doesn't actually exist. I guess only lightdm is installed by the
Live distro. Will try on other system.

In this case, it's definitely not Wayland.




As hinted, the culprit appears to be lightdm. Switching to gdm fixes the 
problem.


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Fedora 25 upgrade woes

2016-11-27 Thread Denis Leroy

On 11/27/2016 11:20 PM, Matthew Miller wrote:

On Sun, Nov 27, 2016 at 08:48:42PM +0100, Denis Leroy wrote:

Problem still occurs on a fresh install, and /etc/gdm/custom.conf
doesn't actually exist. I guess only lightdm is installed by the
Live distro. Will try on other system.

In this case, it's definitely not Wayland.


Good to know, thank you.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Fedora 25 upgrade woes

2016-11-27 Thread Denis Leroy

On 11/27/2016 07:50 PM, Matthew Miller wrote:

On Sun, Nov 27, 2016 at 07:24:49PM +0100, Denis Leroy wrote:

Both systems are very different. One is a Lenovo, built-in Intel
graphics support and XFCE, the other is a Dell with a AMD Firepro
M5100 graphics card running Cinnamon. Yet the result is the same. I
assumed Wayland is at fault here, however I noticed both systems
work fine if I boot with an older kernel:

Can you try editing /etc/gdm/custom.conf and uncommenting WaylandEnable=false
as a diagnostic step?



Problem still occurs on a fresh install, and /etc/gdm/custom.conf 
doesn't actually exist. I guess only lightdm is installed by the Live 
distro. Will try on other system.



___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Fedora 25 upgrade woes

2016-11-27 Thread Denis Leroy

Hi List,


So I updated both my Fedora laptops from 24 to 25, resulting in both 
booting into black screens with no login dialogs and no way of going 
into a console or looking at logs.



Both systems are very different. One is a Lenovo, built-in Intel 
graphics support and XFCE, the other is a Dell with a AMD Firepro M5100 
graphics card running Cinnamon. Yet the result is the same. I assumed 
Wayland is at fault here, however I noticed both systems work fine if I 
boot with an older kernel:



kernel-4.8.6-300.fc25.x86_64 : works

kernel-4.8.8-300.fc25.x86_64 : nope


I had some trouble finding further info on this looking at various 
forums and mailing lists, hence my message here. Any insight appreciated.


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Agonizingly slow SATA HDD performance

2010-09-12 Thread Denis Leroy
On 09/13/2010 12:12 AM, Marcus D. Leech wrote:
> I have a new F12 system that is experiencing *agonizingly slow* SATA HDD
> performance, and I
> can't figure out why.  No errors messages at all, just *really slow*.

Sounds like a bad disk to me. Run some diagnostic with smartctl (from 
the smartmontools package). What does 'smartctl -H /dev/sda' return ? 
(replace sda by your disk name if it's different).

What's the content of the error log ? (smartctl -l error /dev/sda) A 
non-empty error log is a good sign the disk is on the down curve.

Next, run a quick self test (smartctl -t short /dev/sda), wait 2 minutes 
then check the result with "smartctl -l selftest".

If that succeeds, run a long test (smart -t long /dev/sda), which takes 
about 2 hours.
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines


Re: cannot erase a CD-RW

2010-09-10 Thread Denis Leroy
On 09/10/2010 10:54 PM, JB wrote:
> Antonio M  gmail.com>  writes:
>
>>
>> It was a long time since my last burn.tonight I wanted to burn a
>> CD-RW but I could not as I could not erase it.
>> I was using K3B or Brasero, and NautilusI could burn a standard CD
>> Running a fully updated F13 with 2.6.34.6-54.fc13.i686.PAE
>>
>
> Hi,
> do it manually.

One can also use cdrdao

 > cdrdao disk-info

 > cdrdao blank --blank-mode minimal
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines


[F-13] Printing regression ?

2010-09-08 Thread Denis Leroy
Hi list,

Woke up this morning to find my printer no longer working. Looks like a 
recent F-13 testing update broke my setup, even though printing has been 
very very stable for me as a rule these past couple of years.

I'm seeing

/var/log/messages:Sep  8 08:26:54 jupiler hpcups[2108]: 
prnt/hpcups/HPCupsFilter.cpp 493: cupsRasterOpen failed, fd = 0


after trying to reconfigure the printer (an HP Photosmart C7280). 
Downgrading the recent ghostscript testing package didn't fix it. I'm 
still looking into it, but has anyone ran into similar problems ?

-denis
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines