Pages : 1
#1 Le 07/06/2025, à 12:47
- visual1956
problème avec rsync
bonjour,
je viens d'acheter un disque externe de 4To pour sauvegarder les différentes photos que j'ai sur mon disque interne et sur d'autres disques externes.
Pour copier ces photos j'utilise la commande " rsync -av /répertoire d'origine / répertoire de destination"
lorsque je lance la commande tout se passe bien et le terminal affiche les fichiers copiés tout en me permettant de travailler par ailleurs.
Comme le nombre de fichiers est important je laisse tourner l'ordinateur la nuit. Au matin je remarque que je n'ai plus accès ni au clavier ni à la souris et le terminal semble être figé sur la référence d'un fichier.
je sais que le transfert est partiel car après avoir relancé l'ordinateur le nombre de fichiers dans le répertoire de destination est inférieur au nombre de fichier du répertoire source
j'ai retiré la fonction de mise en veille mais cela ne modifie en rien la situation
je suis sous Ubuntu 24.02 .2
par avance merci
Hors ligne
#2 Le 07/06/2025, à 12:49
- geole
Re : problème avec rsync
Bonjour
relance ta commande
Donne aussi l'état du disque externe ( chapitres 1 et 3)
Dernière modification par geole (Le 07/06/2025, à 12:51)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#3 Le 07/06/2025, à 13:06
- ylag
Re : problème avec rsync
Bonjour,
"... le terminal semble être figé sur la référence d'un fichier"
Il se pourrait que ce fichier en particulier soit corrompu et bloque le fonctionnement de la commande rsync ?
Essaie peut-être de l'exclure de la sauvegarde, ou bien de le déplacer ailleurs manuellement ?
Peut-être de l'information à obtenir sur ce fichier avec une commande du genre de :
file /chemin/vers/fichier-en-questionA+
Dernière modification par ylag (Le 07/06/2025, à 14:00)
Hors ligne
#4 Le 07/06/2025, à 15:24
- visual1956
Re : problème avec rsync
bonjour
voici la réponse SMARTMONTOOLS
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.8.0-60-generic] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
Read Device Identity failed: scsi error unsupported field in scsi command
If this is a USB connected device, look at the various --device=TYPE variants
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.par contre l'utilitaire "Disque "reconnait bien le disque dur avec une capacité de 4To format ext4
autre commande
patricia@patricia-MS-7895:~$ sudo smartctl -s on -a -d machin-truc /dev/sdb
[sudo] Mot de passe de patricia :
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.8.0-60-generic] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
/dev/sdb: Unknown device type 'machin-truc'
=======> VALID ARGUMENTS ARE: ata, scsi[+TYPE], nvme[,NSID], sat[,auto][,N][+TYPE], usbasm1352r,N, usbcypress[,X], usbjmicron[,p][,x][,N], usbprolific, usbsunplus, sntasmedia, sntjmicron[,NSID], sntrealtek, jmb39x[-q],N[,sLBA][,force][+TYPE], jms56x,N[,sLBA][,force][+TYPE], areca,N/E, 3ware,N, hpt,L/M/N, megaraid,N, aacraid,H,L,ID, sssraid,E,S, cciss,N, auto, test <=======
Use smartctl -h to get a usage summary
patricia@patricia-MS-7895:~$ j'avoue que cette réponse dépasse largement mes compétence
Hors ligne
#5 Le 07/06/2025, à 16:13
- geole
Re : problème avec rsync
Essaie
sudo smartctl -s on -d scsi -T verypermissive -a /dev/sdbsudo smartctl -s on -d ata -T verypermissive -a /dev/sdbAs-tu aussi essayé de déplacer le fichier manuellement?
cp -av "/répertoire d'origine/LeFichierQuiBloque" "/répertoire de destination"Dernière modification par geole (Le 07/06/2025, à 19:28)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#6 Le 07/06/2025, à 19:18
- Tawal
Re : problème avec rsync
Attention !
Sur la commande cp, il y a un guillemet qui traîne à la fin, même si cette commande n'est qu'un 'template'.
Dernière modification par Tawal (Le 07/06/2025, à 19:19)
Le savoir n'a d’intérêt que si on le transmet.
Useless Use of Cat Award
Filenames and Pathnames in Shell: How to do it Correctly
Why not 'ls' in script ?
Hors ligne
#7 Le 07/06/2025, à 19:29
- geole
Re : problème avec rsync
Merci.
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#8 Le 08/06/2025, à 12:53
- visual1956
Re : problème avec rsync
bonjour
après avoir relance la commande sync j'ai identifié le fichier problématique; C'est un fichier de type ".Js" Je l'ai supprimé et cela a débloquer la situation
Encore merci
Hors ligne
#9 Le 09/06/2025, à 10:07
- geole
Re : problème avec rsync
Bonjour
relance ta commande
Donne aussi l'état du disque externe interne (chapitres 1 et 3)
Dernière modification par geole (Le 09/06/2025, à 10:08)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#10 Le 10/06/2025, à 13:30
- visual1956
Re : problème avec rsync
bonjour
j'ai de nouveau le même problème; Ayant un autre ordinateur avec Ubuntu j'ai relancé ma commande rsync avec ce dernier et cela se passe bien. Mon problème semble donc lié à mon premier ordinateur.
voici le retour de smartmontool pour les disques
patricia@patricia-MS-7895:~$ sudo smartctl -s on -a -d machin-truc /dev/sda
[sudo] Mot de passe de patricia :
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.8.0-60-generic] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
/dev/sda: Unknown device type 'machin-truc'
=======> VALID ARGUMENTS ARE: ata, scsi[+TYPE], nvme[,NSID], sat[,auto][,N][+TYPE], usbasm1352r,N, usbcypress[,X], usbjmicron[,p][,x][,N], usbprolific, usbsunplus, sntasmedia, sntjmicron[,NSID], sntrealtek, jmb39x[-q],N[,sLBA][,force][+TYPE], jms56x,N[,sLBA][,force][+TYPE], areca,N/E, 3ware,N, hpt,L/M/N, megaraid,N, aacraid,H,L,ID, sssraid,E,S, cciss,N, auto, test <=======
Use smartctl -h to get a usage summary
patricia@patricia-MS-7895:~$ sudo smartctl -s on -a -d machin-truc /dev/sdb
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.8.0-60-generic] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
/dev/sdb: Unknown device type 'machin-truc'
=======> VALID ARGUMENTS ARE: ata, scsi[+TYPE], nvme[,NSID], sat[,auto][,N][+TYPE], usbasm1352r,N, usbcypress[,X], usbjmicron[,p][,x][,N], usbprolific, usbsunplus, sntasmedia, sntjmicron[,NSID], sntrealtek, jmb39x[-q],N[,sLBA][,force][+TYPE], jms56x,N[,sLBA][,force][+TYPE], areca,N/E, 3ware,N, hpt,L/M/N, megaraid,N, aacraid,H,L,ID, sssraid,E,S, cciss,N, auto, test <=======
Use smartctl -h to get a usage summary
patricia@patricia-MS-7895:~$ sudo smartctl -s on -a -d machin-truc /dev/sdc
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.8.0-60-generic] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
/dev/sdc: Unknown device type 'machin-truc'
=======> VALID ARGUMENTS ARE: ata, scsi[+TYPE], nvme[,NSID], sat[,auto][,N][+TYPE], usbasm1352r,N, usbcypress[,X], usbjmicron[,p][,x][,N], usbprolific, usbsunplus, sntasmedia, sntjmicron[,NSID], sntrealtek, jmb39x[-q],N[,sLBA][,force][+TYPE], jms56x,N[,sLBA][,force][+TYPE], areca,N/E, 3ware,N, hpt,L/M/N, megaraid,N, aacraid,H,L,ID, sssraid,E,S, cciss,N, auto, test <=======
Use smartctl -h to get a usage summary
patricia@patricia-MS-7895:~$ pourquoi cette réponse "type : machin-truc
Dernière modification par visual1956 (Le 10/06/2025, à 13:39)
Hors ligne
#11 Le 10/06/2025, à 14:34
- geole
Re : problème avec rsync
Bonjour
Identifions les disques
lsblk -d | grep -Ev "NAME|loop|sr0|zram"Le disque interne est très probablement le premier de la liste
Donne le retour de
sudo smartctl -s on -a /dev/sdaPour Info, Machin-truc n'est pas prévu comme option, comme tu peux le constater.
smartctl -h
.....
-d TYPE, --device=TYPE
Specify device type to one of:
ata, scsi[+TYPE], nvme[,NSID], sat[,auto][,N][+TYPE], usbasm1352r,N, usbcypress[,X], usbjmicron[,p][,x][,N], usbprolific, usbsunplus, sntasmedia, sntjmicron[,NSID], sntrealtek, jmb39x[-q],N[,sLBA][,force][+TYPE], jms56x,N[,sLBA][,force][+TYPE], areca,N/E, 3ware,N, hpt,L/M/N, megaraid,N, aacraid,H,L,ID, sssraid,E,S, cciss,N, auto, testman smartctl
.....
-d TYPE, --device=TYPE
Specifies the type of the device. The valid arguments to this option are:
auto - attempt to guess the device type from the device name or from controller type info provided by the operating system or from a
matching USB ID entry in the drive database. This is the default.
-d TYPE, --device=TYPE
test - prints the guessed TYPE, then opens the device and prints the (possibly changed) TYPE name and then exits without performing
any further commands.
ata - the device type is ATA. This prevents smartctl from issuing SCSI commands to an ATA device.
scsi - the device type is SCSI. This prevents smartctl from issuing ATA commands to a SCSI device.
nvme[,NSID] - the device type is NVM Express (NVMe). The optional parameter NSID specifies the namespace id (in hex) passed to the
driver. Use 0xffffffff for the broadcast namespace id. The default for NSID is the namespace id addressed by the device name.
sat[,auto][,N] - the device type is SCSI to ATA Translation (SAT). This is for ATA disks that have a SCSI to ATA Translation Layer
(SATL) between the disk and the operating system. SAT defines two ATA PASS THROUGH SCSI commands, one 12 bytes long and the other 16
bytes long. The default is the 16 byte variant which can be overridden with either '-d sat,12' or '-d sat,16'.
If '-d sat,auto' is specified, device type SAT (for ATA/SATA disks) is only used if the SCSI INQUIRY data reports a SATL (VENDOR:
"ATA "). Otherwise device type SCSI (for SCSI/SAS disks) is used.
usbasm1352r,PORT - [NEW EXPERIMENTAL SMARTCTL 7.4 FEATURE] this device type is for one or two SATA disks that are behind an ASMedia
ASM1352R USB to SATA (RAID) bridge. The parameter PORT (0 or 1) selects the disk to monitor.
Note: This USB bridge also supports '-d sat'. This monitors either the first disk or the second disk if no disk is connected to the
first port.
usbcypress - this device type is for ATA disks that are behind a Cypress USB to PATA bridge. This will use the ATACB proprietary
scsi pass through command. The default SCSI operation code is 0x24, but although it can be overridden with '-d usbcypress,0xN',
where N is the scsi operation code, you're running the risk of damage to the device or filesystems on it.
usbjmicron[,p][,x][,PORT] - this device type is for SATA disks that are behind a JMicron USB to PATA/SATA bridge. The 48-bit ATA
commands (required e.g. for '-l xerror', see below) do not work with all of these bridges and are therefore disabled by default.
These commands can be enabled by '-d usbjmicron,x'. If two disks are connected to a bridge with two ports, an error message is
printed if no PORT (0 or 1) is specified.
The PORT parameter is not necessary if the device uses a port multiplier to connect multiple disks to one port. The disks appear un‐
der separate /dev/ice names then.
CAUTION: Specifying ',x' for a device which does not support it results in I/O errors and may disconnect the drive. The same applies
if the specified PORT does not exist or is not connected to a disk.
The Prolific PL2507/3507 USB bridges with older firmware support a pass-through command similar to JMicron and work with '-d usbjmi‐
cron,0'. Newer Prolific firmware requires a modified command which can be selected by '-d usbjmicron,p'. Note that this does not
yet support the SMART status command.
usbprolific - this device type is for SATA disks that are behind a Prolific PL2571/2771/2773/2775 USB to SATA bridge.
usbsunplus - this device type is for SATA disks that are behind a SunplusIT USB to SATA bridge.
sntasmedia - [NEW EXPERIMENTAL SMARTCTL 7.3 FEATURE] this device type is for NVMe disks that are behind an ASMedia USB to NVMe
bridge.
sntjmicron[,NSID] - this device type is for NVMe disks that are behind a JMicron USB to NVMe bridge. The optional parameter NSID
specifies the namespace id (in hex) passed to the driver. The default namespace id is the broadcast namespace id (0xffffffff).
sntrealtek - this device type is for NVMe disks that are behind a Realtek USB to NVMe bridge.
marvell - [Linux only] (deprecated and subject to remove).
megaraid,N - [FreeBSD and Linux only] the device consists of one or more SCSI/SAS disks connected to a MegaRAID controller. The non-
negative integer N (in the range of 0 to 127 inclusive) denotes which disk on the controller is monitored. This interface will also
work for Dell PERC controllers. Use syntax such as:
smartctl -a -d megaraid,2 /dev/sda
smartctl -a -d megaraid,0 /dev/sdb
smartctl -a -d megaraid,0 /dev/bus/0
It is possible to set RAID device name as /dev/bus/N, where N is a SCSI bus number.
The following entry in /proc/devices must exist:
For PERC2/3/4 controllers: megadevN
For PERC5/6 controllers: megaraid_sas_ioctlN
aacraid,H,L,ID - [Linux, Windows and Cygwin only] the device consists of one or more SCSI/SAS or SATA disks connected to an AacRaid
controller. The non-negative integers H,L,ID (Host number, Lun, ID) denote which disk on the controller is monitored. Use syntax
such as:
smartctl -a -d aacraid,0,0,2 /dev/sda
smartctl -a -d aacraid,1,0,4 /dev/sdb
Option '-d sat,auto+...' is implicitly enabled to detect SATA disks. Use '-d scsi+aacraid,H,L,ID' to disable it.
On Linux, the following entry in /proc/devices must exist: aac. Character device nodes /dev/aacH (H=Host number) are created if re‐
quired.
3ware,N - [FreeBSD and Linux only] the device consists of one or more ATA disks connected to a 3ware RAID controller. The non-nega‐
tive integer N (in the range from 0 to 127 inclusive) denotes which disk on the controller is monitored. Use syntax such as:
smartctl -a -d 3ware,2 /dev/sda [Linux only]
smartctl -a -d 3ware,0 /dev/twe0
smartctl -a -d 3ware,1 /dev/twa0
smartctl -a -d 3ware,1 /dev/twl0 [Linux only]
smartctl -a -d 3ware,1 /dev/tws0 [FreeBSD only]
The first two forms, which refer to devices /dev/sda-z (deprecated) and /dev/twe0-15, may be used with 3ware series 6000, 7000, and
8000 series controllers that use the 3x-xxxx driver. The devices /dev/twa0-15, must be used with 3ware 9000 series controllers,
which use the 3w-9xxx driver. The devices /dev/twl0-15 [Linux] or /dev/tws0-15 [FreeBSD] must be used with the 3ware/LSI 9750 series
controllers which use the 3w-sas driver.
Note that if the special character device nodes /dev/tw[ls]?, /dev/twa? and /dev/twe? do not exist, or exist with the incorrect ma‐
jor or minor numbers, smartctl will recreate them on the fly.
areca,N - [FreeBSD, Linux, Windows and Cygwin only] the device consists of one or more SATA disks connected to an Areca SATA RAID
controller. The positive integer N (in the range from 1 to 24 inclusive) denotes which disk on the controller is monitored. On
Linux use syntax such as:
smartctl -a -d areca,2 /dev/sg2
smartctl -a -d areca,3 /dev/sg3
The first line above addresses the second disk on the first Areca RAID controller. The second line addresses the third disk on the
second Areca RAID controller. To help identify the correct device on Linux, use the command:
cat /proc/scsi/sg/device_hdr /proc/scsi/sg/devices
to show the SCSI generic devices (one per line, starting with /dev/sg0). The correct SCSI generic devices to address for smartmon‐
tools are the ones with the type field equal to 3. If the incorrect device is addressed, please read the warning/error messages
carefully. They should provide hints about what devices to use.
Important: the Areca controller must have firmware version 1.46 or later. Lower-numbered firmware versions will give (harmless) SCSI
error messages and no SMART information.
areca,N/E - [FreeBSD, Linux, Windows and Cygwin only] the device consists of one or more SATA or SAS disks connected to an Areca SAS
RAID controller. The integer N (range 1 to 128) denotes the channel (slot) and E (range 1 to 8) denotes the enclosure. Important:
This requires Areca SAS controller firmware version 1.51 or later.
cciss,N - [FreeBSD and Linux only] the device consists of one or more SCSI/SAS or SATA disks connected to a cciss RAID controller.
The non-negative integer N (in the range from 0 to 15 inclusive) denotes which disk on the controller is monitored.
Option '-d sat,auto+...' is implicitly enabled to detect SATA disks. Use '-d scsi+cciss,N' to disable it.
To look at disks behind HP Smart Array controllers, use syntax such as:
smartctl -a -d cciss,0 /dev/cciss/c0d0 (cciss driver under Linux)
smartctl -a -d cciss,0 /dev/sg2 (hpsa or hpahcisr drivers under Linux)
hpt,L/M/N - [FreeBSD and Linux only] the device consists of one or more ATA disks connected to a HighPoint RocketRAID controller.
The integer L is the controller id, the integer M is the channel number, and the integer N is the PMPort number if it is available.
The allowed values of L are from 1 to 4 inclusive, M are from 1 to 128 inclusive and N from 1 to 4 if PMPort available. And also
these values are limited by the model of the HighPoint RocketRAID controller. Use syntax such as:
smartctl -a -d hpt,1/3 /dev/sda (under Linux)
smartctl -a -d hpt,1/2/3 /dev/sda (under Linux)
Note that the /dev/sda-z form should be the device node which stands for the disks derived from the HighPoint RocketRAID controllers
under Linux and under FreeBSD, it is the character device which the driver registered (eg, /dev/hptrr, /dev/hptmv6).
sssraid,E,S - [Linux only: NEW EXPERIMENTAL SMARTCTL 7.4 FEATURE] the device consists of one or more SCSI/SAS or SATA disks connected
to a SSSRAID controller. The non-negative integer E (in the range of 0 to 8) denotes the enclosure and S (range 0 to 128) denotes
the slot. Use syntax such as:
smartctl -a -d sssraid,0,1 /dev/bsg/sssraid0
It is possible to set RAID device name as /dev/bsg/sssraidN, where N is a SCSI bus number.
intelliprop,N[+TYPE] - (deprecated and subject to remove).
jmb39x[-q],N[,sLBA][,force][+TYPE] - the device consists of multiple SATA disks connected to a JMicron JMB39x RAID port multiplier.
The suffix '-q' selects a slightly different command variant used by some QNAP NAS devices. The integer N is the port number from 0
to 4.
WARNING: The ATA pass-through commands are issued via READ/WRITE commands to a LBA of the RAID volume. Using this option with other
devices may overwrite this sector.
The default LBA is 33. The LBA could be selected in the range from 1 to 255 inclusive.
If a GPT partition table is used, LBA 33 contains the last 4 (of 128) entries of the partition table. These entries are zero filled
in most cases. If a MBR partition table is used, LBA 33 may be zero filled or may contain code from a boot loader.
By default, access to the device is refused if the selected sector is not zero filled. The 'force' flag disables this check.
WARNING: Original sector data is not written back if smartctl is aborted with a signal.
jms56x,N[,sLBA][,force][+TYPE] - the device consists of multiple SATA disks connected to a JMicron JMS56x USB to SATA RAID bridge.
See 'jmb39x...' above for valid arguments.Dernière modification par geole (Le 10/06/2025, à 14:48)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
Pages : 1