brammp/little-backup-box-Bram
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Updated Troubleshooting (markdown)

Dmitri Popov
2017-10-01 15:03:25 +02:00
parent a2013c806a
commit 715715b9dc
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
Troubleshooting.md

@@ -11,6 +11,7 @@ sda 8:0 1 115.7G 0 disk
└─sda1 8:1 1 115.7G 0 part /media/storage └─sda1 8:1 1 115.7G 0 part /media/storage
mmcblk0 179:0 0 14.5G 0 disk mmcblk0 179:0 0 14.5G 0 disk
├─mmcblk0p2 179:2 0 14.4G 0 part / ├─mmcblk0p2 179:2 0 14.4G 0 part /
└─mmcblk0p1 179:1 0 63M 0 part /boot``` └─mmcblk0p1 179:1 0 63M 0 part /boot
```
The important part here is the names (*sdb1* and *sda2*) and mount points (*/media/card* and */media/storage*). If the names are different, you need to adjust the values of the STORAGE_DEV and CARD_DEV variables in the *backup.sh* script. For your convenience, the latest version of the script runs the sudo lsblk command automatically and saves the output in the */root/pi/lsblk.log* file. You can view this file by running the sudo cat /root/lsblk.log command on the Raspberry Pi. The important part here is the names (*sdb1* and *sda2*) and mount points (*/media/card* and */media/storage*). If the names are different, you need to adjust the values of the STORAGE_DEV and CARD_DEV variables in the *backup.sh* script. For your convenience, the latest version of the script runs the sudo lsblk command automatically and saves the output in the */root/pi/lsblk.log* file. You can view this file by running the sudo cat /root/lsblk.log command on the Raspberry Pi.