Raspberry Pi Guide

[Yorus]

This post is being processed/translated. The original version will be shown:

Gracias por compartirlo, la verdad es que nunca he intentado ejecutar nada de las X de forma remota y me sonaba todo a chino.

[cobito]

This post is being processed/translated. The original version will be shown:

Lanzar aplicaciones gráficas con SSH no suele ser muy práctico para mi excepto cuando se trata del gestor de archivos. Tener a mano todas las unidades montadas y poder copiar, pegar, eliminar… a velocidad de crucero desde cualquier sitio es un gustazo.

Para todo lo demás: clientes remotos.

[Yorus]

Today your guide has been very useful for me, since the installation steps I have followed vary greatly from what I did the first time. In my case, I downloaded a file that I decompressed directly onto the SD card and when I started the Raspberry, it did a classic Debian Netinst style installation downloading almost everything from the internet and leaving me with a typical root user and a normal user at the end.

Now I have followed your guide and the only different step is that I have flashed the image onto the SD card through Linux.

By the way, I like the change on your page, the new fonts look great.

[cobito]

Well, here's another one with data corruption on the SD. I was updating the system when messages started appearing about problems with the file system. I rebooted but it wouldn't start up again. I put the card in a PC, ran an fsck and it had a lot of messed up i-nodes. I'll see if I can recover it and if not, format it.

I read somewhere that doing an overvolt fixes the problem. This is a real pain because now you have to go messing around with things that could fry the raspi. You have to be careful with backups. I hope I haven't lost my MySQL databases.

[Yorus]

I put a Panasonic SD class 6 4Gb in it and we'll see how long it lasts, because it has been on for several days but it is not working. I hope we don't have to fiddle with it much so that it doesn't cause more problems with the SD card.

[Yorus]

I already have the transmission running at full capacity, but I have a question about how to access the data from another computer. I couldn't set up NFS because of some package that I can't remember that isn't available. I did set up SAMBA, although that only works for the local network.

What I need is to be able to access it even if it's through SSH using the file browser (nemo, nautilus or whatever it is) and many times I find that I can't do certain things because the user is not root. How do you usually do it? Do you give permissions to the normal user in those folders including the one of the web server? Or on the contrary do you create a real root user? Sometimes I get confused with this, and it's also not clear to me if it's better to give permissions to the external disk through fstab or giving permissions to the folder in which it is mounted, since I get confused when touching things and in the end I don't know which one makes it work well.

[cobito]

Section 7.2 of the guide explains how to start an FTP server whose root directory is the root of the Raspi, so in principle you could access all your storage devices in /media.

Section 10.1.3 explains how to manage files remotely using Dolphin (the KDE file manager) via SSH.

The owner of your downloaded files should be 'pi' so using the technique in section 10.1.3 you will be able to do whatever you want with them.

If you want to be able to manage files and folders whose owner is 'root','mysql' or any other different from 'pi' you will have to change the password of 'root' using the commands;
sudo -s
passwd root

Once you have done that, you can use the procedure in section 10.1.3 again using 'root' as the username and the password you have set.

I have not tried it, but I am sure that the file managers of other desktop environments also allow remote file management via SSH.

Another possibility is to follow the procedure in 10.1.2. The only drawback is that you will only be able to manage as 'pi' since for some reason it is not possible to launch X applications like 'root' from SSH.

[Yorus]

It's curious, yesterday from the PC that is inside the local network I couldn't create files/folders inside the transmission downloads folder with SSH (but with Samba), but right now through the internet I can. I don't know what would happen, but in both PCs I use the same Linux and they are configured almost the same way. Where I don't have permissions is in /var/www, although I imagine it's about giving them and that's it, but I don't know if it's convenient or it's better to do the operations as root activating it as you said. By the way and for those who are interested, from Cinnamon (file browser Nemo) you would access with a simple sftp://pi@x.x.x.x/.

[deeiivid]

As cobito told you, in the guide you have how to set up an ftp server.
Although I recommend SFTP (FTP over SSH) since FTP servers, as I understand it, do not encrypt anything, not even the access key, so if you are going to enter from a network that you do not have totally controlled it is not entirely recommended.

Regarding ROOT permissions when running the X's through SSH, I do not know about raspberrian but in debian I have no problems and with lubuntu I did not have any either. I run Pcmanfm without problems as root.

[Yorus]

What a streak I'm on. I was messing around with Apache and had decided to configure it to have the folder where the page is saved in the user's home instead of in /var/www, but with all the messing around I've done I've preferred to uninstall Apache and when I restart to make sure it doesn't accept SSH connections although it does ask for the password. As a curiosity, it does allow me to connect to the Transmission web interface.

Well, I have to wait again until Wednesday or do 20 extra kms tomorrow to restart the machine correctly :mad:

[cobito]

@Yorus:

What a streak I'm on. I was messing around with Apache and had decided to configure it to have the folder where the page is saved on the user's home instead of in /var/www, but with all the messing around I've done I've preferred to uninstall Apache and when I restarted to make sure it turns out that it doesn't accept SSH connections although it does ask for the password. As a curiosity it does allow me to connect to the Transmission web interface.

So, I have to wait again until Wednesday or do 20 extra kms tomorrow to restart the machine correctly :mad:

I feel identified. In my case the journey is 150 km. The curious thing is that sometimes it fixes itself. I think all this is related to the issue of SD card data corruption.

In a couple of weeks I'll start investigating how to install Raspbian on the external hard drive to have the least possible access to the SD card.

PD: Yorus, I edited your post without wanting to. I clicked edit instead of quote and I started writing as happily as if it were a new post :facepalm:. I left it exactly as it was.

[deeiivid]

@Yorus:

What a streak I'm on. I was messing around with Apache and had decided to configure it to have the folder where the page is saved on the user's home instead of in /var/www, but with all the messing around I've done I preferred to uninstall Apache and when I restarted to make sure it turns out that it doesn't accept SSH connections although it does ask for the password. As a curiosity, it does allow me to connect to the Transmission web interface.

So, I have to wait again until Wednesday or do 20 extra kms tomorrow to restart the machine properly :mad:

I didn't think twice and told him to turn it off instead of restarting :ugly: :ugly:

@cobito:

I feel identified. In my case the journey is 150 km. The curious thing is that sometimes it fixes itself. I think all this is related to the issue of SD card data corruption.

In a couple of weeks I'll start investigating how to install Raspbian on the external hard drive to have the least possible access to the SD card.

PD: Yorus, I edited your post without meaning to. I clicked edit instead of quote and started writing as happily as if it were a new post :facepalm:. I left it exactly as it was.

Exactly like me, 150 km. But well I waited for it to be my turn to go... because if not...

I'm surprised by the amount of problems you're having with the SD issue... how is it possible so much data corruption? maybe it's a Raspbian thing?

[Yorus]

I still have to confirm that it's a matter of the SD card again, but given what I've seen, there are many possibilities. We'll see when I look at it on Wednesday.

The thing about turning off instead of restarting sounds familiar to me, but my case was a bit different, since I had two terminals open, the one on the raspberry via SSH and the one on the local computer, and believing I was with the raspberry I did a'sudo reboot' of the PC with a lot of things open :ugly:. It didn't ask for a password because I was tinkering around and let's say that the permissions hadn't expired yet.

[Yorus]

I feel bad linking several posts in a row, but if I don't, the notifications that someone has written won't arrive.

Well, I'm in front of the beast and I can't log in directly to the machine, it says:

Cannot execute: No such file or directory 

I had enabled root but I can't log in as root or as pi.

[cobito]

Insert the card into a PC with Linux and without mounting it, type in the console
fsck -f /dev/sdb2

Note that sdb is the device corresponding to the SD card if you only have one hard drive and there is nothing in the optical drives. If you are not sure (you can mess things up if you make a mistake), type:
df -h

There look at the device (first column) that corresponds to your SD card based on capacity. If you are not sure, mount it and run df -h again, using the mount point to locate it. REMEMBER TO UNMOUNT IT BEFORE RUNNING FSCK OR YOU WILL LOSE EVERYTHING.

Remember to add the 2 after sdX because that indicates the partition. If you don't, it will give a superblock error.

If you see that the number of errors is very large, run

fsck -fy /dev/sdb2

and everything will be automatically confirmed.

Run it several times until there are no errors.

[Yorus]

Coincidentally it is also sdb2, but it doesn't throw errors:

sudo fsck -f /dev/sdb2 fsck from util-linux 2.20.1 e2fsck 1.42.5 (29-Jul-2012) Step 1: Checking i-nodes, blocks and sizes Step 2: Checking directory structure Step 3: Checking directory connectivity Step 4: Checking reference counts Step 5: Checking group information summary /dev/sdb2: 71793/245760 files (0.2% non-contiguous), 453837/954880 blocks  

And it continues with the same error. I don't know, I'm going to opt for a clean installation again to see if messing around with permissions and other things with Apache has messed something up. I could try to recover it from the PC, but I think it would take me less time this way and I can make sure that the Apache issue is back in place.

[cobito]

Now the same thing happens to me. The problem is that the services that depend on MySQL also cannot contact the database even though the web server is working fine. If I don't find a solution to these problems I'm going to have to look for an alternative. The services that run on the Raspi are not used for critical things, but I have to have some confidence that I will be able to resort to them when I want.

[Yorus]

Well, we're in a bit of a pickle. Let's see if I can give it another try this weekend and start investigating these glitches, firmware, etc...

[hjt123]

¡Esta publicación está eliminada!

[Yorus]

I'm still struggling with the setup. I followed this guide to move almost everything to the external hard drive, as the file system has once again been messed up: http://belinuxmyfriend.blogspot.com.es/2012/11/arrancando-la-raspberry-pi-desde-un.html and it worked except for the step of making the root partition take up the whole disk, because it tries to do it on the next reboot but fails. I decided to connect the disk to the laptop again and did it with Gparted without any problems, the only thing is that it keeps trying (and failing) to resize the partition on each boot. Another problem I encountered, but before doing all this, is when doing the update of raspy-config, which causes it not to work on the next reboot. We'll see how it goes after the apt-get upgrade I'm doing now, but I'm considering going back to the old C7 for these issues and I'll keep messing around with this one more calmly, but at least have something that gives me service.