From: robin_listas@es.invalid   
      
   On 2023-03-31 13:14, bad sector wrote:   
   >   
   > Undedr /0 (in addition to everything else that I don't want systems to   
   > step on) I have canned mountpoints for every partition on every   
   > imaginable device such as disks from /dev/sda to /dev/sdg. One such is   
   > /0/sda4 which theoretically serves as a mount-POINT for dev/sda4. This   
   > partition happens to be my Leap-15.3 partition and I want to mount it so   
   > that I might copy one user's home folder over to my TW system (on   
   > dev/sda5). I just created this user with a specific look-and-feel and   
   > the LAST thing I want to do is repeat the exercise to set up under TW   
   > and then 5 other distros as well.   
   >   
   > This would/should go like   
   >   
   > fdisk -l   
   > ..to confirm that sda IS the disk seen as primary, a step made necessary   
   > ONLY by Leap which ALONE in all my distros continues to sometimes list   
   > it as /dev/sdb.   
      
      
   Plain simple:   
      
   DO NOT use device names such as /dev/sda. Use the new nomenclature, no   
   matter if you think they are too long.   
      
      
   Then, the command to see the information you need is:   
      
      
   lsblk --output   
   NAME,KNAME,RA,RM,RO,PARTFLAGS,SIZE,TYPE,FSTYPE,LABEL,PARTLABEL,P   
   TYPE,MOUNTPOINT,UUID,PARTUUID,WWN,MODEL,ALIGNMENT   
   | less -S   
      
   (one single line). Keep it in your important_notes.txt and paste it when   
   needed; use as root.)   
      
      
   >   
   > There *is* this fdisk item   
   >   
   >    /dev/mapper/Samsung_SSD_860_EVO_1TB_S59VNJ0N419951T-part4   
   >   
   > but I can't really use it because on one hand I can only guess that it   
   > refers to /dev/sda4 and on the other typing yard-and-a-half long names   
   > isn't my forte.   
   >   
   >   
   > mount /dev/sda4 /0/sa04   
   >   
   > FileManager copy /0/sa04/home/userX to /home/userX   
   >   
   > make all /home/userX owned by userX   
   >   
   > now for the real run:   
   >   
   > # umount /dev/sda4   
   > umount: /dev/sda4: not mounted.   
   >   
   > # mount /dev/sda4 /0/sa04   
   > mount: /0/sa04: /dev/sda4 already mounted or mount point busy.   
   >         dmesg(1) may have more information after failed mount system   
   call.   
   >   
   >   
   > # dmesg   
   > [  222.582351] /dev/sda4: Can't open blockdev   
   > [  313.515808] /dev/sda4: Can't open blockdev   
   > [  366.135462] /dev/sda4: Can't open blockdev   
   > [  416.200151] /dev/sda4: Can't open blockdev   
      
   Well, you have a hardware problem.   
      
   >   
   >   
   > If I click the USB icon in SystTray I can select ALL devices and after   
   > an hour's worth of eyestrain I can make out /dev/sda4. One option is to   
   > "Open in File Manager" (not even 'boo' as to what moint-POINT is being   
   > talked about!). Why is this important? BECAUSE the above message said   
   > "or mountpoint busy" which couldn't possibley refer to the attempted   
   > mountpoint of /0/sa04 because the systemn doesn't know about my canned   
   > mountpoints. It would be nice all the same to have some clue as to what   
   > moount-POINT was being talked about.   
      
      
   mountpoint is clearly is "/0/sa04". It says so.   
      
   >   
   > So, how am I supposed to get to /dev/sda4 for the stated copy   
   > without taking it out of the mobile tray and plugging it in as a USB   
   > thing on a USB pigtail?   
      
   Your post is confusing, and you use the wrong command to get the   
   information.   
      
   --   
   Cheers, Carlos.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)