Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
How do you mount a solid state drive? ...
30 views
Skip to first unread message
Albretch Mueller
Jul 27, 2022, 4:10:06 PM7/27/22
to
I googled: "mount solid state drive" Linux, and I got very few hits
(like 16?) which were mostly totally irrelevant.
I got a laptop with Windows installed on which I installed WSLg.
WIndows and WSLg both seem to detect the SSD just fine, but in ways
that are not totally clear to me.
What I care about is using the SSD for my data intensive code in
Linux, but when I boot that computer with Debian live I can't see the
SSD.
What could be going on?
lbrtchx
(like 16?) which were mostly totally irrelevant.
I got a laptop with Windows installed on which I installed WSLg.
WIndows and WSLg both seem to detect the SSD just fine, but in ways
that are not totally clear to me.
What I care about is using the SSD for my data intensive code in
Linux, but when I boot that computer with Debian live I can't see the
SSD.
What could be going on?
lbrtchx
Albretch Mueller
Jul 27, 2022, 4:30:05 PM7/27/22
to
Dan Ritter
Jul 27, 2022, 4:40:05 PM7/27/22
to
Albretch Mueller wrote:
> I got a laptop with Windows installed on which I installed WSLg.
> WIndows and WSLg both seem to detect the SSD just fine, but in ways
> that are not totally clear to me.
> What I care about is using the SSD for my data intensive code in
> Linux, but when I boot that computer with Debian live I can't see the
> SSD.
> What could be going on?
An SSD shows up as a disk. What's in /dev/disk/by-id/ ?
> I got a laptop with Windows installed on which I installed WSLg.
> WIndows and WSLg both seem to detect the SSD just fine, but in ways
> that are not totally clear to me.
> What I care about is using the SSD for my data intensive code in
> Linux, but when I boot that computer with Debian live I can't see the
> SSD.
> What could be going on?
-dsr-
Jude DaShiell
Jul 27, 2022, 7:00:05 PM7/27/22
to
An easy way to locate an ssd is to have it unplugged from the system and
run lsblk and save that to a file then plug the ssd in and run lsblk again
saving its output to another file. The line in the second file that's
missing from the first file is the ssd.
run lsblk and save that to a file then plug the ssd in and run lsblk again
saving its output to another file. The line in the second file that's
missing from the first file is the ssd.
to...@tuxteam.de
Jul 28, 2022, 12:40:05 AM7/28/22
to
On Wed, Jul 27, 2022 at 06:54:32PM -0400, Jude DaShiell wrote:
> An easy way to locate an ssd is to have it unplugged from the system and
> run lsblk and save that to a file then plug the ssd in and run lsblk again
> saving its output to another file. The line in the second file that's
> missing from the first file is the ssd.
Nice trick :)
> An easy way to locate an ssd is to have it unplugged from the system and
> run lsblk and save that to a file then plug the ssd in and run lsblk again
> saving its output to another file. The line in the second file that's
> missing from the first file is the ssd.
To add one to the toolbox: do "tail -f /var/log/messages" while plugging
in the device: you'll watch your OS pondering on what to do about it.
Or do "dmesg | tail" right away after having plugged it in. In both cases
you'll see which name the device was registered with.
Both need root privilege, so "sudo" or "su" or whatever.
Cheers
--
t
to...@tuxteam.de
Jul 28, 2022, 12:40:05 AM7/28/22
to
On Wed, Jul 27, 2022 at 03:06:47PM -0500, Albretch Mueller wrote:
> I googled: "mount solid state drive" Linux, and I got very few hits
> (like 16?) which were mostly totally irrelevant.
First of all, you don't mount a drive. You mount a file system.
> I googled: "mount solid state drive" Linux, and I got very few hits
> (like 16?) which were mostly totally irrelevant.
This may sound like an unimportant nit to pick, but it actually
can get very confusing when there's more than one partition
(and thus potentially more than one file system) on that drive.
Then, from the system software side, there's no difference between
an SSD and a "traditional" hard disk. As far as you, the sysadmin,
are concerned, they both present themselves as block devices you
can partition, put file systems there, etc.
*If*
(a) there is a file system on your drive (perhaps in a partition
in there)
(b) your OS is set up in a way that it automatically recognises
it
then it'll probably somehow auto-mount that file system (that
may be helpful or not).
Now the question back to you: *what* are you trying to do?
Cheers
--
t
David Wright
Jul 28, 2022, 1:20:05 AM7/28/22
to
On Wed 27 Jul 2022 at 15:06:47 (-0500), Albretch Mueller wrote:
> I googled: "mount solid state drive" Linux, and I got very few hits
> (like 16?) which were mostly totally irrelevant.
> I got a laptop with Windows installed on which I installed WSLg.
> WIndows and WSLg both seem to detect the SSD just fine, but in ways
> that are not totally clear to me.
Oh, come on.
> I googled: "mount solid state drive" Linux, and I got very few hits
> (like 16?) which were mostly totally irrelevant.
> I got a laptop with Windows installed on which I installed WSLg.
> WIndows and WSLg both seem to detect the SSD just fine, but in ways
> that are not totally clear to me.
> What I care about is using the SSD for my data intensive code in
> Linux, but when I boot that computer with Debian live I can't see the
> SSD.
> What could be going on?
you /have/ made. Please.
Cheers,
David.
David Wright
Jul 28, 2022, 1:30:06 AM7/28/22
to
it was that difficult to spot the SSD, if it's showing up
at all. That's disregarding the tediousness of opening up
a laptop.
Cheers,
David.
Nicolas George
Jul 28, 2022, 2:40:06 AM7/28/22
to
to...@tuxteam.de (12022-07-28):
> Both need root privilege, so "sudo" or "su" or whatever.
sudo vim /etc/sysctl.conf
kernel.dmesg_restrict=0
Regards,
--
Nicolas George
> To add one to the toolbox: do "tail -f /var/log/messages" while plugging
> in the device: you'll watch your OS pondering on what to do about it.
>
> Or do "dmesg | tail" right away after having plugged it in. In both cases
> you'll see which name the device was registered with.
dmesg -w
> in the device: you'll watch your OS pondering on what to do about it.
>
> Or do "dmesg | tail" right away after having plugged it in. In both cases
> you'll see which name the device was registered with.
> Both need root privilege, so "sudo" or "su" or whatever.
kernel.dmesg_restrict=0
Regards,
--
Nicolas George
David
Jul 28, 2022, 3:30:05 AM7/28/22
to
On Thu, 28 Jul 2022 at 14:33, <to...@tuxteam.de> wrote:
> On Wed, Jul 27, 2022 at 06:54:32PM -0400, Jude DaShiell wrote:
> > An easy way to locate an ssd is to have it unplugged from the system and
> > run lsblk and save that to a file then plug the ssd in and run lsblk again
> > saving its output to another file. The line in the second file that's
> > missing from the first file is the ssd.
>
> Nice trick :)
A similar trick that I use when I like to see the difference in real
> On Wed, Jul 27, 2022 at 06:54:32PM -0400, Jude DaShiell wrote:
> > An easy way to locate an ssd is to have it unplugged from the system and
> > run lsblk and save that to a file then plug the ssd in and run lsblk again
> > saving its output to another file. The line in the second file that's
> > missing from the first file is the ssd.
>
> Nice trick :)
time as the device is connected and disconnected, or if the connection
might be unreliable:
watch lsblk -f
gene heskett
Jul 28, 2022, 4:40:08 AM7/28/22
to
Seems like it s/b, but doesn't see my camera, but a tail on
/var/log/syslog sees it just fine.
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>
Jude DaShiell
Jul 28, 2022, 4:40:08 AM7/28/22
to
a recap and this ought to be better.
lsblk >orig
# plug ssd in.
lsblk >new
comm -1 -3 -f orig new
lsblk >orig
# plug ssd in.
lsblk >new
comm -1 -3 -f orig new
gene heskett
Jul 28, 2022, 4:40:09 AM7/28/22
to
Take care & stay well.
David Christensen
Jul 28, 2022, 5:20:05 AM7/28/22
to
"The distribution installation resides inside an ext4-formatted
filesystem inside a virtual disk, and the host file system is
transparently accessible through the 9P protocol,[54] similarly to other
virtual machine technologies like QEMU."
Use Windows Backup and Restore to create a system image and to backup
your Windows data to an external HDD.
Use Windows RecoveryDrive to create a USB recovery drive.
Figuring out how to mount the WSL ext4 filesystem using Debian Live
looks to be non-trivial. Mounting NTFS is easy. Mounting ext4 is easy.
But, I do not know what format Microsoft uses for the WSL virtual
disk; so, I do not know if Debian can open it. And, unless you can find
known good commands, fumbling around with incorrect commands could
corrupt the WSL filesystem, the WSL virtual disk, the Windows C:
filesystem, and/or the SSD partitioning scheme.
Dual-boot comes to mind; but I had bad experiences with dual-boot and
avoid it.
I would boot Windows, shrink the C: partition to create free space, shut
down Windows, boot Debian Live, create a new partition in the free space
(partitioning scheme should be GPT), and create a new ext4 filesystem in
the new partition. You should then be able to mount the new ext4
filesystem using WSL, Debian Live, or any other live OS that supports
GPT and ext4.
David
Nicolas George
Jul 28, 2022, 5:30:06 AM7/28/22
to
gene heskett (12022-07-28):
> > sudo vim /etc/sysctl.conf
> > kernel.dmesg_restrict=0
> Did that Nicolas, on bullseye still no perms w/o the sudo.
Did you reboot or have the corresponding service apply the change or do
the change manually (sudo syctl -w)?
Regards,
--
Nicolas George
> > sudo vim /etc/sysctl.conf
> > kernel.dmesg_restrict=0
> Did that Nicolas, on bullseye still no perms w/o the sudo.
the change manually (sudo syctl -w)?
Regards,
--
Nicolas George
gene heskett
Jul 28, 2022, 12:50:04 PM7/28/22
to
On 7/28/22 05:24, Nicolas George wrote:
> sudo syctl -w
A typu? Added an s...
gene@coyote:/var/log$ sudo sysctl -w
sysctl: no variables specified
Try `sysctl --help' for more information.
debian bullseye, no reboot, takes 15+ minutes to get everything up and
running after a reboot.
What was I supposed to write?
Thank Nic.
> sudo syctl -w
A typu? Added an s...
gene@coyote:/var/log$ sudo sysctl -w
sysctl: no variables specified
Try `sysctl --help' for more information.
debian bullseye, no reboot, takes 15+ minutes to get everything up and
running after a reboot.
What was I supposed to write?
Thank Nic.
Andrew M.A. Cater
Jul 28, 2022, 1:00:05 PM7/28/22
to
On Thu, Jul 28, 2022 at 12:46:46PM -0400, gene heskett wrote:
> On 7/28/22 05:24, Nicolas George wrote:
> > sudo syctl -w
> A typu? Added an s...
>
> gene@coyote:/var/log$ sudo sysctl -w
> sysctl: no variables specified
> Try `sysctl --help' for more information.
>
> debian bullseye, no reboot, takes 15+ minutes to get everything up and
> running after a reboot.
>
> What was I supposed to write?
>
> Thank Nic.
>
> Cheers, Gene Heskett.
> --
mount -a will work for any drive specified in /etc/fstab
> On 7/28/22 05:24, Nicolas George wrote:
> > sudo syctl -w
> A typu? Added an s...
>
> gene@coyote:/var/log$ sudo sysctl -w
> sysctl: no variables specified
> Try `sysctl --help' for more information.
>
> debian bullseye, no reboot, takes 15+ minutes to get everything up and
> running after a reboot.
>
> What was I supposed to write?
>
> Thank Nic.
>
> Cheers, Gene Heskett.
> --
All the very best,as ever,
Andy Cater
Nicolas George
Jul 28, 2022, 1:00:05 PM7/28/22
to
gene heskett (12022-07-28):
--
Nicolas George
> gene@coyote:/var/log$ sudo sysctl -w
> sysctl: no variables specified
> Try `sysctl --help' for more information.
Have you tried reading the fine manual?
> sysctl: no variables specified
> Try `sysctl --help' for more information.
--
Nicolas George
gene heskett
Jul 28, 2022, 1:10:05 PM7/28/22
to
Vincent Lefevre
Aug 3, 2022, 5:30:05 AM8/3/22
to
On 2022-07-27 15:20:19 -0500, Albretch Mueller wrote:
> https://wiki.debian.org/SSDOptimization
I'm wondering whether information is obsolete. At least for the
"Low-Latency IO-Scheduler" section, it talks about the cfq vs
deadline scheduler, but it seems that they no longer exist:
zira:~> cat /sys/block/sda/queue/scheduler
[mq-deadline] none
(which is the default).
--
Vincent Lefèvre <vin...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
> https://wiki.debian.org/SSDOptimization
I'm wondering whether information is obsolete. At least for the
"Low-Latency IO-Scheduler" section, it talks about the cfq vs
deadline scheduler, but it seems that they no longer exist:
zira:~> cat /sys/block/sda/queue/scheduler
[mq-deadline] none
(which is the default).
--
Vincent Lefèvre <vin...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Albretch Mueller
Aug 11, 2022, 10:20:06 PM8/11/22
to
Sorry, for my late reaction. I'd wish I could dedicate myself to
coding and reading only. This is what blkid and hwinfo are telling me
and I know that that SSD is not sda or sdb, nor is it the DVD; so,
what is it and how do I mount that SSD
Isn't it weird that I don't see it on blkid or hwinfo? Could that
possibly be some kind of BIOS problem. I want to install Debian on
that box, but I want to make sure I can use the SSD.
~
$ sudo blkid
/dev/sr0: BLOCK_SIZE="2048" UUID="2021-12-18-12-41-54-00"
LABEL="d-live 11.2.0 lx amd64" TYPE="iso9660" PTUUID="2300adc2"
PTTYPE="dos"
/dev/loop0: TYPE="squashfs"
/dev/sda1: BLOCK_SIZE="512" UUID="063EB7273EB70F25" TYPE="ntfs"
PARTUUID="7784295b-01"
/dev/sda2: LABEL="RECOVERY" BLOCK_SIZE="512" UUID="02E62855E6284AED"
TYPE="ntfs" PARTUUID="7784295b-02"
/dev/sdb1: UUID="EEB0-73CE" BLOCK_SIZE="512" TYPE="exfat" PARTUUID="011ad286-01"
$
~
sudo hwinfo --block
21: SCSI 300.0: 10600 Disk
[Created at block.245]
Unique ID: hSuP.AaKvbIlfUrE
Parent ID: MZfG.V56qLD9omq1
SysFS ID: /class/block/sdb
SysFS BusID: 3:0:0:0
SysFS Device Link:
/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.0/host3/target3:0:0/3:0:0:0
Hardware Class: disk
Model: "ASolid USB"
Vendor: usb 0x24a9 "ASolid"
Device: usb 0x205a "USB"
Revision: "0000"
Serial ID: "0000000005"
Driver: "usb-storage", "sd"
Driver Modules: "usb_storage", "sd_mod"
Device File: /dev/sdb (/dev/sg2)
Device Files: /dev/sdb,
/dev/disk/by-path/pci-0000:00:14.0-usb-0:2:1.0-scsi-0:0:0:0,
/dev/disk/by-id/usb-ASolid_USB_91870508-0:0
Device Number: block 8:16-8:31 (char 21:2)
Geometry (Logical): CHS 15297/255/63
Size: 245760001 sectors a 512 bytes
Capacity: 117 GB (125829120512 bytes)
Module Alias: "usb:v24A9p205Ad0110dc00dsc00dp00ic08isc06ip50in00"
Driver Info #0:
Driver Status: uas is active
Driver Activation Cmd: "modprobe uas"
Driver Info #1:
Driver Status: usb_storage is active
Driver Activation Cmd: "modprobe usb_storage"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #19 (USB Controller)
22: None 00.0: 11300 Partition
[Created at block.434]
Unique ID: h4pj.SE1wIdpsiiC
Parent ID: hSuP.AaKvbIlfUrE
SysFS ID: /class/block/sdb/sdb1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdb1
Device Files: /dev/sdb1, /dev/disk/by-partuuid/011ad286-01,
/dev/disk/by-id/usb-ASolid_USB_91870508-0:0-part1,
/dev/disk/by-path/pci-0000:00:14.0-usb-0:2:1.0-scsi-0:0:0:0-part1,
/dev/disk/by-uuid/EEB0-73CE
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #21 (Disk)
23: SCSI 200.0: 10602 CD-ROM (DVD)
[Created at block.249]
Unique ID: 2UT6.6hpq9kiHcsB
Parent ID: MZfG.V56qLD9omq1
SysFS ID: /class/block/sr0
SysFS BusID: 2:0:0:0
SysFS Device Link:
/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/host2/target2:0:0/2:0:0:0
Hardware Class: cdrom
Model: "MATSHITA DVD-RAM UJ870BJ"
Vendor: usb 0x13fd "MATSHITA"
Device: usb 0x0840 "DVD-RAM UJ870BJ"
Revision: "1.00"
Serial ID: "524534332020303336303033"
Driver: "usb-storage", "sr"
Driver Modules: "usb_storage", "sr_mod"
Device File: /dev/sr0 (/dev/sg1)
Device Files: /dev/sr0,
/dev/disk/by-label/d-live\x2011.2.0\x20lx\x20amd64, /dev/dvd,
/dev/disk/by-uuid/2021-12-18-12-41-54-00, /dev/cdrw, /dev/dvdrw,
/dev/disk/by-id/usb-MATSHITA_DVD-RAM_UJ870BJ_524534332020303336303033-0:0,
/dev/cdrom, /dev/disk/by-path/pci-0000:00:14.0-usb-0:3:1.0-scsi-0:0:0:0
Device Number: block 11:0 (char 21:1)
Features: CD-R, CD-RW, DVD, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW,
DVD+R DL, DVD-RAM, MRW, MRW-W
Speed: 480 Mbps
Module Alias: "usb:v13FDp0840d0114dc00dsc00dp00ic08isc02ip50in00"
Driver Info #0:
Driver Status: usb_storage is active
Driver Activation Cmd: "modprobe usb_storage"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #19 (USB Controller)
Drive Speed: 62
Volume ID: "d-live 11.2.0 lx amd64"
Preparer: "XORRISO-1.5.2 2019.10.26.180001, LIBISOBURN-1.5.2,
LIBISOFS-1.5.2, LIBBURN-1.5.2"
Creation date: "2021121812415400"
El Torito info: platform 0, bootable
Boot Catalog: at sector 0x0175
Media: none starting at sector 0x0691
Load: 2048 bytes
24: IDE 00.0: 10600 Disk
[Created at block.245]
Unique ID: 3OOL.vPgxpiTnr01
Parent ID: abAj.sYX0o+9l7nE
SysFS ID: /class/block/sda
SysFS BusID: 0:0:0:0
SysFS Device Link:
/devices/pci0000:00/0000:00:17.0/ata1/host0/target0:0:0/0:0:0:0
Hardware Class: disk
Model: "TOSHIBA MK3252GS"
Vendor: "TOSHIBA"
Device: "MK3252GS"
Revision: "1C"
Serial ID: "29DAF54XS"
Driver: "ahci", "sd"
Driver Modules: "ahci", "sd_mod"
Device File: /dev/sda
Device Files: /dev/sda, /dev/disk/by-path/pci-0000:00:17.0-ata-1.0,
/dev/disk/by-id/wwn-0x5000039196c01633,
/dev/disk/by-id/ata-TOSHIBA_MK3252GSX_29DAF54XS,
/dev/disk/by-path/pci-0000:00:17.0-ata-1
Device Number: block 8:0-8:15
Geometry (Logical): CHS 38913/255/63
Size: 625142448 sectors a 512 bytes
Capacity: 298 GB (320072933376 bytes)
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #7 (RAID bus controller)
25: None 00.0: 11300 Partition
[Created at block.434]
Unique ID: bdUI.SE1wIdpsiiC
Parent ID: 3OOL.vPgxpiTnr01
SysFS ID: /class/block/sda/sda1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sda1
Device Files: /dev/sda1,
/dev/disk/by-path/pci-0000:00:17.0-ata-1.0-part1,
/dev/disk/by-partuuid/7784295b-01,
/dev/disk/by-path/pci-0000:00:17.0-ata-1-part1,
/dev/disk/by-id/wwn-0x5000039196c01633-part1,
/dev/disk/by-id/ata-TOSHIBA_MK3252GSX_29DAF54XS-part1,
/dev/disk/by-uuid/063EB7273EB70F25
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #24 (Disk)
26: None 00.0: 11300 Partition
[Created at block.434]
Unique ID: 2pkM.SE1wIdpsiiC
Parent ID: 3OOL.vPgxpiTnr01
SysFS ID: /class/block/sda/sda2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sda2
Device Files: /dev/sda2, /dev/disk/by-partuuid/7784295b-02,
/dev/disk/by-label/RECOVERY,
/dev/disk/by-path/pci-0000:00:17.0-ata-1.0-part2,
/dev/disk/by-path/pci-0000:00:17.0-ata-1-part2,
/dev/disk/by-id/wwn-0x5000039196c01633-part2,
/dev/disk/by-uuid/02E62855E6284AED,
/dev/disk/by-id/ata-TOSHIBA_MK3252GSX_29DAF54XS-part2
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #24 (Disk)
$
coding and reading only. This is what blkid and hwinfo are telling me
and I know that that SSD is not sda or sdb, nor is it the DVD; so,
what is it and how do I mount that SSD
Isn't it weird that I don't see it on blkid or hwinfo? Could that
possibly be some kind of BIOS problem. I want to install Debian on
that box, but I want to make sure I can use the SSD.
~
$ sudo blkid
/dev/sr0: BLOCK_SIZE="2048" UUID="2021-12-18-12-41-54-00"
LABEL="d-live 11.2.0 lx amd64" TYPE="iso9660" PTUUID="2300adc2"
PTTYPE="dos"
/dev/loop0: TYPE="squashfs"
/dev/sda1: BLOCK_SIZE="512" UUID="063EB7273EB70F25" TYPE="ntfs"
PARTUUID="7784295b-01"
/dev/sda2: LABEL="RECOVERY" BLOCK_SIZE="512" UUID="02E62855E6284AED"
TYPE="ntfs" PARTUUID="7784295b-02"
/dev/sdb1: UUID="EEB0-73CE" BLOCK_SIZE="512" TYPE="exfat" PARTUUID="011ad286-01"
$
~
sudo hwinfo --block
21: SCSI 300.0: 10600 Disk
[Created at block.245]
Unique ID: hSuP.AaKvbIlfUrE
Parent ID: MZfG.V56qLD9omq1
SysFS ID: /class/block/sdb
SysFS BusID: 3:0:0:0
SysFS Device Link:
/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.0/host3/target3:0:0/3:0:0:0
Hardware Class: disk
Model: "ASolid USB"
Vendor: usb 0x24a9 "ASolid"
Device: usb 0x205a "USB"
Revision: "0000"
Serial ID: "0000000005"
Driver: "usb-storage", "sd"
Driver Modules: "usb_storage", "sd_mod"
Device File: /dev/sdb (/dev/sg2)
Device Files: /dev/sdb,
/dev/disk/by-path/pci-0000:00:14.0-usb-0:2:1.0-scsi-0:0:0:0,
/dev/disk/by-id/usb-ASolid_USB_91870508-0:0
Device Number: block 8:16-8:31 (char 21:2)
Geometry (Logical): CHS 15297/255/63
Size: 245760001 sectors a 512 bytes
Capacity: 117 GB (125829120512 bytes)
Module Alias: "usb:v24A9p205Ad0110dc00dsc00dp00ic08isc06ip50in00"
Driver Info #0:
Driver Status: uas is active
Driver Activation Cmd: "modprobe uas"
Driver Info #1:
Driver Status: usb_storage is active
Driver Activation Cmd: "modprobe usb_storage"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #19 (USB Controller)
22: None 00.0: 11300 Partition
[Created at block.434]
Unique ID: h4pj.SE1wIdpsiiC
Parent ID: hSuP.AaKvbIlfUrE
SysFS ID: /class/block/sdb/sdb1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdb1
Device Files: /dev/sdb1, /dev/disk/by-partuuid/011ad286-01,
/dev/disk/by-id/usb-ASolid_USB_91870508-0:0-part1,
/dev/disk/by-path/pci-0000:00:14.0-usb-0:2:1.0-scsi-0:0:0:0-part1,
/dev/disk/by-uuid/EEB0-73CE
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #21 (Disk)
23: SCSI 200.0: 10602 CD-ROM (DVD)
[Created at block.249]
Unique ID: 2UT6.6hpq9kiHcsB
Parent ID: MZfG.V56qLD9omq1
SysFS ID: /class/block/sr0
SysFS BusID: 2:0:0:0
SysFS Device Link:
/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/host2/target2:0:0/2:0:0:0
Hardware Class: cdrom
Model: "MATSHITA DVD-RAM UJ870BJ"
Vendor: usb 0x13fd "MATSHITA"
Device: usb 0x0840 "DVD-RAM UJ870BJ"
Revision: "1.00"
Serial ID: "524534332020303336303033"
Driver: "usb-storage", "sr"
Driver Modules: "usb_storage", "sr_mod"
Device File: /dev/sr0 (/dev/sg1)
Device Files: /dev/sr0,
/dev/disk/by-label/d-live\x2011.2.0\x20lx\x20amd64, /dev/dvd,
/dev/disk/by-uuid/2021-12-18-12-41-54-00, /dev/cdrw, /dev/dvdrw,
/dev/disk/by-id/usb-MATSHITA_DVD-RAM_UJ870BJ_524534332020303336303033-0:0,
/dev/cdrom, /dev/disk/by-path/pci-0000:00:14.0-usb-0:3:1.0-scsi-0:0:0:0
Device Number: block 11:0 (char 21:1)
Features: CD-R, CD-RW, DVD, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW,
DVD+R DL, DVD-RAM, MRW, MRW-W
Speed: 480 Mbps
Module Alias: "usb:v13FDp0840d0114dc00dsc00dp00ic08isc02ip50in00"
Driver Info #0:
Driver Status: usb_storage is active
Driver Activation Cmd: "modprobe usb_storage"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #19 (USB Controller)
Drive Speed: 62
Volume ID: "d-live 11.2.0 lx amd64"
Preparer: "XORRISO-1.5.2 2019.10.26.180001, LIBISOBURN-1.5.2,
LIBISOFS-1.5.2, LIBBURN-1.5.2"
Creation date: "2021121812415400"
El Torito info: platform 0, bootable
Boot Catalog: at sector 0x0175
Media: none starting at sector 0x0691
Load: 2048 bytes
24: IDE 00.0: 10600 Disk
[Created at block.245]
Unique ID: 3OOL.vPgxpiTnr01
Parent ID: abAj.sYX0o+9l7nE
SysFS ID: /class/block/sda
SysFS BusID: 0:0:0:0
SysFS Device Link:
/devices/pci0000:00/0000:00:17.0/ata1/host0/target0:0:0/0:0:0:0
Hardware Class: disk
Model: "TOSHIBA MK3252GS"
Vendor: "TOSHIBA"
Device: "MK3252GS"
Revision: "1C"
Serial ID: "29DAF54XS"
Driver: "ahci", "sd"
Driver Modules: "ahci", "sd_mod"
Device File: /dev/sda
Device Files: /dev/sda, /dev/disk/by-path/pci-0000:00:17.0-ata-1.0,
/dev/disk/by-id/wwn-0x5000039196c01633,
/dev/disk/by-id/ata-TOSHIBA_MK3252GSX_29DAF54XS,
/dev/disk/by-path/pci-0000:00:17.0-ata-1
Device Number: block 8:0-8:15
Geometry (Logical): CHS 38913/255/63
Size: 625142448 sectors a 512 bytes
Capacity: 298 GB (320072933376 bytes)
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #7 (RAID bus controller)
25: None 00.0: 11300 Partition
[Created at block.434]
Unique ID: bdUI.SE1wIdpsiiC
Parent ID: 3OOL.vPgxpiTnr01
SysFS ID: /class/block/sda/sda1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sda1
Device Files: /dev/sda1,
/dev/disk/by-path/pci-0000:00:17.0-ata-1.0-part1,
/dev/disk/by-partuuid/7784295b-01,
/dev/disk/by-path/pci-0000:00:17.0-ata-1-part1,
/dev/disk/by-id/wwn-0x5000039196c01633-part1,
/dev/disk/by-id/ata-TOSHIBA_MK3252GSX_29DAF54XS-part1,
/dev/disk/by-uuid/063EB7273EB70F25
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #24 (Disk)
26: None 00.0: 11300 Partition
[Created at block.434]
Unique ID: 2pkM.SE1wIdpsiiC
Parent ID: 3OOL.vPgxpiTnr01
SysFS ID: /class/block/sda/sda2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sda2
Device Files: /dev/sda2, /dev/disk/by-partuuid/7784295b-02,
/dev/disk/by-label/RECOVERY,
/dev/disk/by-path/pci-0000:00:17.0-ata-1.0-part2,
/dev/disk/by-path/pci-0000:00:17.0-ata-1-part2,
/dev/disk/by-id/wwn-0x5000039196c01633-part2,
/dev/disk/by-uuid/02E62855E6284AED,
/dev/disk/by-id/ata-TOSHIBA_MK3252GSX_29DAF54XS-part2
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #24 (Disk)
$
Dan Ritter
Aug 11, 2022, 11:30:06 PM8/11/22
to
Albretch Mueller wrote:
> Sorry, for my late reaction. I'd wish I could dedicate myself to
> coding and reading only. This is what blkid and hwinfo are telling me
> and I know that that SSD is not sda or sdb, nor is it the DVD; so,
> what is it and how do I mount that SSD
> Isn't it weird that I don't see it on blkid or hwinfo? Could that
> possibly be some kind of BIOS problem. I want to install Debian on
> that box, but I want to make sure I can use the SSD.
If the information you have presented is correct, there is no
> Sorry, for my late reaction. I'd wish I could dedicate myself to
> coding and reading only. This is what blkid and hwinfo are telling me
> and I know that that SSD is not sda or sdb, nor is it the DVD; so,
> what is it and how do I mount that SSD
> Isn't it weird that I don't see it on blkid or hwinfo? Could that
> possibly be some kind of BIOS problem. I want to install Debian on
> that box, but I want to make sure I can use the SSD.
way to use the SSD. There is no evidence that it exists.
If the kernel can recognize it and it is attached, it will be in
cat /proc/partitions
and
ls -al /dev/disk/by-id/
Since you can't see it there, it is not usable.
-dsr-
Timothy M Butterworth
Aug 12, 2022, 1:10:06 AM8/12/22
to
On Thu, Aug 11, 2022 at 11:21 PM Dan Ritter <d...@randomstring.org> wrote:
Albretch Mueller wrote:
> Sorry, for my late reaction. I'd wish I could dedicate myself to
> coding and reading only. This is what blkid and hwinfo are telling me
> and I know that that SSD is not sda or sdb, nor is it the DVD; so,
> what is it and how do I mount that SSD
> Isn't it weird that I don't see it on blkid or hwinfo? Could that
> possibly be some kind of BIOS problem. I want to install Debian on
> that box, but I want to make sure I can use the SSD.
If the information you have presented is correct, there is no
way to use the SSD. There is no evidence that it exists.
If the kernel can recognize it and it is attached, it will be in
cat /proc/partitions
Here is what my NVME Solid State drive partitions look like:
cat /proc/partitions
major minor #blocks name
259 0 500107608 nvme0n1
259 1 257007 nvme0n1p1
259 2 2097152 nvme0n1p2
259 3 16793600 nvme0n1p3
259 4 480959815 nvme0n1p4
major minor #blocks name
259 0 500107608 nvme0n1
259 1 257007 nvme0n1p1
259 2 2097152 nvme0n1p2
259 3 16793600 nvme0n1p3
259 4 480959815 nvme0n1p4
What is it that you are trying to mount?
and
ls -al /dev/disk/by-id/
Since you can't see it there, it is not usable.
-dsr-
David Wright
Aug 12, 2022, 1:30:05 AM8/12/22
to
On Fri 12 Aug 2022 at 01:03:45 (-0400), Timothy M Butterworth wrote:
> On Thu, Aug 11, 2022 at 11:21 PM Dan Ritter <d...@randomstring.org> wrote:
> > Albretch Mueller wrote:
> > > Sorry, for my late reaction. I'd wish I could dedicate myself to
> > > coding and reading only. This is what blkid and hwinfo are telling me
> > > and I know that that SSD is not sda or sdb, nor is it the DVD; so,
> > > what is it and how do I mount that SSD
> > > Isn't it weird that I don't see it on blkid or hwinfo? Could that
> > > possibly be some kind of BIOS problem. I want to install Debian on
> > > that box, but I want to make sure I can use the SSD.
> >
> > If the information you have presented is correct, there is no
> > way to use the SSD. There is no evidence that it exists.
> >
> > If the kernel can recognize it and it is attached, it will be in
> > cat /proc/partitions
> >
>
> Here is what my NVME Solid State drive partitions look like:
> cat /proc/partitions
> major minor #blocks name
>
> 259 0 500107608 nvme0n1
> 259 1 257007 nvme0n1p1
> 259 2 2097152 nvme0n1p2
> 259 3 16793600 nvme0n1p3
> 259 4 480959815 nvme0n1p4
>
> What is it that you are trying to mount?
The OP has already been asked that, but apparently refuses to post
> On Thu, Aug 11, 2022 at 11:21 PM Dan Ritter <d...@randomstring.org> wrote:
> > Albretch Mueller wrote:
> > > Sorry, for my late reaction. I'd wish I could dedicate myself to
> > > coding and reading only. This is what blkid and hwinfo are telling me
> > > and I know that that SSD is not sda or sdb, nor is it the DVD; so,
> > > what is it and how do I mount that SSD
> > > Isn't it weird that I don't see it on blkid or hwinfo? Could that
> > > possibly be some kind of BIOS problem. I want to install Debian on
> > > that box, but I want to make sure I can use the SSD.
> >
> > If the information you have presented is correct, there is no
> > way to use the SSD. There is no evidence that it exists.
> >
> > If the kernel can recognize it and it is attached, it will be in
> > cat /proc/partitions
> >
>
> Here is what my NVME Solid State drive partitions look like:
> cat /proc/partitions
> major minor #blocks name
>
> 259 0 500107608 nvme0n1
> 259 1 257007 nvme0n1p1
> 259 2 2097152 nvme0n1p2
> 259 3 16793600 nvme0n1p3
> 259 4 480959815 nvme0n1p4
>
> What is it that you are trying to mount?
that information except in a very oblique manner.
https://lists.debian.org/debian-user/2022/07/msg00666.html
> > and
> > ls -al /dev/disk/by-id/
> >
> > Since you can't see it there, it is not usable.
David.
0 new messages