Updated Dayna Port SCSI Link (markdown)

Daniel Markstedt 2021-10-29 08:49:04 -07:00
parent 4e9cceb298
commit 54bb7c23a8
1 changed files with 4 additions and 20 deletions

@ -12,31 +12,15 @@ The instructions for the wired network use case assumes that you're using a DHCP
# <img src="images/rpi_logo.png" alt="Raspberry Pi" height="30"> Raspberry Pi Setup
Depending upon which use case matches your situation, the Raspberry Pi configuration will be slightly different.
<table style="border: 1px solid red"><tr><td>
<span style="color:red">Currently the DaynaPort functionality is only on the `develop` branch. You will need to checkout that version of RaSCSI to try it out</span>
</td></tr></table>
## Automated Setup
- Download and install latest version of RaSCSI:
```
cd ~
# Install git and clone RaSCSI if you haven't:
sudo apt install git
git clone https://github.com/akuker/RASCSI.git
# Install or update RaSCSI:
cd ~/RASCSI
git checkout develop
./easyinstall.sh # Select option 1 to install or update, or option 0 if you need a new drive image as well
```
- Download and install latest version of RaSCSI by following the [[setup instructions]].
- Run the network bridge setup script for wired or wireless:
```
# Scripted network configuration:
./easyinstall.sh # Select option 5 to configure wired, and 6 to configure wireless bridge
./easyinstall.sh # Select option 6 to configure wired, and 7 to configure wireless bridge
```
- Let the Pi reboot, and attach a DaynaPORT adapter to your RaSCSI as instructed in the script
@ -139,7 +123,7 @@ There are four ways to accomplish this:
1. Launch 'rascsi' with parameters on the command line (when not running as a service)
2. Edit the rascsi.service configuration to attach devices on launch (when running as a service)
3. Use 'rasctl' to dynamically attach the device on a running rascsi instance
4. Use the Web UI to attach the device
4. Use the [[web interface]] to attach the device
Note that by default, the DaynaPORT device will launch with parameters 'eth0,wlan0' meaning it will attempt to use eth0 first, and if unavailable then wlan0. Also, note that the default IP address / netmask is 10.10.20.1/24. So for most usecases, if you follow the automated process and use the default values, you don't have to specify any parameters when attaching the DaynaPORT device and it should work out of the box.
@ -161,7 +145,7 @@ Ex. with rasctl / wireless / static IP, RaSCSI already running
Here you have two options. Either have the RaSCSI Web UI read your *default* configuration file on startup, or hard code the launch parameters in the rascsi.service ExecStart argument. The latter is more permanent, while the former can be managed more easily through the Web UI. Also note that the Web UI configuration will override whatever is defined in rascsi.service.
- Web UI configuration option:
Once you've attached your DaynaPORT device with just the right parameters, you can save that as a RaSCSI Web UI configuration file. If you name it *default* (~/images/default.json) that configuration will be loaded when the Web UI starts up for ultimate convenience!
Once you've attached your DaynaPORT device with just the right parameters, you can save that as a RaSCSI Web UI configuration file. If you name it *default* (~/.config/rascsi/default.json) that configuration will be loaded when the Web UI starts up for ultimate convenience!
- rascsi.service ExecStart option:
Modify your service startup script to automatically add the DaynaPort at startup. To do this, open `/etc/systemd/system/rascsi.service` with a text editor. Modify the ExecStart line to add the ID and device. For example: