You are not logged in.
Hmm now that you've confirmed it's 2 TB...I'm wondering if it couldn't see it because of the BIOS itself.... Is this a 32 or 64bit cpu you have in the laptop? Coupled with the fact that it's using some odd cdrom conversion...I'm wondering if the drive is too big....?
Hi,
tried installing it in the laptop itself after you mentioned this... got to thinking of the TB limit itself but I can install an OS on it, tried putty linux for a fast test.
The laptop itself:
Lenovo ThinkPad T420
Intel i5 2.5 GHz Dual-Core CPU (64-bit)
Intel HD 3000 Graphics
4GB Ram
128GB SSD (bl installed on it)
Last edited by UnderMiner (2016-10-20 11:45:56)
"Computers are like Old Testament gods; lots of rules and no mercy."
- Joseph Campbell
Offline
I'd say it's highly probable the cause is the drive caddy, they tend to be pressed ally, knocked out at high speed by Chinese workers on piece rate, who don't want to lose wages calling a setter to the press when the tooling gets slightly out of alignment, *if* it was ever set accurately to start with. These accessories are built to a price, at least the common ones you see on internet auction sites are, without the demands of quality a laptop OEM would make, consequently the odds that the SATA connector won't align properly go way up in comparison to the optical drive the OEM would supply, I doubt it's any more than bad luck with the fit and finish of that particular drive caddy.
Blessed is he who expecteth nothing, for he shall not be disappointed...
If there's an obscure or silly way to break it, but you don't know what.. Just ask me
Offline
Tried all the commands but nothing worked.
What does this actually mean?
If there was no output at all from `dmesg -w` or `udevadm monitor` then there must be a problem with the drive and/or connector/cable.
Offline
Well, nothing happened when I put the caddy in while the laptop was on. Like Bearded says, it's probably the caddy that's damaged or not made correctly.
Anyway it's not a huge problem as I can return it free of charge and get a replacement . the downside is that they're not in stock until 22nd of November 8.(. Then again, that leaves me time to fiddle with something else in my bl install
"Computers are like Old Testament gods; lots of rules and no mercy."
- Joseph Campbell
Offline
For reference, this command will give you lots of useful information. It is similar to dmesg | tail:
journalctl -xf
If you need to dig back into the past boot and see what went wrong you can use
journalctl -xb
I usually keep a terminal up with journalctl -xf so I can keep tabs on what my system is doing.
Offline
Hi again guys/girls,
got the new caddy and it works like a charm. GParted sees the HDD, it's been formatted and all but I can't seem to access the disk nor make any folders. In GParted it shows a small "lock" after /dev/sdb1, is that supposed to be there? Mountpoint says it's
/media/antonio/a73e8cd-aacf-4f729fdd5fcfc23ce545
but I have no idea what those numbers and letters mean. Any help would be very appreciated.
- EDIT -
I can open the HDD as root and make folders but I dare not do anything as root as I've read some terrifying tales about what can go wrong. What do I do to change it so that I can access it from my "normal" account? Is it something with permissions?
Last edited by UnderMiner (2016-11-17 18:31:40)
"Computers are like Old Testament gods; lots of rules and no mercy."
- Joseph Campbell
Offline
How are you mounting the drive?
Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt «» BunsenLabs on DeviantArt
Offline
/media/antonio/a73e8cd-aacf-4f729fdd5fcfc23ce545
but I have no idea what those numbers and letters mean. Any help would be very appreciated.
- EDIT -
I can open the HDD as root and make folders but I dare not do anything as root as I've read some terrifying tales about what can go wrong. What do I do to change it so that I can access it from my "normal" account? Is it something with permissions?
I believe the /media/antonia/ xxxxxxxxxxxxxxxxxxxxxxx number is the drive's UUID.
if you run the 'blkid' command by itself, you'll see a list of all the drives and their UUID's.
"I have not failed, I have found 10,000 ways that will not work" -Edison
Offline
- damo -
I don't know how I mounted the drive... I opened GParted and formatted it and it just shows up after each reboot which I guess is a good thing.
- horizon -
It does indeed seem like it's the UUID of the drive, but it was also the name which I changed to "data" in case I need to write something in the terminal to make it all work . Easier than writing the whole string hehe.
So, how do I get from this stage to being able to access the drive from my account without having to use my password to open it as root (it says that the owner is root)? I'm not entirely sure I'm not just missing something very basic here but as I've stated earlier I'm totally new to linux
Last edited by UnderMiner (2016-11-17 20:37:59)
"Computers are like Old Testament gods; lots of rules and no mercy."
- Joseph Campbell
Offline
If you hotplug the drive, check the settings in Thunar -> Edit -> Preferences -> Advanced -> Configure;
Otherwise you can add a mountpoint in /etc/fstab, so it mounts when you boot. An example from my fstab here:
# data on /dev/sdb1
UUID=7101014f-1f15-402e-8ea4-4aa255a0d2a0 /mnt/data ext4 rw,user,auto 0 2
NB the mountpoint must be created first, and you can get the UUID of the drive from the blkid command. There are more up-to-date methods, but I still use this old way!
Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt «» BunsenLabs on DeviantArt
Offline
If you hotplug the drive, check the settings in Thunar -> Edit -> Preferences -> Advanced -> Configure;
Otherwise you can add a mountpoint in /etc/fstab, so it mounts when you boot. An example from my fstab here:
# data on /dev/sdb1 UUID=7101014f-1f15-402e-8ea4-4aa255a0d2a0 /mnt/data ext4 rw,user,auto 0 2
NB the mountpoint must be created first, and you can get the UUID of the drive from the blkid command. There are more up-to-date methods, but I still use this old way!
It mounts fine and all as it is now, shows up on reboot and I can access it. The thing is that if I want to create folders/use the drive, I need to log in as root which I don't want to do. The drive mounts as /media/antonio/data so as far as I understand I should have permissions on the drive when it's under my username (I may have the short end of the stick here )
It's not a drive that I take out of the PC, it's in a drive caddy where the DVD drive normally goes.
Last edited by UnderMiner (2016-11-17 20:43:57)
"Computers are like Old Testament gods; lots of rules and no mercy."
- Joseph Campbell
Offline
The drive mounts as /media/antonio/data so as far as I understand I should have permissions on the drive when it's under my username
Yes, you should be able to write to the drive just fine as a normal user, modifying /etc/fstab should not be needed at all.
Can you modify the drive if you load the BunsenLabs ISO image and select the "live session"?
Offline
please open a terminal in the base directory of the mounted drive and enter
ls -al
and post the output.
Offline
- ohnonot -
ls -al gives
antonio@BunsenLabs:/media/antonio/data$ ls -al
totalt 24
drwxr-xr-x 3 root root 4096 nov 17 19:16 .
drwxr-x---+ 3 root root 4096 nov 17 21:24 ..
drwx------ 2 root root 16384 nov 17 19:16 lost+found
antonio@BunsenLabs:/media/antonio/data$
- Head on a stick -
Don't know if I can, my son took the DVD with bl on it and I don't have any more DVDs at home. It's 22:15 here now so there're no places to get some new ones (that's 10:15pm).
Can I
sudo chown
something-or-other?
Last edited by UnderMiner (2016-11-17 21:21:17)
"Computers are like Old Testament gods; lots of rules and no mercy."
- Joseph Campbell
Offline
It's 22:15 here now so there're no places to get some new ones (that's 10:15pm).
Hey, no rush -- I'm here all week
Can I
sudo chown
something-or-other?
No, don't do that.
Offline
Can I
sudo chown
something-or-other?
No, don't do that.
why not on an empty hdd?
in fact i think they'll have to if they want user rights?
Offline
why not on an empty hdd?
Because it shouldn't be needed.
BunsenLabs uses gvfs & udisks(?2) to enable a normal user to write to an automounted device.
Offline
but if if the file system is owned by root? doesn't that need to be chowned? i'm not quite sure how gvfs/udisks et.al. can change the owner?
Offline
i'm not quite sure how gvfs/udisks et.al. can change the owner?
IIRC, it creates a new, user-owned mountpoint, named after the UUID of the device.
I will have to check all this when I have access to my BL system (not tonight).
Offline
Figured it out after all .
Opened the drive as root and changed the permissions for the drive to include my user so now I can create folders and do whatever I want on the drive yaay. Was so afraid to do anything as root but after going through my options as a normal user I figured I'd give it a try hehe.
Thanks for all your help guys. I'm glad there's a great forum for things like this. Take care.
- EDIT -
Marked this one as solved
Last edited by UnderMiner (2016-11-17 21:50:55)
"Computers are like Old Testament gods; lots of rules and no mercy."
- Joseph Campbell
Offline