Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Disk model: ST500LT012-1DG14
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x6077e745

Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 968802303 968800256 462G 83 Linux
/dev/sdb2 968804350 976771071 7966722 3.8G 5 Extended
/dev/sdb5 968804352 976771071 7966720 3.8G 82 Linux swap / Solaris

Partition 2 does not start on physical sector boundary.


Disk /dev/sda: 111.8 GiB, 120034123776 bytes, 234441648 sectors
Disk model: CT120BX500SSD1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x4a9856dc

Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 3905535 3903488 1.9G 82 Linux swap / Solaris
/dev/sda2 * 3905536 234440703 230535168 110G 83 Linux
user@debian:~$

gotta sleep now zzz ta for help so far hope to catch you tomorrow :-)

ps it was the sudo command that worked

they're your hdd's try another one if you like. then you can go back to that one when you have more time to mess with it to figure out what is wrong with it.

tried another hdd, a 300gig one this time with same results. Debian 'sees' the drive and everything on it, but i cant write to it at all. my take on this is that the drives fine and that i just need to use correct combination of commands in terminal to resolve. Completely beyond my level of competence im afraid, so help still required im afraid.

i just tried this:

sudo chmod 777 /path/to/drive -R
[sudo] password for user:
chmod: cannot access '/path/to/drive': No such file or directory
user@debian:~$

:-(

If it is not an USB-drive look into /etc/fstab how it is mounted from there.

ive looked in /etc and there is no fstab file.. this is a coreboot machine, maybe that is why?

its a lenovo x230 with ultrabase 3 which contains the additional hdd. v frustrating.

check your connections, the one docking station I seen on YouTube had a DVD player, so I assume you're using one of them replace dvd with hdd caddies. if you do just happen to have a means to connect one of your hdds via usb port via a sata to usb cable then you're going to at least see if they do work, and it is the docking station I'd be looking into the why is it not connecting the hdd in it to the laptop.

Is this possible BW-userx, even though debian can 'see' and read the hdd contents?

BTW, i know the hdd are fully functional, they work in my old thinkpad x201.

so you can see them just not access them. you should be able to lsblk, to get the /dev/sdxx then mount them to a mount point on your system then access the contents within the hdds. if you're docking stations is not letting you do that then ... I'd look at the docking stations connections not allowing access and not the say a USB Port mount. if you can (auto)mount it via USB Port you can change permissions / ownership there then plug it into the docking station and see what happens.

where Xx is the drive letter and partition to mount. last two alphanumerical notations on the string. aka /dev/sd[c2] <-- last two

fyi: you cannot mount the device only its partitions. so
will never work.

i've made some progress on this but not enough. Using gparted i have created two partitions on the hdd, so it must be functional?

im still struggling to be able to write anything onto the hdd, so i have concluded that the problem relates to permissions and/or ownwership. im hoping the following information from terminal will allow someone to help me get the hdd into a useful state, so I can store data on it:

user@debian:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 111.8G 0 disk
├─sda1 8:1 0 1.9G 0 part [SWAP]
└─sda2 8:2 0 110G 0 part /
sdb 8:16 0 298.1G 0 disk
├─sdb1 8:17 0 149G 0 part /media/user/videos
└─sdb2 8:18 0 149G 0 part /media/user/data
user@debian:~$ ls -la /mnt
total 8
drwxr-xr-x 2 root root 4096 Nov 5 15:47 .
drwxr-xr-x 19 root root 4096 Nov 5 16:22 ..
user@debian:~$

after you make a partition ROOT owns it period. Because root is the only one allowed to preform these tasks on the system. or pseudo root, pronounced sudo.

So you as root, or pseudo root using sudo have to give it permissions to let others do stuff to it. You can do this at least two ways that I use.

keep it root owner and give it 777. having it mounted somewhere.
Here on mine you can see root owns it but I a user can read/write/exec from it too.
or you can change it to your user or just the group too is suppose to work.
group
both
so with your partitons as you posted are mounted
or change the ownership whichever why you want your system to be setup.

woowoo!!

Result!!

Thankyou so much for your endurance BW userx. You have enhanced my pc experience :-)

1 members found this post helpful.