Low Space on Root - Unable to update firmware


#1

I’d like to update to the latest firmware, but I don’t seem to have enough space on the root partition of the drive.   Here’s the output of an fdisk -l command from the bash prompt:

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/sda1               1          26      208844+  fd  Linux raid autodetect
/dev/sda2              27         156     1044225   fd  Linux raid autodetect
/dev/sda3             157         182      208845   fd  Linux raid autodetect
/dev/sda4             183      121601   975298117+  fd  Linux raid autodetect

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/sdb1               1          26      208844+  fd  Linux raid autodetect
/dev/sdb2              27         156     1044225   fd  Linux raid autodetect
/dev/sdb3             157         182      208845   fd  Linux raid autodetect
/dev/sdb4             183      121601   975298117+  fd  Linux raid autodetect

Here’s the output of a df command from the bash prompt:

Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/md0                  2172      2172         0 100% /old
/dev/md0                202175    180115     11622  94% /
/dev/vg0/lv0         1919986664    176420 1919810244   0% /DataVolume
/dev/ram0                63164        24     63140   0% /mnt/ram
/dev/vg0/lv0         1919986664    176420 1919810244   0% /shares/Public
/dev/vg0/lv0         1919986664    176420 1919810244   0% /shares/Download

As you can see, /dev/md0 is 94% full.  There isn’t enough room for the firmware update to download and extract.  Does anyone know what I might delete to make room?  Here’s the output of an ls -al command from the bash prompt at the base directory of the filesystem:

drwxr-xr-x   27 root     root         1024 May 30 22:08 .
drwxr-xr-x   27 root     root         1024 May 30 22:08 …
-rw-------    1 root     root         1024 May 30 21:04 .rnd
lrwxrwxrwx    1 root     root           17 Sep 23  2009 CacheVolume -> /DataVolume/jewab
drwxr-xr-x    2 root     root         1024 Oct 18  2008 Configuration
drwxr-xr-x    8 root     root         4096 May 30 22:51 DataVolume
drwxrwxr-x    3 root     root         1024 Apr  9  2008 ExtendVolume
drwxr-xr-x    2 root     root         2048 Sep 23  2009 bin
drwx------    2 root     root         1024 Sep 23  2009 boot
drwxr-xr-x    9 root     root         3072 May 30 21:04 dev
drwxr-xr-x   11 root     root         2048 May 30 22:07 etc
drwx------    2 root     root         1024 May 30 22:55 ftmp
drwx------    2 root     root         1024 Sep 23  2009 jewab
drwxrwxr-x    3 root     root         2048 May 21 22:11 lib
lrwxrwxrwx    1 root     root           11 Sep 23  2009 linuxrc -> bin/busybox
drwx------    2 root     root        12288 Oct 18  2008 lost+found
drwxr-xr-x    3 root     root         1024 Sep 23  2009 mnt
drwxr-xr-x    2 root     root         1024 May 30 21:52 nfs
drwxrwxr-x    1 root     root          200 Dec 31  1969 old
drwxr-xr-x   15 root     root         1024 May 29 22:28 opt
dr-xr-xr-x   96 root     root            0 Dec 31  1969 proc
drwxrwxr-x    3 root     root         1024 Apr  2  2009 proto
drwxrwxr-x    2 root     root         1024 May 21 22:22 root
drwxr-xr-x    2 root     root         2048 Sep 23  2009 sbin
drwxrwxr-x    6 root     jewab        1024 May 30 22:05 shares
drwxrwxrwx    6 root     root         2048 May 30 22:59 tmp
drwxr-xr-x    1 root     root            0 May 30 22:04 trustees
drwxrwxr-x    5 root     root         1024 May 30 22:05 twonky
drwxrwxr-x   10 root     root         1024 Apr  2  2009 usr
drwxrwxr-x    6 root     root         1024 Sep 23  2009 var
-rw-------    1 root     root        73539 Jun  1  2008 zf

Any advice is appreciated!


#2

I was able to resolve the issue by taking the drives out of the Sharespace, putting them into an XP computer and deleting the partitions (NOT reformatting the drive, just deleting the existing partitions.)  I then put the drives back into the Sharespace and let it rebuild itself.  I then had 153MB free on the root partition.  When I attempted to update the firmware automatically, it said that I had the latest firmware (this was not the case as I was on 2.1.92)  I had saved the link to the firmware file by pulling the wixFW_downloaded_automatically.wgspider file off the Sharespace previously. The link to the firmware inside that file was listed as http://download.wdc.com/nas/wda4nc40000-02.02.08.img.  I downloaded that file and did a manual update, and now I’m on version 2.2.8 of the firmware and am currently recreating my RAID 1 array.


#3

I really don’t know why I can’t upgrade from 1.0.5 (factory) to the new firmware version 2.2.8, I’ve just downloaded the file from the link you posted but when I tryed to send the file to Sharespace device there is a message “filename of firmware image contains invalid characters”.

Could you help me to identify the apropriate filename for the firmware image file?

thanks.