[Solved via suspend crash] umount and sync take forever - sdd not listed in /var/log/messages

Technical issues/questions of an intermediate or advanced nature.
User avatar
Rava
Contributor
Contributor
Posts: 5401
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

[Solved via suspend crash] umount and sync take forever - sdd not listed in /var/log/messages

Post#1 by Rava » 09 Nov 2022, 12:16

What's tz?

Code: Select all

guest@porteus:/$ type tz
tz is a function
tz () 
{ 
    echo $(date +%d.%m.%Y\ %H:%M:%S) ____________________________________________________________
}
The issue, now it's "09.11.2022 13:14" (or as when I edited this post it was 13:14)
the umount command is still not finished, I copied a mere 320 MB file to a VFAT USB Thumbdrive using tz and time to monitor how long it takes to umount after the copying:

Code: Select all

guest@porteus:/my/video/Filme$ tz;time umount /mnt/sdd1/;tz
09.11.2022 09:50:46 ____________________________________________________________
As you can see, what was executed at 09:50 and still not finished at 13:14 will most probably never finish.
Looking into recent entries concerning the device ( /mnt/sdd1 ) in /var/log/messages I realized for some unknown reason the other two external devices I mounted and umounted are mentioned (sdc1 and sde1) but not sdd1!

Code: Select all

Nov  9 09:39:48 porteus syslogd[790]: -- MARK --
Nov  9 09:42:20 porteus kernel: EXT4-fs (sdc1): mounting ext2 file system using the ext4 subsystem
Nov  9 09:42:20 porteus kernel: EXT4-fs (sdc1): mounted filesystem without journal. Opts: (null)
Nov  9 09:48:18 porteus kernel: usb 2-1.1.1: USB disconnect, device number 4
Nov  9 09:51:06 porteus kernel: usb 2-1.2: reset high-speed USB device number 13 using ehci-pci
Nov  9 09:51:08 porteus last message buffered 3 times
Nov  9 09:51:08 porteus kernel: usb 2-1.1.1: new high-speed USB device number 14 using ehci-pci
Nov  9 09:51:08 porteus kernel: usb 2-1.1.1: New USB device found, idVendor=05e3, idProduct=0727, bcdDevice= 2.07
Nov  9 09:51:08 porteus kernel: usb 2-1.1.1: New USB device strings: Mfr=3, Product=4, SerialNumber=2
Nov  9 09:51:08 porteus kernel: usb 2-1.1.1: Product: USB Storage
Nov  9 09:51:08 porteus kernel: usb 2-1.1.1: Manufacturer: Generic
Nov  9 09:51:08 porteus kernel: usb 2-1.1.1: SerialNumber: -blabla-
Nov  9 09:51:08 porteus kernel: usb-storage 2-1.1.1:1.0: USB Mass Storage device detected
Nov  9 09:51:08 porteus kernel: scsi host6: usb-storage 2-1.1.1:1.0
Nov  9 09:51:08 porteus mtp-probe: checking bus 2, device 14: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1.1" 
Nov  9 09:51:08 porteus mtp-probe: bus: 2, device: 14 was not an MTP device 
Nov  9 09:51:09 porteus kernel: scsi 6:0:0:0: Direct-Access     Generic  STORAGE DEVICE   0207 PQ: 0 ANSI: 0
Nov  9 09:51:09 porteus kernel: sd 6:0:0:0: [sdc] 3862528 512-byte logical blocks: (1.98 GB/1.84 GiB)
Nov  9 09:51:09 porteus kernel: sd 6:0:0:0: [sdc] Write Protect is off
Nov  9 09:51:09 porteus kernel:  sdc: sdc1
Nov  9 09:51:09 porteus kernel: sd 6:0:0:0: [sdc] Attached SCSI removable disk
Nov  9 09:51:31 porteus kernel: EXT4-fs (sdc1): mounting ext2 file system using the ext4 subsystem
Nov  9 09:51:31 porteus kernel: EXT4-fs (sdc1): mounted filesystem without journal. Opts: (null)
Nov  9 09:51:38 porteus kernel: usb 2-1.2: reset high-speed USB device number 13 using ehci-pci
Nov  9 10:03:37 porteus kernel: usb 2-1.3: new high-speed USB device number 15 using ehci-pci
Nov  9 10:03:37 porteus kernel: usb 2-1.3: New USB device found, idVendor=8644, idProduct=800b, bcdDevice= 1.00
Nov  9 10:03:37 porteus kernel: usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov  9 10:03:37 porteus kernel: usb 2-1.3: Product: USB Flash Disk                
Nov  9 10:03:37 porteus kernel: usb 2-1.3: Manufacturer: General                       
Nov  9 10:03:37 porteus kernel: usb 2-1.3: SerialNumber: -blabla-
Nov  9 10:03:37 porteus kernel: usb-storage 2-1.3:1.0: USB Mass Storage device detected
Nov  9 10:03:37 porteus kernel: scsi host8: usb-storage 2-1.3:1.0
Nov  9 10:03:37 porteus mtp-probe: checking bus 2, device 15: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3" 
Nov  9 10:03:37 porteus mtp-probe: bus: 2, device: 15 was not an MTP device 
Nov  9 10:03:38 porteus kernel: scsi 8:0:0:0: Direct-Access     General  USB Flash Disk   1.0  PQ: 0 ANSI: 2
Nov  9 10:03:38 porteus kernel: sd 8:0:0:0: [sde] 15656960 512-byte logical blocks: (8.02 GB/7.47 GiB)
Nov  9 10:03:38 porteus kernel: sd 8:0:0:0: [sde] Write Protect is off
Nov  9 10:03:38 porteus kernel:  sde: sde1
Nov  9 10:03:38 porteus kernel: sd 8:0:0:0: [sde] Attached SCSI removable disk
Nov  9 10:12:51 porteus kernel: usb 2-1.3: USB disconnect, device number 15
Nov  9 10:17:55 porteus kernel: usb 2-1.3: new high-speed USB device number 16 using ehci-pci
Nov  9 10:17:55 porteus kernel: usb 2-1.3: New USB device found, idVendor=8644, idProduct=800b, bcdDevice= 1.00
Nov  9 10:17:55 porteus kernel: usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov  9 10:17:55 porteus kernel: usb 2-1.3: Product: USB Flash Disk                
Nov  9 10:17:55 porteus kernel: usb 2-1.3: Manufacturer: General                       
Nov  9 10:17:55 porteus kernel: usb 2-1.3: SerialNumber: -blabla-
Nov  9 10:17:55 porteus kernel: usb-storage 2-1.3:1.0: USB Mass Storage device detected
Nov  9 10:17:55 porteus kernel: scsi host8: usb-storage 2-1.3:1.0
Nov  9 10:17:55 porteus mtp-probe: checking bus 2, device 16: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3" 
Nov  9 10:17:55 porteus mtp-probe: bus: 2, device: 16 was not an MTP device 
Nov  9 10:17:56 porteus kernel: scsi 8:0:0:0: Direct-Access     General  USB Flash Disk   1.0  PQ: 0 ANSI: 2
Nov  9 10:17:56 porteus kernel: sd 8:0:0:0: [sde] 15656960 512-byte logical blocks: (8.02 GB/7.47 GiB)
Nov  9 10:17:56 porteus kernel: sd 8:0:0:0: [sde] Write Protect is off
Nov  9 10:17:56 porteus kernel:  sde: sde1
Nov  9 10:17:56 porteus kernel: sd 8:0:0:0: [sde] Attached SCSI removable disk
Nov  9 10:22:32 porteus kernel: usb 2-1.3: USB disconnect, device number 16
Nov  9 10:59:48 porteus syslogd[790]: -- MARK --
I did the copy and umount monitored by tz and time on the same device previously, and thanks to tz I have the time info when that did happen:

Code: Select all

guest@porteus:/my/video/Filme$ tz;time umount /mnt/sdd1/;tz
09.11.2022 09:46:24 ____________________________________________________________

real	0m48.558s
user	0m0.002s
sys	0m0.164s
09.11.2022 09:47:12 ____________________________________________________________
but still at around 09:46 / 09:47 there was no mentioning of sdd in /var/log/messages either.
using mount to tell me what devices are mounted minus sda* and sdb* using this one-liner:

Code: Select all

guest@porteus:~$ mount | grep -v sd[ab] | grep sd
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
gives no sdd1 and nor does df:

Code: Select all

guest@porteus:~$ df -Tm  |grep sdd
guest@porteus:~$ 
Anyone any idea why I could mount and write to sdd1 when sdd is not mentioned in /var/log/messages during the time frame at all?

And what kind of limbo state is sdd1 currently in?

It's LED is blinking meaning there is a read or read/write operation going on, but like I said above: when the umount is not finished after several hours it never will finish.

Executing sync also seems to never be able to finish most likely due to the same sdd device:

Code: Select all

root@porteus:/usr/local/bin# tz
09.11.2022 12:51:42 ____________________________________________________________
root@porteus:/usr/local/bin# sync

asking ps about the sync and the umount processes:

Code: Select all

root@porteus:/usr/local/bin# /bin/ps ax | /bin/grep sync | /bin/grep -v grep
26270 pts/1    D+     0:00 sync
root@porteus:/usr/local/bin# /bin/ps ax | /bin/grep umount | /bin/grep -v grep
25764 pts/7    D+     0:00 umount /mnt/sdd1/
man ps tells us this on the statuses:

Code: Select all

D    uninterruptible sleep (usually IO)
+    is in the foreground process group
So far I did not dare do a suspend, but I cannot keep the machine going for days in the very slim hope the umount (or sync) will finish.

Any ideas?

Added in 9 hours 25 minutes 47 seconds:
Update

since the 1st approach of going into suspend failed (system came back after approx 10 seconds of black screen) I plugged out the offending USB thumbdrive but the system crashed at 2nd suspend anyway :cry: (the kind of crash where not even REISUB was working) :(

But the fsck on all Unix file systems during boot was okay, and the fsck.vfat on the USB thumbdrive did require some minor cleanup, and the md5sum of the copied 320 MB file was wrong, so I simply deleted it. Good luck no harm was done because of the system crash. :)
Cheers!
Yours Rava