Ocena wątku:
  • 0 głosów - średnia: 0
  • 1
  • 2
  • 3
  • 4
  • 5
Czy da się sformatować dysk przenośny na ext?
#3
0
Kod:
[ 3.253225] usb 1-1: New USB device found, idVendor=0781, idProduct=55b0, bcdDevice= 3.05
[ 3.253236] usb 1-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 3.253240] usb 1-1: Product: Portable SSD
[ 3.253243] usb 1-1: Manufacturer: SanDisk
[ 3.253247] usb 1-1: SerialNumber: 32323034474D343032383436
[ 3.328111] input: Synaptics TM3336-001 as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-SYNA2B49:00/0018:06CB:8251.0001/input/input5
[ 3.328327] hid-rmi 0018:06CB:8251.0001: input,hidraw0: I2C HID v1.00 Mouse [SYNA2B49:00 06CB:8251] on i2c-SYNA2B49:00
[ 3.376970] usb 2-3: new SuperSpeed USB device number 2 using xhci_hcd
[ 3.403547] usb 2-3: New USB device found, idVendor=05e3, idProduct=0616, bcdDevice= 4.01
[ 3.403560] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0

[32851.921131] usb 1-1: new high-speed USB device number 9 using xhci_hcd
[32852.071883] usb 1-1: New USB device found, idVendor=0781, idProduct=55b0, bcdDevice= 3.05
[32852.071898] usb 1-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[32852.071905] usb 1-1: Product: Portable SSD
[32852.071910] usb 1-1: Manufacturer: SanDisk
[32852.071915] usb 1-1: SerialNumber: 32323034474D343032383436
[32852.081944] scsi host2: uas
[32852.089456] scsi 2:0:0:0: Direct-Access SanDisk Portable SSD 0305 PQ: 0 ANSI: 6
[32852.092692] scsi 2:0:0:1: Enclosure SanDisk SES Device 0305 PQ: 0 ANSI: 6
[32852.096942] sd 2:0:0:0: Attached scsi generic sg1 type 0
[32852.099111] ses 2:0:0:1: Attached Enclosure device
[32852.099504] ses 2:0:0:1: Attached scsi generic sg2 type 13
[32852.117440] ses 2:0:0:1: Wrong diagnostic page; asked for 1 got 8
[32852.117464] ses 2:0:0:1: Failed to get diagnostic page 0x1
[32852.117479] ses 2:0:0:1: Failed to bind enclosure -19
[32852.119148] sd 2:0:0:0: [sdb] 1953523712 512-byte logical blocks: (1.00 TB/932 GiB)
[32852.119163] sd 2:0:0:0: [sdb] 4096-byte physical blocks
[32852.119529] sd 2:0:0:0: [sdb] Write Protect is off
[32852.119540] sd 2:0:0:0: [sdb] Mode Sense: 5f 00 10 00
[32852.120298] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
[32852.120943] sd 2:0:0:0: [sdb] Optimal transfer size 1048576 bytes
[32852.161868] sdb: sdb1
[32852.190162] sd 2:0:0:0: [sdb] Attached SCSI disk
[32852.685207] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: errors=remount-ro. Quota mode: none.
[32890.014640] perf: interrupt took too long (3982 > 3971), lowering kernel.perf_event_max_sample_rate to 50000
[33138.640299] usb 1-1: USB disconnect, device number 9
[33138.641478] blk_update_request: I/O error, dev sdb, sector 973343896 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0
[33138.641517] Aborting journal on device sdb1-8.
[33138.641552] blk_update_request: I/O error, dev sdb, sector 973342720 op 0x1:(WRITE) flags 0x20800 phys_seg 1 prio class 0
[33138.641568] Buffer I/O error on dev sdb1, logical block 121667584, lost sync page write
[33138.641852] JBD2: Error -5 detected when updating journal superblock for sdb1-8.
[33138.643052] blk_update_request: I/O error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
[33138.685558] sd 2:0:0:0: [sdb] Synchronizing SCSI cache
[33138.749433] blk_update_request: I/O error, dev sdb, sector 76976 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[33138.753463] EXT4-fs error (device sdb1): ext4_journal_check_start:83: comm ext4lazyinit: Detected aborted journal
[33138.753475] EXT4-fs (sdb1): Remounting filesystem read-only
[33138.758588] EXT4-fs error (device sdb1): __ext4_find_entry:1662: inode #2: comm doublecmd: reading directory lblock 0
[33138.758774] blk_update_request: I/O error, dev sdb, sector 76976 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[33138.758798] EXT4-fs error (device sdb1): __ext4_find_entry:1662: inode #2: comm doublecmd: reading directory lblock 0
[33138.789505] blk_update_request: I/O error, dev sdb, sector 76976 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[33138.789662] EXT4-fs error (device sdb1): __ext4_find_entry:1662: inode #2: comm doublecmd: reading directory lblock 0
[33138.789797] blk_update_request: I/O error, dev sdb, sector 76976 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[33138.789805] EXT4-fs error (device sdb1): __ext4_find_entry:1662: inode #2: comm doublecmd: reading directory lblock 0
[33138.941513] sd 2:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[33139.801829] EXT4-fs error (device sdb1): __ext4_find_entry:1662: inode #2: comm doublecmd: reading directory lblock 0
[33139.801926] EXT4-fs error (device sdb1): __ext4_find_entry:1662: inode #2: comm doublecmd: reading directory lblock 0
[33144.961589] usb 2-1: new SuperSpeed USB device number 3 using xhci_hcd
[33144.986778] usb 2-1: New USB device found, idVendor=0781, idProduct=55b0, bcdDevice= 3.05
[33144.986794] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[33144.986801] usb 2-1: Product: Portable SSD
[33144.986807] usb 2-1: Manufacturer: SanDisk
[33144.986812] usb 2-1: SerialNumber: 32323034474D343032383436
[33144.995056] scsi host2: uas
[33144.996265] scsi 2:0:0:0: Direct-Access SanDisk Portable SSD 0305 PQ: 0 ANSI: 6
Odpowiedz


Wiadomości w tym wątku
RE: Czy da się sformatować dysk przenośny na ext? - przez AndrzejB - 26-09-2023, 21:48

Skocz do:




Użytkownicy przeglądający ten wątek: 1 gości