Jun 142013
 

Not sure if this will be of use to anyone but I’ve decided to release it anyway…

I’ve split RSE2.4 into a directory and an image file.
The directory contains all the boot files that RSE needs to boot up, and the image file is meant to be dd’ed onto a USB stick or Hard drive.
As the image file is a partition, it should be dded onto a partition
e.g.

dd if=RSE2.4.HD.img of=/dev/sda1 bs=1M

The distro itself is the same as RSE 2.4 with the exception that it’s split over 2 devices.

You can download the zip file from here

SHA1SUM –
583ad4e16b0b56d686ddee84af471a67c5103b8f RSE2.4HD.zip
I updated RSE 2.4, so this is the new SHA1 sum
461d595a5eb646da97bd2d751f05d9dcfdf96204 RSE2.4.HD.img

Share

  11 Responses to “Raspbian Server Hard Drive Edition 2.4”

  1. What kind of scenario is this useful for?

    • Server with root partition on a usb hard drive rather than a SD card ?

      Make partitioning easier, hopefully less chance of corruption too.

  2. I’ve a problem. Raspberry pi don’t found /dev/sda1 during the boot

    • Does it pick up any removable drives ? Are you using a usb hdd or usb stick ?

      Is the usb storage plugged straight into the Pi or into a USB hub ?

  3. I use one hard drive
    Solved with replace :

    /dev/sda1 (/boot/cmdline.txt)
    with /dev/sda

    I have use this command dd if=/../RSE.HD.img of=/dev/sdX
    ( i have use /dev/sda but no /dev/sda1 )

  4. it’s necessary to add in /etc/fstab
    /dev/sda1 ?
    Because root is monted with dev/mmcblk2

    • No…
      This is how mount should look

      /dev/root on / type ext4 (rw,noatime,data=ordered)
      devtmpfs on /dev type devtmpfs (rw,relatime,size=86184k,nr_inodes=21546,mode=755)
      tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=18888k,mode=755)
      tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
      proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
      sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
      tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=37760k)
      devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620)
      /dev/mmcblk0p1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=ascii,shortname=mixed,errors=remount-ro)

      and this is how df -h should look

      Filesystem Size Used Avail Use% Mounted on
      rootfs 1.8G 655M 1018M 40% /
      /dev/root 1.8G 655M 1018M 40% /
      devtmpfs 85M 0 85M 0% /dev
      tmpfs 19M 268K 19M 2% /run
      tmpfs 5.0M 0 5.0M 0% /run/lock
      tmpfs 37M 0 37M 0% /run/shm
      /dev/mmcblk0p1 56M 19M 38M 33% /boot

  5. This is interesting. I am looking at maybe using a Pi as a mail server for my small business. This appeals to me because I run mail servers already and I had a HD die recently that requires me to rebuild one whole mail server and sync data etc to get back to where I was. Regular HDs will die eventually and so I thought why not use a Pi since it uses a SD card and so this is solid state (the Pi is also low power consumption, so is green). However, reading in more detail, it seems that SD cards also die eventually and so this might not be much more reliable than a regular Linux PC with normal HD. Looking at this even more turned up a suggestion that one could move various partitions to a USB drive, such as a SSD and this would mean the bulk of the read/write would be on the SSD not the SD card. The problem is that the partitioning scheme on the Pi seems more complicated than on regular Linux (eg Debian). Your split solution could help a lot with ensuring things work properly. However, I am still confused about how to install things. I have been using a Pi as a wireless media server for some time, so I am familiar with it. I have always installed regular Raspbian by writing an image to the SD card (from Windows so far). Hence, I am not quite sure how one would go about using the folder to get the boot files onto the SD and then dd’ing the image to the SSD (I understand dd, but is the image to be written on the SD card or another USB drive?). Could you maybe give a little step-by-step of the process?

    Many thanks in advance,

    Nick.

    • Hey Nick,

      The process is as simple as copying the boot files onto a SD card, and then dding the image file onto a partition onto the USB storage device.

      Make sure you are copying it to a partition and not to the whole device.
      It’d probably be easier if you’re starting with a storage device that is totally clean, that way you won’t have to worry about losing existing data.

      1. Download
      2. Unzip
      3. Copy boot files to SD Card
      4. dd if=imgfile.img of=/dev/sda1 bs=1M

      That’s pretty much it.

  6. Sorry this is so late, but I think this is excellent.

    As more and more people move “cloud” services into their homes to ward off the eyes of the evil ones (email to avoid yer ISP, ownCloud to avoid Google/Apple etc.)

    The RPi makes an adequate and environmentally friendly server, but SD/USB flash storage is going to be a problem in the fullness of time. This distribution plus a whirl y disk is the answer.

    I found a few snags during the installation, but nothing serious.

    Many thanks and well done.

Leave a Reply to NickH Cancel reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

(required)

(required)