From: robin_listas@es.invalid   
      
   On 2023-04-01 18:41, bad sector wrote:   
   > On 4/1/23 08:52, Carlos E.R. wrote:   
   >> On 2023-04-01 02:51, bad sector wrote:   
   >   
   >>>>>   
   >>>>> and your lsblok one-liner (thanks BTW) just ends with   
   >>>>>   
   >>>>> "[14551.227219] /dev/sda4: Can't open blockdev"   
   >>>>   
   >>>> Is it really a blockdev? Do check it.   
   >>>>   
   >>>> ls -l /dev/sda*   
   >>>   
   >>> # ls -l /dev/sda   
   >>> brw-rw---- 1 root disk 8, 0 Mar 31 14:39 /dev/sda   
   >>>   
   >>> # ls -l /dev/sda1   
   >>> brw-rw---- 1 root disk 8, 1 Mar 31 14:39 /dev/sda1   
   >>>   
   >>   
   >> So, you do not have /dev/sda4   
   >>   
   >> notice I asked for "ls -l /dev/sda*"  >:-)   
   >   
   > my mistake   
   >   
   > # ls -l /dev/sda*   
   > brw-rw---- 1 root disk   8,  0 Apr  1 12:29 /dev/sda   
   > brw-rw---- 1 root disk   8,  1 Apr  1 12:29 /dev/sda1   
   > brw-rw---- 1 root disk   8, 10 Apr  1 12:29 /dev/sda10   
   > brw-rw---- 1 root disk   8, 11 Apr  1 12:29 /dev/sda11   
   > brw-rw---- 1 root disk   8, 12 Apr  1 12:29 /dev/sda12   
   > brw-rw---- 1 root disk   8, 13 Apr  1 12:29 /dev/sda13   
   > brw-rw---- 1 root disk   8, 14 Apr  1 12:29 /dev/sda14   
   > brw-rw---- 1 root disk   8, 15 Apr  1 12:29 /dev/sda15   
   > brw-rw---- 1 root disk 259,  0 Apr  1 12:29 /dev/sda16   
   > brw-rw---- 1 root disk 259,  1 Apr  1 12:29 /dev/sda17   
   > brw-rw---- 1 root disk   8,  2 Apr  1 12:29 /dev/sda2   
   > brw-rw---- 1 root disk   8,  3 Apr  1 12:29 /dev/sda3   
   > brw-rw---- 1 root disk   8,  4 Apr  1 12:29 /dev/sda4   
   > brw-rw---- 1 root disk   8,  5 Apr  1 12:29 /dev/sda5   
   > brw-rw---- 1 root disk   8,  6 Apr  1 12:29 /dev/sda6   
   > brw-rw---- 1 root disk   8,  7 Apr  1 12:29 /dev/sda7   
   > brw-rw---- 1 root disk   8,  8 Apr  1 12:29 /dev/sda8   
   > brw-rw---- 1 root disk   8,  9 Apr  1 12:29 /dev/sda9   
      
   Ok, all seems fine.   
      
   Just the other day I could not write to an USB stick because its device   
   had been replaced with a file, same name. Weird trouble with absurd   
   error messages similar to yours.   
      
   So the system was right in those messages to me. "It" was right, not me.   
      
      
   >> Your choice. But if you insist on using names like /dev/sdXY you get   
   >> the trouble.   
   >>   
   >> Ah, you can change the UUID to something of your choice...   
   >   
   > like so?   
   >   
   > tune2fs -U "dev_sda4" /dev/sda4   :-)   
      
   If you put that on a file or script, then yes, that is asking for trouble.   
      
   --   
   Cheers, Carlos.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)