Ir al contenido

josspark

Miembros
  • Contenido

    202
  • Registrado

  • Última Visita

  • Días Ganando

    6

josspark ganó por última vez en Marzo 1

¡josspark tuvo el contenido mejor valorado!

Sobre josspark

  • Rango
    Linuxero
  • Cumpleaños 08/08/1979

Género

  • Género
    Hombre

Características del sistema

  • Distribución
    ArchLinux
  • Entorno gráfico
    Mate
  • Navegador Web
    Firefox
  • Entorno gráfico secundario
    Sin_especificar
  • Navegador Web secundario
    Sin_especificar

Visitantes recientes en el perfil

389 visitas al perfil
  1. Has visto el curve 24" de slimbook??? https://slimbook.es/aio-curve-el-all-in-one-curvo-de-gnu-linux Enviado desde mi Redmi Note 4 mediante Tapatalk
  2. seguimos para bingo... analicé el hdd mediante sudo badblocks -swn /de/sda1 y no me dió ningún error, pero hoy descargando una plei por transmission... [ 1079.645054] usb 1-1.5: reset high-speed USB device number 4 using dwc_otg [ 1086.205608] usb 1-1.5: USB disconnect, device number 4 [ 1086.245058] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 [ 1086.245213] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 00 60 ac 60 00 00 f0 00 [ 1086.245326] print_req_error: I/O error, dev sda, sector 6335584 [ 1086.245536] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 [ 1086.245672] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 00 60 ad 50 00 00 f0 00 [ 1086.245785] print_req_error: I/O error, dev sda, sector 6335824 [ 1086.246346] EXT4-fs warning (device sda1): ext4_end_bio:323: I/O error 10 writing to inode 36438020 (offset 490815488 size 1638400 starting block 792084) [ 1086.246561] Buffer I/O error on device sda1, logical block 791572 [ 1086.246662] Buffer I/O error on device sda1, logical block 791573 [ 1086.246756] Buffer I/O error on device sda1, logical block 791574 [ 1086.246849] Buffer I/O error on device sda1, logical block 791575 [ 1086.246943] Buffer I/O error on device sda1, logical block 791576 [ 1086.247035] Buffer I/O error on device sda1, logical block 791577 [ 1086.247127] Buffer I/O error on device sda1, logical block 791578 [ 1086.247218] Buffer I/O error on device sda1, logical block 791579 [ 1086.247310] Buffer I/O error on device sda1, logical block 791580 [ 1086.247402] Buffer I/O error on device sda1, logical block 791581 [ 1086.248417] EXT4-fs warning (device sda1): ext4_end_bio:323: I/O error 10 writing to inode 36438020 (offset 490815488 size 1638400 starting block 792228) [ 1086.249669] JBD2: Detected IO errors while flushing file data on sda1-8 [ 1086.249790] Aborting journal on device sda1-8. [ 1086.249885] JBD2: Error -5 detected when updating journal superblock for sda1-8. [ 1086.250100] EXT4-fs warning (device sda1): ext4_end_bio:323: I/O error 10 writing to inode 36438020 (offset 202768384 size 147456 starting block 721540) [ 1086.250365] JBD2: Detected IO errors while flushing file data on sda1-8 [ 1086.250474] EXT4-fs error (device sda1): ext4_journal_check_start:61: Detected aborted journal [ 1086.250600] EXT4-fs (sda1): Remounting filesystem read-only [ 1086.250686] EXT4-fs (sda1): previous I/O error to superblock detected [ 1086.250813] EXT4-fs (sda1): ext4_writepages: jbd2_start: 2147483611 pages, ino 36438020; err -30 [ 1086.259696] blk_partition_remap: fail for partition 1 [ 1086.259833] blk_partition_remap: fail for partition 1 [ 1086.259936] blk_partition_remap: fail for partition 1 [ 1086.261651] blk_partition_remap: fail for partition 1 [ 1086.261779] blk_partition_remap: fail for partition 1 [ 1086.459787] blk_partition_remap: fail for partition 1 [ 1086.459898] EXT4-fs error (device sda1): ext4_wait_block_bitmap:504: comm transmission-da: Cannot read block bitmap - block_group = 41, block_bitmap = 1048585 [ 1086.460100] EXT4-fs error (device sda1): ext4_discard_preallocations:4096: comm transmission-da: Error -5 loading buddy information for 41 [ 1086.460551] blk_partition_remap: fail for partition 1 [ 1086.460638] EXT4-fs error (device sda1): ext4_find_entry:1436: inode #24641537: comm transmission-da: reading directory lblock 0 [ 1086.460828] blk_partition_remap: fail for partition 1 [ 1086.460909] EXT4-fs error (device sda1): ext4_find_entry:1436: inode #36438019: comm transmission-da: reading directory lblock 0 [ 1086.461198] blk_partition_remap: fail for partition 1 [ 1086.461279] EXT4-fs error (device sda1): ext4_find_entry:1436: inode #24641537: comm transmission-da: reading directory lblock 0 [ 1086.461458] blk_partition_remap: fail for partition 1 [ 1086.461537] EXT4-fs error (device sda1): ext4_find_entry:1436: inode #36438019: comm transmission-da: reading directory lblock 0 [ 1086.461720] blk_partition_remap: fail for partition 1 [ 1086.461800] EXT4-fs error (device sda1): ext4_find_entry:1436: inode #36438019: comm transmission-da: reading directory lblock 0 [ 1086.461973] blk_partition_remap: fail for partition 1 [ 1086.462052] EXT4-fs error (device sda1): ext4_find_entry:1436: inode #24641537: comm transmission-da: reading directory lblock 0 [ 1086.470976] blk_partition_remap: fail for partition 1 [ 1086.480083] EXT4-fs error (device sda1): ext4_find_entry:1436: inode #24641537: comm transmission-da: reading directory lblock 0 [ 1086.490427] blk_partition_remap: fail for partition 1 [ 1086.500236] EXT4-fs error (device sda1): ext4_find_entry:1436: inode #36438019: comm transmission-da: reading directory lblock 0 [ 1086.509995] blk_partition_remap: fail for partition 1 [ 1086.520062] blk_partition_remap: fail for partition 1 [ 1097.685032] usb 1-1.5: new high-speed USB device number 5 using dwc_otg [ 1097.826169] usb 1-1.5: New USB device found, idVendor=152d, idProduct=2338 [ 1097.839790] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=5 [ 1097.849877] usb 1-1.5: Product: USB to ATA/ATAPI bridge [ 1097.859559] usb 1-1.5: Manufacturer: JMicron [ 1097.868781] usb 1-1.5: SerialNumber: 000001D91861 [ 1097.878877] usb-storage 1-1.5:1.0: USB Mass Storage device detected [ 1097.888737] scsi host1: usb-storage 1-1.5:1.0 [ 1100.950173] scsi 1:0:0:0: Direct-Access WDC WD75 00BPVT-22HXZT1 PQ: 0 ANSI: 5 [ 1103.747521] sd 1:0:0:0: [sdb] 1465149168 512-byte logical blocks: (750 GB/699 GiB) [ 1103.761500] sd 1:0:0:0: [sdb] Write Protect is off [ 1103.771042] sd 1:0:0:0: [sdb] Mode Sense: 28 00 00 00 [ 1103.771363] sd 1:0:0:0: [sdb] No Caching mode page found [ 1103.780929] sd 1:0:0:0: [sdb] Assuming drive cache: write through [ 1103.868936] sdb: sdb1 [ 1103.879642] sd 1:0:0:0: [sdb] Attached SCSI disk [ 1113.195195] blk_partition_remap: fail for partition 1 [ 1113.204075] EXT4-fs warning (device sda1): htree_dirblock_to_tree:977: inode #24641537: lblock 0: comm zsh: error -5 reading directory block [ 1113.213643] blk_partition_remap: fail for partition 1 [ 1113.222982] EXT4-fs error: 2 callbacks suppressed [ 1113.222989] EXT4-fs error (device sda1): ext4_find_entry:1436: inode #24641537: comm zsh: reading directory lblock 0 y luego viene: sudo e2fsck -f -c -v /dev/sda e2fsck 1.44.1 (24-Mar-2018) ext2fs_open2(): Número mágico incorrecto en el superbloque e2fsck: Superbloque es inválido, intentando los bloques de respaldo... e2fsck: Número mágico incorrecto en el superbloque mientras se intentaba abrir /dev/sda El superbloque no se ha podido leer o no describe un sistema de ficheros ext2/ext3/ext4 válido. Si el dispositivo es válido y contiene realmente un sistema de ficheros ext2/ext3/ext4 (y no uno de intercambio, ufs u otra cosa), entonces el superbloque está corrompido; podría intentar ejecutar e2fsck con un superbloque alternativo: e2fsck -b 8193 <dispositivo> o e2fsck -b 32768 <dispositivo> /dev/sda contiene datos `DOS/MBR boot sector; partition 1 : ID=0xee, start-CHS (0x0,0,2), end-CHS (0x3ff,255,63), startsector 1, 1465149167 sectors, extended partition table (last)'
  3. no da errores, alguna otra herramienta? gracias
  4. COMO QUE SLIMBOOK ES VALENCIANA????? DONDE???? A VER SI ME PILLA CERCA...
  5. No se si lo compras directamente en China... pero cuidado con las aduanas si es asi. Pone tienda en España Enviado desde mi Redmi Note 4 mediante Tapatalk
  6. La pantalla de Xiaomi es de 15,6" Enviado desde mi Redmi Note 4 mediante Tapatalk
  7. Hola foreros, pues me he decidido a comprarme un portatil, y ya puestos me he dicho: me tiro la manta al cuello y la casa por la ventana. Mis dos opciones son el slimbook excalibur 2 contra el xiaomi notebook air. El slimbook no está disponible, con lo cual tengo que esperar, que no me importa mucho, y estas serían sus especificaciones: https://slimbook.es/pedidos/slimbook-excalibur/excalibur-2-intel-i7-comprar corei7, 16gb de ram, sdd 256gb gráfica no la especifica pero es nvidia de 2gb -> 1.200€ https://es.aliexpress.com/item/Original-Xiaomi-Mi-Notebook-Air-12-5-Inch-Intel-Core-m3-7Y30-CPU-4GB-128GB-SATA/32825162695.html?spm=a2g04.11219474.j884fa8.35.664b7e58wVCvNu&traffic_analysisId=&scm=1007.16233.91832.0&pvid=e75d7c20-0f73-4c20-bc96-bf6f2429a4e2 corei7, 16gb de ram, ssd 256gb, nvidia gforce de 8gb -> 1.000€. A simple vista me decanto por xiaomi, aunque el teclado es ingles, te regalan una funda de silicona transparente en español.
  8. Este es otro HDD Está recien formateado y limpio, algún programa en especial??
  9. volviendo al tema... 625.252960] usb 1-1.5: reset high-speed USB device number 4 using dwc_otg [ 631.813725] usb 1-1.5: USB disconnect, device number 4 [ 631.863168] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 [ 631.863193] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 00 72 bc a8 00 00 f0 00 [ 631.863204] blk_update_request: I/O error, dev sda, sector 7519400 [ 631.863341] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 [ 631.863358] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 00 72 bd 98 00 00 f0 00 [ 631.863365] blk_update_request: I/O error, dev sda, sector 7519640 [ 631.865450] EXT4-fs warning (device sda1): ext4_end_bio:314: I/O error -5 writing to inode 36962308 (offset 1556086784 size 4190208 starting block 940031) [ 631.865467] Buffer I/O error on device sda1, logical block 939519 [ 631.865493] Buffer I/O error on device sda1, logical block 939520 [ 631.865504] Buffer I/O error on device sda1, logical block 939521 [ 631.865513] Buffer I/O error on device sda1, logical block 939522 [ 631.865522] Buffer I/O error on device sda1, logical block 939523 [ 631.865531] Buffer I/O error on device sda1, logical block 939524 [ 631.865540] Buffer I/O error on device sda1, logical block 939525 [ 631.865549] Buffer I/O error on device sda1, logical block 939526 [ 631.865560] Buffer I/O error on device sda1, logical block 939527 [ 631.865571] Buffer I/O error on device sda1, logical block 939528 [ 631.866684] EXT4-fs warning (device sda1): ext4_end_bio:314: I/O error -5 writing to inode 36962308 (offset 1556086784 size 4190208 starting block 940287) [ 631.867660] EXT4-fs warning (device sda1): ext4_end_bio:314: I/O error -5 writing to inode 36962308 (offset 2025844736 size 4198400 starting block 940288) [ 631.867792] EXT4-fs warning (device sda1): ext4_end_bio:314: I/O error -5 writing to inode 36962308 (offset 2025844736 size 4198400 starting block 1086975) [ 631.868904] EXT4-fs warning (device sda1): ext4_end_bio:314: I/O error -5 writing to inode 36962308 (offset 2025844736 size 4198400 starting block 1087231) [ 631.869994] EXT4-fs warning (device sda1): ext4_end_bio:314: I/O error -5 writing to inode 36962308 (offset 2025844736 size 4198400 starting block 1087487) [ 631.871069] EXT4-fs warning (device sda1): ext4_end_bio:314: I/O error -5 writing to inode 36962308 (offset 2025844736 size 4198400 starting block 1087743) [ 631.872035] EXT4-fs warning (device sda1): ext4_end_bio:314: I/O error -5 writing to inode 36962308 (offset 2025844736 size 4198400 starting block 1087744) [ 631.872174] EXT4-fs warning (device sda1): ext4_end_bio:314: I/O error -5 writing to inode 36962308 (offset 2491412480 size 4198400 starting block 1200639) [ 631.873264] EXT4-fs warning (device sda1): ext4_end_bio:314: I/O error -5 writing to inode 36962308 (offset 2491412480 size 4198400 starting block 1200895) [ 631.945847] JBD2: Detected IO errors while flushing file data on sda1-8 [ 631.945877] Aborting journal on device sda1-8. [ 631.945959] JBD2: Error -5 detected when updating journal superblock for sda1-8. [ 631.946026] JBD2: Detected IO errors while flushing file data on sda1-8 [ 631.954093] EXT4-fs error (device sda1): ext4_journal_check_start:56: Detected aborted journal [ 631.954158] EXT4-fs (sda1): Remounting filesystem read-only [ 631.954218] EXT4-fs (sda1): previous I/O error to superblock detected [ 631.954342] EXT4-fs (sda1): ext4_writepages: jbd2_start: 2147483647 pages, ino 36962308; err -30 [ 643.313224] usb 1-1.5: new high-speed USB device number 5 using dwc_otg [ 643.444398] usb 1-1.5: New USB device found, idVendor=152d, idProduct=2338 [ 643.444417] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=5 [ 643.444425] usb 1-1.5: Product: USB to ATA/ATAPI bridge [ 643.444433] usb 1-1.5: Manufacturer: JMicron [ 643.444441] usb 1-1.5: SerialNumber: 000001D91861 [ 643.445760] usb-storage 1-1.5:1.0: USB Mass Storage device detected [ 643.456310] scsi host1: usb-storage 1-1.5:1.0 [ 644.536165] scsi 1:0:0:0: Direct-Access WDC WD75 00BPVT-22HXZT1 PQ: 0 ANSI: 5 [ 644.537414] sd 1:0:0:0: Attached scsi generic sg0 type 0 [ 644.612822] sd 1:0:0:0: [sdb] 1465149168 512-byte logical blocks: (750 GB/699 GiB) [ 644.613367] sd 1:0:0:0: [sdb] Write Protect is off [ 644.613381] sd 1:0:0:0: [sdb] Mode Sense: 28 00 00 00 [ 644.613815] sd 1:0:0:0: [sdb] No Caching mode page found [ 644.613825] sd 1:0:0:0: [sdb] Assuming drive cache: write through [ 644.778790] sdb: sdb1 [ 644.780914] sd 1:0:0:0: [sdb] Attached SCSI disk [ 647.286529] EXT4-fs (sdb1): recovery complete [ 647.287123] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) [ 649.395488] EXT4-fs error (device sda1): ext4_find_entry:1463: inode #36962307: comm transmission-da: reading directory lblock 0 [ 649.395573] EXT4-fs error (device sda1): ext4_find_entry:1463: inode #36962307: comm transmission-da: reading directory lblock 0 [ 649.395625] EXT4-fs error (device sda1): ext4_find_entry:1463: inode #36962307: comm transmission-da: reading directory lblock 0 [ 649.395904] EXT4-fs error (device sda1): ext4_find_entry:1463: inode #36962307: comm transmission-da: reading directory lblock 0 [ 649.395960] EXT4-fs error (device sda1): ext4_find_entry:1463: inode #36962307: comm transmission-da: reading directory lblock 0 esto es lo que me lanza el dmesg después de obsrvar la expulsión, solo expulsa cuando transmission está descargando.
  10. pero esoos de baratos no tienen nada, a partir de 700€...
  11. si claro, windows elimina grub de cuajo, pero si vas a las opciones de recuperación de windows en seleccionar unidad te aparecen las distintas unidades, como la bios (uefi) unidades usb, o la unidad grub-uefi, inicias desde grub-uefi y regeneras el archivo de configuración desde tu linux, sin necesidad de livecd ni entorno chroot.
  12. los microcortes solucionado: echo 'options rtl8821ae ips=N fwlps=N swlps=Y' > /etc/modprobe.d/wifi.conf
  13. mi tema de los microcortes lo tengo solucionado asi: echo 'options rtl8821ae ips=N fwlps=N swlps=Y' > /etc/modprobe.d/wifi.conf
  14. pues evidentemente metí la pata, utilicé resize2fs y me cargué la partición pero lo solucioné dandole el formato fat32 de nuevo, instalando los kernels y el grub. Luego recuperé el arranque de win con el cd de win10 y a funcionar,
×