The easiest way to put rootfs.img in the Public folder is just to transfer it through the good old windows network to the Public folder. If you want to do it through SSH though, yes it is at /DataVolume/shares/Public (The transfer rate is lower through ssh if I remember correctly) Don’t forget to delete or overwrite the old MBL Duo rootfs.img that is there from when you ran the script the first time.
For question number 2, no you will not get a response back from mount /dev/sda4 (This is good, it means your data volume is mounted)
To verify it is mounted after issuing that command, type
mount
and hit enter
You should see it in the mounts list (This is possible because I took the MyBookLive mtab file and uploaded it for you to replace the MBL Duo one which will not let you mount /dev/sda4 (your datavolume) without some editing.
You need the DataVolume mounted so you can put the rootfs.img file in the Public folder and then you can re-run the script against the proper firmware file.
My datavolume is already mounted as you can see in the below PuTTY log but I just wanted to show you what it should look like
login as: root
root@192.168.1.6's password:
Linux MyBookLive 2.6.32.11-svn52288 #1 Wed Oct 26 18:57:59 PDT 2011 ppc
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Disclaimer: SSH provides access to the network device and all its
content, only users with advanced computer networking and Linux experience
should enable it. Failure to understand the Linux command line interface
can result in rendering your network device inoperable, as well as allowing
unauthorized users access to your network. If you enable SSH, do not share
the root password with anyone you do not want to have direct access to all
the content on your network device.
MyBookLive:~# mount /dev/sda4
mount: /dev/sda4 already mounted or /DataVolume busy
mount: according to mtab, /dev/sda4 is already mounted on /DataVolume
MyBookLive:~# mount
/dev/md0 on / type ext3 (rw,noatime,nodiratime)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755,size=50M)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,size=50M)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
tmpfs on /tmp type tmpfs (rw,size=50M)
/var/log on /var/log.hdd type none (rw,bind)
ramlog-tmpfs on /var/log type tmpfs (rw,size=20M)
/dev/sda4 on /DataVolume type ext4 (rw,noatime,nodiratime)
/DataVolume/cache on /CacheVolume type none (rw,bind)
/DataVolume/shares on /shares type none (rw,bind)
/DataVolume/shares on /nfs type none (rw,bind)
none on /sys/kernel/security type securityfs (rw)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)
MyBookLive:~#
 Here is script output from PuTTY when you run resetButtonAction.sh
login as: root
root@192.168.1.6's password:
Linux MyBookLive 2.6.32.11-svn52288 #1 Wed Oct 26 18:57:59 PDT 2011 ppc
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Disclaimer: SSH provides access to the network device and all its
content, only users with advanced computer networking and Linux experience
should enable it. Failure to understand the Linux command line interface
can result in rendering your network device inoperable, as well as allowing
unauthorized users access to your network. If you enable SSH, do not share
the root password with anyone you do not want to have direct access to all
the content on your network device.
MyBookLive:~# /usr/local/sbin/resetButtonAction.sh
currentRootDevice = /dev/md1
upgradeRootDevice = /dev/md0
Ensure both partitions are members of the original MD device
mdadm: hot remove failed for /dev/sda1: Device or resource busy
mdadm: Cannot open /dev/sda1: Device or resource busy
mdadm: hot remove failed for /dev/sda2: Device or resource busy
mdadm: Cannot open /dev/sda2: Device or resource busy
Setting up the upgraded raid unit
mdadm: /dev/sda1 appears to contain an ext2fs file system
size=1999808K mtime=Wed Dec 31 16:00:01 1969
mdadm: size set to 1999808K
mdadm: creation continuing despite oddities due to --run
mdadm: array /dev/md0 started.
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
125184 inodes, 499952 blocks
24997 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=515899392
16 block groups
32768 blocks per group, 32768 fragments per group
7824 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Checking for bad blocks (read-only test): done
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 20 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
Copy image to upgrade device /dev/md0
3999616+0 records in
3999616+0 records out
2047803392 bytes (2.0 GB) copied, 121.793 s, 16.8 MB/s
all done, now rebooting
Broadcast message from root@MyBookLive (pts/0) (Thu Oct 18 06:04:42 2012):
The system is going down for reboot NOW!