search for: goflex

I have several devices, mostly amd64 and armhf architectures, all of which updated samba to 4.17.6 without any problems. But one which is armel architecture failed to update; instead I get the following when I try to update: root at goflex:~# samba -V Version 4.17.5-Debian root at goflex:~# apt update Hit:1 http://ftp.uk.debian.org/debian bullseye InRelease Get:2 http://ftp.uk.debian.org/debian bullseye-backports InRelease [49.0 kB] Get:3 http://www.corpit.ru/mjt/packages/samba bullseye/samba-4.17/ InRelease [2325 B] Hit:4 https://pk...

.../proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) /dev/sda1 on /boot type ext4 (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) /dev/sdb1 on /media/GoFlex type ext3 (rw,nosuid,nodev,uhelper=udisks) ======================================================================================== The following mount command was issued by inserting the external USB drive in a powered down computer and then booting. Note the sdb3 is / and sdb1 is /boot. [root...

...last time the device was unmounted it was a normal unmount. > > Now, when I try to mount the device, I get the following in dmesg: > > usb 2-1: new high speed USB device using ehci_hcd and address 4 > scsi6 : usb-storage 2-1:1.0 > scsi 6:0:0:0: Direct-Access Seagate FreeAgent GoFlex 0148 PQ: 0 ANSI: 4 > sd 6:0:0:0: Attached scsi generic sg2 type 0 > sd 6:0:0:0: [sdb] 1953525167 512-byte logical blocks: (1.00 TB/931 GiB) > sd 6:0:0:0: [sdb] Write Protect is off > sd 6:0:0:0: [sdb] Mode Sense: 1c 00 00 00 > sd 6:0:0:0: [sdb] Assuming drive cache: write through &gt...

Hi all, I have a box, until warranty (I may not open it) and 2 external USB hard drives. My perfect solution is to open the box, plug the drives on the SATA slots, and use them. Unfortunately, I'll have to fall back to the cheap solution: I would like to use each external drive as physical volume (PV) and then "join" them as a VG in order to use a LVM composed by internal