On Tue, Jan 01, 2019 at 06:07:21AM -0600, Richard Owlett wrote: > I am trying to modify the partitioning of a 240GB USB connected SSD. > It was originally created on a laptop running Debian 9.1 which is in > the shop for cooling problems. > > I attempted to repartition it on a laptop running Debian 8.6 and > received an error message that the installed revision of e2fsck > could not analyze the first partition. > > I then tried to perform the repartitioning on a machine I believe to > be running Debian 9.1. > > *FIRST QUESTION* > How do I determine just what Debian release is running?
To a first approximation: tomas@trotzki:~$ cat /etc/debian_version 9.6 Since it's possible to install packages from other releases (cf. FrankenDebian) or from alien repositories, this is just a first approximation. > When I attempted the repartition on the second machine the error report was: > >GParted 0.25.0 --enable-libparted-dmraid --enable-online-resize > > > >Libparted 3.2 > >Shrink /dev/sdc1 from 124.96 GiB to 80.00 GiB 00:00:00 ( ERROR ) > > > >calibrate /dev/sdc1 00:00:00 ( SUCCESS ) > > > >path: /dev/sdc1 (partition) > >start: 2048 > >end: 262051839 > >size: 262049792 (124.96 GiB) > >check file system on /dev/sdc1 for errors and (if possible) fix them > >00:00:00 ( ERROR ) > > > >e2fsck -f -y -v -C 0 /dev/sdc1 00:00:00 ( ERROR ) > > > >Possibly non-existent device? > >e2fsck 1.43.4 (31-Jan-2017) > >e2fsck: No such file or directory while trying to open /dev/sdc1 > > It is obviously *NOT* a "non-existent device" as it is readable on > another machine. Note that this device doesn't have to be called /dev/sdc* on your current machine. The kernel just picks whatever /dev/sda, /dev/sdb... is free and allocates it. Those names are not permanent. Stick your device into the USB port, and shortly thereafter do an tomas@trotzki:~$ sudo dmesg | tail [sudo] password for tomas: [ 417.445120] scsi host6: usb-storage 3-2:1.0 [ 417.445316] usbcore: registered new interface driver usb-storage [ 417.447343] usbcore: registered new interface driver uas [ 418.470251] scsi 6:0:0:0: Direct-Access SanDisk Cruzer Blade 1.20 PQ: 0 ANSI: 5 [ 418.471271] sd 6:0:0:0: Attached scsi generic sg1 type 0 [ 418.472287] sd 6:0:0:0: [sdb] 31266816 512-byte logical blocks: (16.0 GB/14.9 GiB) [ 418.473021] sd 6:0:0:0: [sdb] Write Protect is off [ 418.473028] sd 6:0:0:0: [sdb] Mode Sense: 43 00 00 00 [ 418.473295] sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 418.482812] sd 6:0:0:0: [sdb] Attached SCSI removable disk (I just did that). You see, in my case, the device is called "/dev/sdb". Just assuming the device name is somewhat dangerous: you might end up repartitioning (or worse) the wrong one. > *SECOND QUESTION* > What is this telling me? That (most probably) the device didn't end up as /dev/sdc, but possibly as /dev/sdb (because that name was free). Most probably your other machine has two block devices, thus /dev/sda and /dev/sdb are already taken. This is, btw, the reason why nowadays the preferred way is to address the partitions by UUID. HTH -- tomás
signature.asc
Description: Digital signature
