| Summary: | SSD Disk connected via USB3-SATAII bridge gives Drive Failing warning | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Herbert Poetzl <herbert> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | jani.valimaa, marja11 |
| Version: | Cauldron | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | gnome-disk-utility-2.32.0-1.mga1.src.rpm | CVE: | |
| Status comment: | |||
| Attachments: | smartctl --all -d sat /dev/sdb >/tmp/smartctl.out | ||
|
Description
Herbert Poetzl
2011-05-31 18:52:33 CEST
Created attachment 499 [details] smartctl --all -d sat /dev/sdb >/tmp/smartctl.out Note that smartctl --all /dev/sdb reports: smartctl 5.40 2010-10-16 r3189 [x86_64-mageia-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net /dev/sdb: Unknown USB bridge [0x152d:0x2509 (0x100)] Smartctl: please specify device type with the -d option. Use smartctl -h to get a usage summary I've now attached the SDD directly to the onboard SATA II controller and the issue persists, i.e. smartctl --all /dev/sdb now reports smart values (similar to the attached output) but gnome-disk-utility still reports a Failing Disk, so the USB bridge isn't the one to blame ... @ Herbert Sorry for responding so late Is the problem still there in current cauldron or updated Mageia 1 official? Keywords:
(none) =>
NEEDINFO Herbert, could you please reply to the previous question? There is a maintainer for gnome-disk-utility. If you don't reply, this bug can be closed as OLD two weeks from now Thank you. CC:
(none) =>
jani.valimaa Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD. Status:
NEW =>
RESOLVED |