| 1 |
Bonjour Vincent, |
| 2 |
|
| 3 |
Tout d'abord merci de ton aide. |
| 4 |
|
| 5 |
Voici le contenu du fstab qui concerne la clé USB : |
| 6 |
/dev/sda1 /mnt/usb vfat user,noauto,umask=077 0 0 |
| 7 |
/dev/sdb1 /mnt/usb2 vfat user,noauto,umask=077 0 0 |
| 8 |
|
| 9 |
|
| 10 |
Et voici ce que j'ai dans les logs (pas très prometteur) : |
| 11 |
|
| 12 |
10:10:17 hub.c: new USB device 00:1f.4-1, assigned address 3 |
| 13 |
10:10:17 WARNING: USB Mass Storage data integrity not assured |
| 14 |
10:11:00 usb.c: USB disconnect on device 00:1f.4-1 address 3 |
| 15 |
10:11:01 hub.c: new USB device 00:1f.4-1, assigned address 4 |
| 16 |
10:11:01 WARNING: USB Mass Storage data integrity not assured |
| 17 |
10:11:15 usb.c: USB disconnect on device 00:1f.4-1 address 4 |
| 18 |
10:11:19 hub.c: new USB device 00:1f.4-1, assigned address 5 |
| 19 |
10:11:19 WARNING: USB Mass Storage data integrity not assured |
| 20 |
10:11:23 usbdevfs: USBDEVFS_CONTROL failed dev 5 rqt 128 rq 6 len |
| 21 |
18 ret -84 |
| 22 |
10:11:23 usbdevfs: USBDEVFS_CONTROL failed dev 5 rqt 128 rq 6 len |
| 23 |
18 ret -110 |
| 24 |
- Last output repeated 47 times - |
| 25 |
10:11:23 usb.c: USB disconnect on device 00:1f.4-1 address 5 |
| 26 |
10:11:23 usbdevfs: USBDEVFS_CONTROL failed dev 5 rqt 128 rq 6 len |
| 27 |
18 ret -110 |
| 28 |
10:11:25 hub.c: new USB device 00:1f.4-2, assigned address 6 |
| 29 |
10:11:25 WARNING: USB Mass Storage data integrity not assured |
| 30 |
10:11:49 usb.c: USB disconnect on device 00:1f.4-2 address 6 |
| 31 |
10:31:21 hub.c: new USB device 00:1f.4-2, assigned address 7 |
| 32 |
10:31:21 WARNING: USB Mass Storage data integrity not assured |
| 33 |
10:31:57 usb.c: USB disconnect on device 00:1f.4-2 address 7 |
| 34 |
10:34:48 smb_trans2_request: result=-104, setting invalid |
| 35 |
10:34:48 smb_retry: successful, new pid=2001, generation=3 |
| 36 |
10:43:39 VFS: Disk change detected on device 08:00 |
| 37 |
10:43:39 sda: Unit Not Ready, sense: |
| 38 |
10:45:41 hub.c: new USB device 00:1f.4-2, assigned address 8 |
| 39 |
10:45:42 WARNING: USB Mass Storage data integrity not assured |
| 40 |
10:51:07 smb_request: result -104, setting invalid |
| 41 |
10:51:07 smb_retry: successful, new pid=2001, generation=4 |
| 42 |
11:10:14 usb.c: USB disconnect on device 00:1f.4-2 address 8 |
| 43 |
11:10:17 hub.c: new USB device 00:1f.4-1, assigned address 9 |
| 44 |
11:10:17 WARNING: USB Mass Storage data integrity not assured |
| 45 |
11:10:20 usbdevfs: USBDEVFS_CONTROL failed dev 9 rqt 128 rq 6 len |
| 46 |
18 ret -110 |
| 47 |
- Last output repeated 102 times - |
| 48 |
11:10:21 usb.c: USB disconnect on device 00:1f.4-1 address 9 |
| 49 |
11:10:21 usbdevfs: USBDEVFS_CONTROL failed dev 9 rqt 128 rq 6 len |
| 50 |
18 ret -110 |
| 51 |
14:05:37 smb_trans2_request: result=-104, setting invalid |
| 52 |
14:05:39 smb_retry: successful, new pid=2001, generation=5 |
| 53 |
14:13:54 VFS: Disk change detected on device 08:00 |
| 54 |
14:13:54 sda: Unit Not Ready, sense: |
| 55 |
14:13:54 sda : READ CAPACITY failed. |
| 56 |
14:13:54 sda: test WP failed, assume Write Enabled |
| 57 |
15:08:11 smb_request: result -104, setting invalid |
| 58 |
15:08:12 smb_retry: successful, new pid=2001, generation=6 |
| 59 |
16:35:57 smb_trans2_request: result=-104, setting invalid |
| 60 |
16:35:58 smb_retry: successful, new pid=2001, generation=7 |
| 61 |
16:44:43 PCI: Found IRQ 11 for device 01:00.0 |
| 62 |
17:03:10 smb_trans2_request: result=-104, setting invalid |
| 63 |
17:03:10 smb_retry: caught signal |
| 64 |
03:04:50 smb_trans2_request: result=-104, setting invalid |
| 65 |
03:04:50 smb_retry: successful, new pid=28849, generation=3 |
| 66 |
03:04:53 smb_trans2_request: result=-104, setting invalid |
| 67 |
03:04:53 smb_retry: successful, new pid=2001, generation=8 |
| 68 |
03:05:05 smb_trans2_request: result=-104, setting invalid |
| 69 |
03:05:05 smb_retry: successful, new pid=28802, generation=2 |
| 70 |
09:01:50 smb_trans2_request: result=-104, setting invalid |
| 71 |
09:01:50 smb_retry: successful, new pid=2001, generation=9 |
| 72 |
09:17:00 smb_trans2_request: result=-104, setting invalid |
| 73 |
09:17:00 smb_retry: successful, new pid=28802, generation=3 |
| 74 |
09:29:50 smb_trans2_request: result=-104, setting invalid |
| 75 |
09:29:51 smb_retry: successful, new pid=28849, generation=4 |
| 76 |
|
| 77 |
Stéphan. |
| 78 |
|
| 79 |
Vincent Rubiolo wrote: |
| 80 |
> Hello Stéphan, |
| 81 |
> |
| 82 |
> En ce qui concerne les périhériques USB, ce sont les scripts hotplug qui se |
| 83 |
> chargent de détecter les insertions de périphériques sur le bus, de trouver la |
| 84 |
> référence du produit et de charger les périphériques correspondants. Tu n'as |
| 85 |
> normalement pas besoin de faire quoi que ce soit. |
| 86 |
> |
| 87 |
> C'est en interne un appel au démon du noyau (kerneld) qui charge/décharge les |
| 88 |
> modules. Il peut aussi être configuré pour retirer les modules du noyau |
| 89 |
> lorsqu'ils ne sont plus utilisés (je crois que la durée est configurable). |
| 90 |
> |
| 91 |
> Dans un premier temps, je te conseille de vérifer/poster ici le contenu de ton |
| 92 |
> fstab et d'indiquer la commande exacte que tu emploies pour monter/démonter tes |
| 93 |
> disques. Un extrait des messages noyaux serait aussi utile (dans /var/log/, IIRC). |
| 94 |
> |
| 95 |
> Je le répète, tout doit être automatique, au pire tu montes le périphérique à la |
| 96 |
> main avec un mount /mnt/clef_usb si tu n'as pas de truc comme automount mais |
| 97 |
> c'est tout. |
| 98 |
> |
| 99 |
> Tiens-moi au courant, |
| 100 |
> |
| 101 |
> Vinz |
| 102 |
> |
| 103 |
|
| 104 |
|
| 105 |
-- |
| 106 |
gentoo-user-fr@g.o mailing list |
Archives