[SOLVED] full install on usb don't boot correctly

[juliusse]

The problem is not the laptop, because It's the same on 3 different machines.

Here is the error message I have when plugin the usb

Code: Select all

Error mounting /dev/sdb1 at /run/media/aurelie/c6b9fa76-1d26-4349-aec9-72dad647a1b3: Command-line `mount -t "ext4" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdb1" "/run/media/aurelie/c6b9fa76-1d26-4349-aec9-72dad647a1b3"' exited with non-zero exit status 32: mount: /run/media/aurelie/c6b9fa76-1d26-4349-aec9-72dad647a1b3: can't read superblock on /dev/sdb1

here the neofetch, but in this case it's not relevant

Code: Select all

OS: Slackel Linux 5.4.57 x86_64 
       #######          Host: 3626HMG ThinkPad X201 
     ###########        Kernel: 5.4.57 
    #############       Uptime: 3 mins 
   ###############      Packages: 946 (pkgtool) 
   ################     Shell: bash 5.0.18 
  #################     Resolution: 1280x800 
#####################   WM: Openbox 
#####################   WM Theme: Clearlooks-Olive 
  #################     Theme: Adwaita [GTK2/3] 
                        Icons: matefaenza [GTK2/3] 
                        Terminal: lxterminal 
                        Terminal Font: Terminus 12 
                        CPU: Intel i5 M 520 (4) @ 2.400GHz 
                        GPU: Intel Core Processor 
                        Memory: 646MiB / 1840MiB 

The usb is brand new, a Kingston datatraveller.

I assume it's not because initrd, I was thinking of a swap problem.

[djemos]

have you tried fsck.ext4 ?
plug in your usb but do not mount it. If it is mounted then umounted
Then run

Code: Select all

sudo fsck.ext4 /dev/sdb1

or

Code: Select all

sudo e2fsck /dev/sdb1

or
sudo slapt-src -i testdisk
and run testdisk to repair the usb

Also when you have unplug your usb look at /etc/mtab
If it is any /dev/sdb1 line remove it.

What is the output of
mount
sudo parted -l
for /dev/sdb part of output
e.g mine

Code: Select all

Model: SanDisk Cruzer Blade (scsi)
Disk /dev/sdb: 31,4GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system     Flags
 1      1049kB  29,3GB  29,3GB  primary  ext4            boot
 2      29,3GB  31,4GB  2147MB  primary  linux-swap(v1)

[juliusse]

Honestly I'm like you, I've never had this problem with an USB. And I've used a lot of.
I will try fsck and e2fsck, but as a low-level command like dd hasn't worked, I doubt it will function. Moreover, even with dd, I've got error telling me that sdbX isn't recognized.

I will try try testdisk and also have a look at the mtab file.
Thanks

[djemos]

look also in /etc/fstab if it is also there a line with /dev/sdb1

Look at this link also it it helps solve the problem. https://www.cyberciti.biz/faq/recover-b ... partition/

[juliusse]

/etc/mtab and /etc/fstab have no trace of sdb.
reading my previous posts, I saw that I forgot to tell that the usb can't be mounted, so every command acting with /dev/sdb will fail.
like following

result of mount

Code: Select all

/dev/sda1 on / type ext4 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /dev/shm type tmpfs (rw)
gvfsd-fuse on /var/run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=aurelie)
gvfsd-fuse on /var/run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=aurelie)

parted -l

Code: Select all

Modèle : ATA ST9250315AS (scsi)
Disque /dev/sda : 250GB
Taille des secteurs (logiques/physiques) : 512B/512B
Table de partitions : msdos
Drapeaux de disque : 

Numéro  Début   Fin    Taille  Type     Système de fichiers  Drapeaux
 1      1049kB  246GB  246GB   primary  ext4                 démarrage
 2      246GB   250GB  4194MB  primary  linux-swap(v1)

the usb don't show up
As I told previously, if a low level command and "brutal" try like

Code: Select all

sudo dd if=/dev/zero of=/dev/sdb bs=512M

has failed, you have to look after more complicated solutions, indeed. Normally, this dd trick can save the day more than once, writing 0 on every block of the disk, but...
Actually running a testdisk, I will tell you the result.

[juliusse]

No success with testdisk, I think that's an hardware failure. Thanks