file system of live persist home partition »ro« all of a sudden

Forum Forums New users New Users and General Questions file system of live persist home partition »ro« all of a sudden

  • This topic has 4 replies, 2 voices, and was last updated Oct 19-5:38 am by Robin.
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #69099
    Member
    Robin

      Hi everybody

      I encountered a strange behaviour in antiX 19 full live-usb persistent-all 32-bit all of a sudden: While working normally, the running system wouldn’t accept any files get written to the (persistent) ./home directory.
      All of a sudden no file can get stored, no directory created, no file or directory deleted. Always the message “Error: file system is read only” pops up, as well in console as in spaceFM.
      Half an hour ago I had no problems to write/delete files on ./home, and I didn’t perform anything knowingly which could have caused this strange behaviour.
      I can still write to all the other directories, which are stored on mounted internal hdd /dev/sdax.

      Checked: Files and directories are set to 644, 755, 751, 666, and I’m the owner of them, and member of the group. But this doesn’t make any difference, I can’t write or delete any file now in home and its subdirectories.

      mount shows:

      /live/boot-dev/antiX/homefs on /home type ext4 (ro,noatime)
      /dev/sdb1 on /home/demo/Live-usb-storage type ext4 (ro,noatime)

      There it is clearly ro mounted only. The question is: WHY? Was that always this way (I’ve never paid attention to it before)
      Is there a mechanism in the persistence functionality which could have triggered this? I’ve not the faintest idea what to look for. I’ve never seen this before, even when forcing antix 17 or 19 under heavy duty, squeezing the hardware till the pips squeak…

      I’ll reboot in about half an hour, so if there is anything I should check before in order to find the reason for this strange behaviour please let me know.

      So long
      Robin

      Windows is like a submarine. Open a window and serious problems will start.

      #69101
      Member
      Robin

        [96355.021381] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
        [96355.021389] sd 2:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 04 d8 ad 70 00 00 20 00
        [96355.021393] print_req_error: I/O error, dev sdb, sector 81309040
        [96438.591735] usb 1-3: reset high-speed USB device number 2 using ehci-pci
        [96439.699016] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
        [96439.699025] sd 2:0:0:0: [sdb] tag#0 Sense Key : Unit Attention [current]
        [96439.699033] sd 2:0:0:0: [sdb] tag#0 Add. Sense: Not ready to ready change, medium may have changed
        [96439.699041] sd 2:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 02 b3 48 20 00 00 08 00
        [96439.699047] print_req_error: I/O error, dev sdb, sector 45303840
        [96439.699057] EXT4-fs warning (device sdb1): ext4_end_bio:323: I/O error 10 writing to inode 3145793 (offset 0 size 0 starting block 5662981)
        [96439.699063] Buffer I/O error on device sdb1, logical block 5662724
        [96439.699134] print_req_error: I/O error, dev sdb, sector 45304216
        [96439.699141] EXT4-fs warning (device sdb1): ext4_end_bio:323: I/O error 10 writing to inode 3145793 (offset 0 size 0 starting block 5663028)
        [96439.699145] Buffer I/O error on device sdb1, logical block 5662771
        [96439.699211] print_req_error: I/O error, dev sdb, sector 58988928
        [96439.699231] Aborting journal on device sdb1-8.
        [96442.291364] EXT4-fs error (device sdb1): ext4_journal_check_start:61: Detected aborted journal
        [96442.291370] EXT4-fs (sdb1): Remounting filesystem read-only
        [96442.300618] EXT4-fs (sdb1): ext4_writepages: jbd2_start: 2147483646 pages, ino 3145793; err -30
        [96442.300632] print_req_error: I/O error, dev loop1, sector 25473936
        [96442.300655] loop: Write error at byte offset 11310206976, length 4096.
        [96442.300658] print_req_error: I/O error, dev loop1, sector 22090248
        [96442.300716] EXT4-fs warning (device loop1): ext4_end_bio:323: I/O error 10 writing to inode 655677 (offset 0 size 0 starting block 2761282)
        [96442.300720] Buffer I/O error on device loop1, logical block 2761281
        [96442.300736] Aborting journal on device loop1-8.
        [96442.300787] loop: Write error at byte offset 13019119616, length 4096.
        [96442.300790] print_req_error: I/O error, dev loop1, sector 25427968
        [96442.300794] print_req_error: I/O error, dev loop1, sector 25427968
        [96442.300798] Buffer I/O error on dev loop1, logical block 3178496, lost sync page write
        [96442.300832] JBD2: Error -5 detected when updating journal superblock for loop1-8.
        [96442.308115] EXT4-fs error (device sdb1): ext4_journal_check_start:61: Detected aborted journal
        [96442.308120] EXT4-fs (sdb1): ext4_writepages: jbd2_start: 1020 pages, ino 3145793; err -30
        [96450.187252] loop: Write error at byte offset 0, length 4096.
        [96450.187260] print_req_error: I/O error, dev loop1, sector 0
        [96450.187268] print_req_error: I/O error, dev loop1, sector 0
        [96450.187275] Buffer I/O error on dev loop1, logical block 0, lost sync page write
        [96450.187289] EXT4-fs (loop1): I/O error while writing superblock
        [96450.187293] EXT4-fs error (device loop1): ext4_journal_check_start:61: Detected aborted journal
        [96450.187296] EXT4-fs (loop1): Remounting filesystem read-only
        [96450.187332] loop: Write error at byte offset 0, length 4096.
        [96450.187336] print_req_error: I/O error, dev loop1, sector 0
        [96450.187341] print_req_error: I/O error, dev loop1, sector 0
        [96450.187345] Buffer I/O error on dev loop1, logical block 0, lost sync page write
        [96450.187354] EXT4-fs (loop1): I/O error while writing superblock
        [96967.138256] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
        [96967.138264] sd 2:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 04 f6 1c b8 00 00 10 00
        [96967.138267] print_req_error: I/O error, dev sdb, sector 83238072
        [97333.193995] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
        [97333.194002] sd 2:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 04 dd b1 a0 00 00 10 00
        [97333.194006] print_req_error: I/O error, dev sdb, sector 81637792

        Windows is like a submarine. Open a window and serious problems will start.

        #69102
        Member
        Robin

          Following the demsg output above this system shouldn’t run at all anymore. But I didn’t notice anything abnormal while working, apart from the fact that I couldn’t store or delete a file in my home directory all of a sudden.
          Maybe this was caused simply by a hardware failure of the usb stick, we’ll see. Or a program has gone mad and tried to write rubbish to an area it shouldn’t touch.
          But antiX ran happily on and on, as if nothing had happened at all, I’m still writing from it. Could work without having even noticed what happened under the hood. This is what I call a rock stable system. Great job, anticapitalista, really.
          I’ll reboot now, and force a file system integrity check on this usb stick.

          Windows is like a submarine. Open a window and serious problems will start.

          #69124
          Member
          olsztyn

            I encountered a strange behviour in antiX 19 full live-usb persistent-all 32-bit all of a sudden: While working normally, the running system wouldn’t accept any files get written to the (persistent) ./home directory.
            All of a sudden no file can get stored, no directory created, no file or directory deleted. Always the message “Error: file system is read only” pops up, as well in console as in spaceFM.

            I am very curious what you will find out as the cause of this problem.
            At the first thought I would not necessarily expect this to be caused by bad USB hardware. More likely I would expect persistence file to have gotten corrupted. In the past I had quite a few such cases of corruption but not exactly the same manifestation of being read only.
            Since then I do not use persistence files as I like predictability of the system.

            Live antiX Boot Options (Previously posted by Xecure):
            http://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

            #69178
            Member
            Robin

              Hello olsztyn,

              problem solved. Since you’ve written

              I am very curious what you will find out as the cause of this problem.

              I’ll go a bit more in detail as I’d have done otherwise.

              But first the summary:
              – No hardware failure found.
              – No errors in file systems found.
              Most likely it was simply the system starting to run out of memory. I had done some minor updates of two or three little helper programs last days. The next remaster was scheduled allredy, but the translation work for antiX 21 caused me to postpone this task, even though the data copied to ram during startup exceded 1 GB already. 1 GB, this was half the amount of installed ram on this system… But antiX still worked rock stable this way. Until this strange problem occurred, it came unexpected and all of a sudden, and nothing pointed in the direction »insufficient ram«.

              What I did after rebooting, and seeing the error messages concerning writing errors at USB stick still flooded the dmesg output was:

              I booted the pc using a backup USB stick, containing also anitX 19.3, but one update cycle back , which I use in turn with the other stick for keeping the system up to date, so I have a functioning fallback, a backup at hand always, just in case an update or remaster fails.
              Both sticks are physically identical, same manufacturer, same size.

              First Idea was to apply a full e2fsck -fccv on this device. But…

              After plugging the very stick (having not deactivated automount) the trouble started.
              The cpu load displayed by lxtask was 100% for a minute, then the system was responsive again.
              dmesg looked like this now:

              [  500.669149] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
              [  500.669157] sd 2:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 01 5b c1 68 00 00 10 00
              [  500.669161] print_req_error: I/O error, dev sdb, sector 22790504
              [  689.604961] usb 1-4: new high-speed USB device number 4 using ehci-pci
              [  689.984438] usb 1-4: New USB device found, idVendor=058f, idProduct=6387, bcdDevice= 0.02
              [  689.984445] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
              [  689.984450] usb 1-4: Product: Mass Storage        
              [  689.984455] usb 1-4: Manufacturer: Generic        
              [  689.984459] usb 1-4: SerialNumber: 8B36A82A
              [  689.986067] usb-storage 1-4:1.0: USB Mass Storage device detected
              [  689.988420] scsi host3: usb-storage 1-4:1.0
              [  691.078263] scsi 3:0:0:0: Direct-Access     Generic  Flash Disk       8.01 PQ: 0 ANSI: 6
              [  691.080218] sd 3:0:0:0: Attached scsi generic sg3 type 0
              [  691.082166] sd 3:0:0:0: [sdc] 122880000 512-byte logical blocks: (62.9 GB/58.6 GiB)
              [  691.082851] sd 3:0:0:0: [sdc] Write Protect is off
              [  691.082856] sd 3:0:0:0: [sdc] Mode Sense: 23 00 00 00
              [  691.083456] sd 3:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
              [  691.090154]  sdc: sdc1 sdc2
              [  691.093098] sd 3:0:0:0: [sdc] Attached SCSI removable disk
              [  692.568732] FAT-fs (sdc2): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
              [  692.632439] FAT-fs (sdc2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
              [  699.780143] EXT4-fs (sdc1): warning: mounting fs with errors, running e2fsck is recommended
              [  699.798041] EXT4-fs (sdc1): recovery complete
              [  699.802300] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null)
              [  701.254716] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
              [  701.254727] sd 2:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 01 5d 1a d8 00 00 40 00
              [  701.254733] print_req_error: I/O error, dev sdb, sector 22878936
              [  730.431969] usb 1-4: reset high-speed USB device number 4 using ehci-pci
              [  736.052952] usb 1-4: device descriptor read/64, error -110
              [  751.924955] usb 1-4: device descriptor read/64, error -110
              [  752.145963] usb 1-4: reset high-speed USB device number 4 using ehci-pci
              [  757.556965] usb 1-4: device descriptor read/64, error -110
              [  773.428952] usb 1-4: device descriptor read/64, error -110
              [  773.649952] usb 1-4: reset high-speed USB device number 4 using ehci-pci
              [  784.783946] usb 1-4: device not accepting address 4, error -110
              [  784.897961] usb 1-4: reset high-speed USB device number 4 using ehci-pci
              [  796.047962] usb 1-4: device not accepting address 4, error -110
              [  796.048051] sd 3:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK
              [  796.048060] sd 3:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 07 51 65 00 00 00 f0 00
              [  796.048066] print_req_error: I/O error, dev sdc, sector 122774784
              [  796.048198] sd 3:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
              [  796.048205] sd 3:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 07 51 65 f0 00 00 10 00
              [  796.048209] print_req_error: I/O error, dev sdc, sector 122775024
              [  796.048264] usb 1-4: USB disconnect, device number 4
              [  796.052004] print_req_error: I/O error, dev sdc, sector 76040
              [  796.052069] EXT4-fs error (device sdc1): __ext4_find_entry:1449: inode #2: comm spacefm: reading directory lblock 0
              [  796.052158] print_req_error: I/O error, dev sdc, sector 122774784
              [  796.052164] Buffer I/O error on dev sdc1, logical block 15346592, async page read
              [  796.052186] print_req_error: I/O error, dev sdc, sector 58984448
              [  796.052191] Buffer I/O error on dev sdc1, logical block 7372800, lost sync page write
              [  796.053936] JBD2: Error -5 detected when updating journal superblock for sdc1-8.
              [  796.053939] Aborting journal on device sdc1-8.
              [  796.061948] print_req_error: I/O error, dev sdc, sector 122775553
              [  796.061955] Buffer I/O error on dev sdc2, logical block 1, lost async page write
              [  796.061995] print_req_error: I/O error, dev sdc, sector 2048
              [  796.061997] Buffer I/O error on dev sdc1, logical block 0, lost sync page write
              [  796.062014] print_req_error: I/O error, dev sdc, sector 58984448
              [  796.062016] Buffer I/O error on dev sdc1, logical block 7372800, lost sync page write
              [  796.062023] JBD2: Error -5 detected when updating journal superblock for sdc1-8.
              [  796.062044] EXT4-fs (sdc1): I/O error while writing superblock
              [  796.135745] udevd[6673]: inotify_add_watch(7, /dev/sdc, 10) failed: No such file or directory
              [  796.194947] usb 1-4: new high-speed USB device number 5 using ehci-pci
              [  796.228122] FAT-fs (sdc2): Directory bread(block 1576) failed
              [  796.405429] FAT-fs (sdc2): Directory bread(block 1576) failed
              [  801.588957] usb 1-4: device descriptor read/64, error -110
              [  817.460958] usb 1-4: device descriptor read/64, error -110
              [  817.681953] usb 1-4: new high-speed USB device number 6 using ehci-pci
              [  823.092960] usb 1-4: device descriptor read/64, error -110
              [  838.964959] usb 1-4: device descriptor read/64, error -110
              [  839.071986] usb usb1-port4: attempt power cycle
              [  839.497953] usb 1-4: new high-speed USB device number 7 using ehci-pci
              [  850.831958] usb 1-4: device not accepting address 7, error -110
              [  850.945955] usb 1-4: new high-speed USB device number 8 using ehci-pci
              [  862.095961] usb 1-4: device not accepting address 8, error -110
              [  862.096004] usb usb1-port4: unable to enumerate USB device
              [  862.345953] usb 3-2: new full-speed USB device number 2 using uhci_hcd
              [  877.874961] usb 3-2: device descriptor read/64, error -110
              [  893.746942] usb 3-2: device descriptor read/64, error -110
              [  893.969958] usb 3-2: new full-speed USB device number 3 using uhci_hcd
              [  909.618960] usb 3-2: device descriptor read/64, error -110
              [  925.490959] usb 3-2: device descriptor read/64, error -110
              [  925.599980] usb usb3-port2: attempt power cycle
              [  926.025958] usb 3-2: new full-speed USB device number 4 using uhci_hcd
              [  937.359962] usb 3-2: device not accepting address 4, error -110
              [  937.473958] usb 3-2: new full-speed USB device number 5 using uhci_hcd
              [  948.623964] usb 3-2: device not accepting address 5, error -110
              [  948.624013] usb usb3-port2: unable to enumerate USB device

              OK, unmounted the stick manually and wanted to e2fsck it, but /dev/sdc was gone completely from file system.

              $ e2fsck -fv /dev/sdc1
              e2fsck 1.44.5 (15-Dec-2018)
              e2fsck: Datei oder Verzeichnis nicht gefunden while trying to open /dev/sdc1
              Possibly non-existent device?
              $ lsusb
              Bus 001 Device 002: ID 058f:6387 Alcor Micro Corp. Flash Drive
              Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
              Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
              Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
              Bus 002 Device 002: ID 093a:2533 Pixart Imaging, Inc. 
              Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

              Well, well well… One plugged USB device missing here. Should be Alcor Micro Corp. Flash Drive present two times.

              Deactivated automount option in antiX control center and plugged the stick again.
              This time everything was fine, since no attempt was done to mount it.

              Unplugged it again, and activated automount option again, just to be sure there is a correlation:

              [ 1064.979958] usb 1-4: new high-speed USB device number 9 using ehci-pci
              [ 1065.365331] usb 1-4: New USB device found, idVendor=058f, idProduct=6387, bcdDevice= 0.02
              [ 1065.365337] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
              [ 1065.365342] usb 1-4: Product: Mass Storage        
              [ 1065.365347] usb 1-4: Manufacturer: Generic        
              [ 1065.365351] usb 1-4: SerialNumber: 8B36A82A
              [ 1065.368076] usb-storage 1-4:1.0: USB Mass Storage device detected
              [ 1065.368997] scsi host3: usb-storage 1-4:1.0
              [ 1066.501383] scsi 3:0:0:0: Direct-Access     Generic  Flash Disk       8.01 PQ: 0 ANSI: 6
              [ 1066.502082] sd 3:0:0:0: Attached scsi generic sg3 type 0
              [ 1066.504226] sd 3:0:0:0: [sdc] 122880000 512-byte logical blocks: (62.9 GB/58.6 GiB)
              [ 1066.504990] sd 3:0:0:0: [sdc] Write Protect is off
              [ 1066.504997] sd 3:0:0:0: [sdc] Mode Sense: 23 00 00 00
              [ 1066.505721] sd 3:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
              [ 1066.512050]  sdc: sdc1 sdc2
              [ 1066.514593] sd 3:0:0:0: [sdc] Attached SCSI removable disk
              [ 1105.215963] usb 1-4: reset high-speed USB device number 9 using ehci-pci
              [ 1105.615896] sd 3:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
              [ 1105.615905] sd 3:0:0:0: [sdc] tag#0 Sense Key : Unit Attention [current] 
              [ 1105.615914] sd 3:0:0:0: [sdc] tag#0 Add. Sense: Not ready to ready change, medium may have changed
              [ 1105.615942] sd 3:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 00 00 08 20 00 00 08 00
              [ 1105.615947] print_req_error: I/O error, dev sdc, sector 2080
              [ 1105.616968] print_req_error: I/O error, dev sdc, sector 2080
              [ 1105.616975] Buffer I/O error on dev sdc1, logical block 4, async page read
              [ 1105.619248] sd 3:0:0:0: [sdc] 122880000 512-byte logical blocks: (62.9 GB/58.6 GiB)
              [ 1105.627043]  sdc: sdc1 sdc2
              [ 1106.225293] EXT4-fs (sdc1): recovery complete
              [ 1106.225300] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null)
              [ 1107.867050] FAT-fs (sdc2): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
              [ 1107.889413] FAT-fs (sdc2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
              [ 1108.930984] FAT-fs (sdc2): error, invalid access to FAT (entry 0x00082003)
              [ 1108.930989] FAT-fs (sdc2): Filesystem has been set read-only
              [ 1108.931844] FAT-fs (sdc2): error, invalid access to FAT (entry 0x00082003)
              [ 1139.519972] usb 1-4: reset high-speed USB device number 9 using ehci-pci
              [ 1145.140974] usb 1-4: device descriptor read/64, error -110
              [ 1161.012966] usb 1-4: device descriptor read/64, error -110
              [ 1161.233949] usb 1-4: reset high-speed USB device number 9 using ehci-pci
              [ 1166.644950] usb 1-4: device descriptor read/64, error -110
              [ 1168.029731] udevd[2673]: worker [7518] /devices/pci0000:00/0000:00:1d.7/usb1/1-4/1-4:1.0/host3/target3:0:0/3:0:0:0/block/sdc/sdc1 is taking a long time
              [ 1168.029747] udevd[2673]: worker [7500] /devices/pci0000:00/0000:00:1d.7/usb1/1-4/1-4:1.0/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 is taking a long time
              [ 1182.516968] usb 1-4: device descriptor read/64, error -110
              [ 1182.737970] usb 1-4: reset high-speed USB device number 9 using ehci-pci
              [ 1193.871963] usb 1-4: device not accepting address 9, error -110
              [ 1193.985964] usb 1-4: reset high-speed USB device number 9 using ehci-pci
              [ 1205.135971] usb 1-4: device not accepting address 9, error -110
              [ 1205.136048] sd 3:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK
              [ 1205.136057] sd 3:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 00 00 0a f8 00 00 10 00
              [ 1205.136063] print_req_error: I/O error, dev sdc, sector 2808
              [ 1205.136252] sd 3:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
              [ 1205.136259] sd 3:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 07 51 68 28 00 00 08 00
              [ 1205.136264] print_req_error: I/O error, dev sdc, sector 122775592
              [ 1205.136296] usb 1-4: USB disconnect, device number 9
              [ 1205.143972] print_req_error: I/O error, dev sdc, sector 122775593
              [ 1205.144006] print_req_error: I/O error, dev sdc, sector 2568
              [ 1205.144013] Buffer I/O error on dev sdc1, logical block 65, async page read
              [ 1205.144341] print_req_error: I/O error, dev sdc, sector 58984448
              [ 1205.144346] Buffer I/O error on dev sdc1, logical block 7372800, lost sync page write
              [ 1205.144369] JBD2: Error -5 detected when updating journal superblock for sdc1-8.
              [ 1205.144372] Aborting journal on device sdc1-8.
              [ 1205.144410] print_req_error: I/O error, dev sdc, sector 58984448
              [ 1205.144414] Buffer I/O error on dev sdc1, logical block 7372800, lost sync page write
              [ 1205.144423] JBD2: Error -5 detected when updating journal superblock for sdc1-8.
              [ 1205.144857] print_req_error: I/O error, dev sdc, sector 2048
              [ 1205.144862] Buffer I/O error on dev sdc1, logical block 0, lost sync page write
              [ 1205.144971] EXT4-fs (sdc1): I/O error while writing superblock
              [ 1205.149972] scsi 3:0:0:0: rejecting I/O to dead device
              [ 1205.149978] print_req_error: I/O error, dev sdc, sector 122775688
              [ 1205.150195] FAT-fs (sdc2): FAT read failed (blocknr 32)
              [ 1205.153979] Buffer I/O error on dev sdc2, logical block 16, async page read
              [ 1205.153983] Buffer I/O error on dev sdc2, logical block 17, async page read
              [ 1205.153984] Buffer I/O error on dev sdc2, logical block 18, async page read
              [ 1205.153986] Buffer I/O error on dev sdc2, logical block 19, async page read
              [ 1205.153988] Buffer I/O error on dev sdc2, logical block 20, async page read
              [ 1205.153990] Buffer I/O error on dev sdc2, logical block 21, async page read
              [ 1205.154600] udevd[7500]: inotify_add_watch(7, /dev/sdc2, 10) failed: No such file or directory
              [ 1205.163396] udevd[7518]: inotify_add_watch(7, /dev/sdc1, 10) failed: No such file or directory
              [ 1205.209793] udevd[7848]: inotify_add_watch(7, /dev/sdc, 10) failed: No such file or directory
              [ 1205.212684] FAT-fs (sdc2): FAT read failed (blocknr 32)
              [ 1205.265950] usb 1-4: new high-speed USB device number 10 using ehci-pci
              [ 1210.676949] usb 1-4: device descriptor read/64, error -110
              [ 1226.548968] usb 1-4: device descriptor read/64, error -110
              [ 1226.769951] usb 1-4: new high-speed USB device number 11 using ehci-pci
              [ 1232.180958] usb 1-4: device descriptor read/64, error -110
              [ 1248.052962] usb 1-4: device descriptor read/64, error -110
              [ 1248.159988] usb usb1-port4: attempt power cycle
              [ 1248.585962] usb 1-4: new high-speed USB device number 12 using ehci-pci
              [ 1259.919964] usb 1-4: device not accepting address 12, error -110
              [ 1260.033958] usb 1-4: new high-speed USB device number 13 using ehci-pci
              [ 1271.183966] usb 1-4: device not accepting address 13, error -110
              [ 1271.184005] usb usb1-port4: unable to enumerate USB device
              [ 1271.433976] usb 3-2: new full-speed USB device number 6 using uhci_hcd
              [ 1286.962959] usb 3-2: device descriptor read/64, error -110
              [ 1302.834963] usb 3-2: device descriptor read/64, error -110
              [ 1303.057958] usb 3-2: new full-speed USB device number 7 using uhci_hcd
              [ 1318.706947] usb 3-2: device descriptor read/64, error -110
              [ 1334.578958] usb 3-2: device descriptor read/64, error -110
              [ 1334.687975] usb usb3-port2: attempt power cycle
              [ 1335.113956] usb 3-2: new full-speed USB device number 8 using uhci_hcd
              [ 1346.447958] usb 3-2: device not accepting address 8, error -110
              [ 1346.561953] usb 3-2: new full-speed USB device number 9 using uhci_hcd
              [ 1357.711948] usb 3-2: device not accepting address 9, error -110
              [ 1357.711983] usb usb3-port2: unable to enumerate USB device
              

              OK, OK, understood. No automount possible with this device for now.
              So I deactivated automount again, and plugged the stick again.
              And voilà, it works again. What the heck? This has never been a problem before.
              But see yourself:

              [ 1588.055960] usb 1-4: new high-speed USB device number 14 using ehci-pci
              [ 1588.288306] usb 1-4: New USB device found, idVendor=058f, idProduct=6387, bcdDevice= 0.02
              [ 1588.288312] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
              [ 1588.288316] usb 1-4: Product: Mass Storage        
              [ 1588.288321] usb 1-4: Manufacturer: Generic        
              [ 1588.288325] usb 1-4: SerialNumber: B04CA515
              [ 1588.290804] usb-storage 1-4:1.0: USB Mass Storage device detected
              [ 1588.291905] scsi host3: usb-storage 1-4:1.0
              [ 1590.043801] scsi 3:0:0:0: Direct-Access     Generic  Flash Disk       8.01 PQ: 0 ANSI: 6
              [ 1590.045980] sd 3:0:0:0: Attached scsi generic sg3 type 0
              [ 1590.047745] sd 3:0:0:0: [sdc] 122880000 512-byte logical blocks: (62.9 GB/58.6 GiB)
              [ 1590.048372] sd 3:0:0:0: [sdc] Write Protect is off
              [ 1590.048377] sd 3:0:0:0: [sdc] Mode Sense: 23 00 00 00
              [ 1590.049097] sd 3:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
              [ 1590.054171]  sdc: sdc1 sdc2
              [ 1590.057281] sd 3:0:0:0: [sdc] Attached SCSI removable disk

              Everything fine now. And also there was the missing /dev/sdc again:

              $ lsusb
              Bus 001 Device 014: ID 058f:6387 Alcor Micro Corp. Flash Drive
              Bus 001 Device 002: ID 058f:6387 Alcor Micro Corp. Flash Drive
              Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
              Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
              Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
              Bus 002 Device 002: ID 093a:2533 Pixart Imaging, Inc. 
              Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

              Now e2fsck works:

              $ sudo e2fsck -fccv /dev/sdc1
              e2fsck 1.44.5 (15-Dec-2018)
              Checking for bad blocks (non-destructive read-write-test)
              Testing with random pattern: 45.53% done, 00:39:46 elapsed. (0/0/0 errors)
              ...
              Checking for bad blocks (non-destructive read-write-test): done                                                 
              antiX-Live-usb: Updating bad block inode.
              Pass 1: Checking inodes, blocks, and sizes
              Pass 2: Checking directory structure
              Pass 3: Checking directory connectivity
              Pass 4: Checking reference counts
              Pass 5: Checking group summary information
                      1094 inodes used (0.03%, out of 3842048)
                         1 non-contiguous file (0.1%)
                         0 non-contiguous directories (0.0%)
                           # of inodes with ind/dind/tind blocks: 0/0/0
                           Extent depth histogram: 1081/5
                  10408043 blocks used (67.82%, out of 15346688)
                         0 bad blocks
                         6 large files
                      1000 regular files
                        85 directories
                         0 character device files
                         0 block device files
                         0 fifos
                         0 links
                         0 symbolic links (0 fast symbolic links)
                         0 sockets
              ------------
                      1085 files

              No errors, no bad blocks found. Hence I decided to mount manually.

              $ sudo mkdir /media/demo/usb_test_01
              $ sudo mount /dev/sdc1 /media/demo/usb_test_01

              Still everything fine, no errors in dmesg.
              Could access the content also without any problem. Nothing missing there.

              So next step: Checking homefs file internally:

              $ sudo e2fsck -fccv /media/demo/usb_test_01/antiX/homefs
              e2fsck 1.44.5 (15-Dec-2018)
              Checking for bad blocks (non-destructive read-write-test)
              Testing with random pattern: 98.61% done, 02:19:37 elapsed. (0/0/0 errors)
              ...
              Testing with random pattern: done
              /media/demo/usb_test_01/antiX/homefs: Updating bad block inode.
              Pass 1: Checking inodes, blocks, and sizes
              Pass 2: Checking directory structure
              Pass 3: Checking directory connectivity
              Pass 4: Checking reference counts
              Pass 5: Checking group summary information
                     15912 inodes used (0.97%, out of 1638400)
                       489 non-contiguous files (3.1%)
                         6 non-contiguous directories (0.0%)
                           # of inodes with ind/dind/tind blocks: 0/0/0
                           Extent depth histogram: 15737/23
                    295667 blocks used (4.51%, out of 6553600)
                         0 bad blocks
                         1 large file
                     14543 regular files
                      1208 directories
                         0 character device files
                         0 block device files
                         0 fifos
                         0 links
                       152 symbolic links (144 fast symbolic links)
                         0 sockets
              ------------
                     15903 files

              Took about two hours (unattended), but no errors, no bad blocks.

              Now I mounted homefs as loop, just to see what happens.

              $ sudo mkdir /media/demo/test_home
              $ sudo mount /media/demo/usb_test_01/antiX/homefs /media/demo/test_home -o loop

              Everything fine inside, nothing missing (no important data stored there, but anyway),
              and no error messages in dmesg still.

              $ sudo e2fsck -fccv /media/demo/usb_test_01/antiX/rootfs
              e2fsck 1.44.5 (15-Dec-2018)
              Checking for bad blocks (non-destructive read-write-test)
              Testing with random pattern: 95.02% done, 00:14:11 elapsed. (0/0/0 errors)
              ...
              Testing with random pattern: done
              /media/demo/usb_test_01/antiX/rootfs: Updating bad block inode.
              Pass 1: Checking inodes, blocks, and sizes
              Pass 2: Checking directory structure
              Pass 3: Checking directory connectivity
              Pass 4: Checking reference counts
              Pass 5: Checking group summary information
                     25832 inodes used (4.93%, out of 524288)
                       240 non-contiguous files (0.9%)
                        24 non-contiguous directories (0.1%)
                           # of inodes with ind/dind/tind blocks: 0/0/0
                           Extent depth histogram: 24603/1
                    342634 blocks used (16.34%, out of 2097152)
                         0 bad blocks
                         1 large file
                     22313 regular files
                      2274 directories
                       309 character device files
                         0 block device files
                         0 fifos
                         0 links
                       927 symbolic links (911 fast symbolic links)
                         0 sockets
              ------------
                     25823 files

              And finally

              $ sudo fsck -V /dev/sdc2
              fsck from util-linux 2.33.1
              [/usr/sbin/fsck.vfat (1) -- /dev/sdc2] fsck.vfat /dev/sdc2 
              fsck.fat 4.1 (2017-01-24)
              0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
              1) Remove dirty bit
              2) No action
              ? 1
              Perform changes ? (y/n) y
              /dev/sdc2: 11 files, 8561/98776 clusters

              Additional finding:

              lxtask shows 100% CPU load (see attached screenshots), but… htop tells me there are only 8..19%

              Always when accessing USB lxtask reports these 100% CPU. So what’s going on here?

              The interessting thing is: I noticed before also while working a delay of 10..30 seconds, up to a minute sometimes
              after writing a file of even less than 10kb to any USB storage. During this time the CPU monitor of lxtask always shows 100%.
              And during this time the program involved (whichever it is) stays irresponsive, while any other program reacts normally. On even more writing task even the USB mouse pointer wouldn’t move for a short period of time.
              Now I know, it is not CPU actually, since all the other programs respond normally. But it is USB which is the bottleneck here, even if it is USB-2.0 with a transfer rate of about 20MB/sec.

              Last step: let run memtest, full checkup.
              No findings. No bad cells found in system memory. Everything fine, even with unattended three hour random pattern testing.

              Conclusion: Back to normal. No idea what had actually happened. Best guess is probably it was the beginning of running out of memory, which scatterend the data sent to the USB device, which caused its controller to batten down the hatches.

              It looks like a kind of timing issue, concerning data transfer and protocol to the USB device while some
              component of the PC is at its limit.

              Going now to boot again with the checked stick.

              And back again, having booted this stick, seeing same error messages in dmesg as before. Let’s do a remaster, to get rid of the 1,08 GB root directory copied to ram at every startup, taking half of system memory.
              Remaster worked fine, and after reboot the error messages in dmesg were gone.

              So, this is the whole story.

              So long
              Robin

              Windows is like a submarine. Open a window and serious problems will start.

            Viewing 5 posts - 1 through 5 (of 5 total)
            • You must be logged in to reply to this topic.