Duo boot problem

You can factory reset with one drive. Note that the other drive would need to be wiped when it is added (it should be added while the NAS is on).

Ok. I'm happy to tell you it's back up and running. Here's what happened:

- After the boot recovery (attempt) I found with Raidar that the IP address had changed.
- No ssh access/web access/anything but ping.
- So tried factory reset (with 1 drive in place) by holding the reset button on the back during Power on.
- The NAS then came to life! With:
-- The new Ip address
-- Raid 1, as if there were 2 disks, 2 green lights (? very strange since there was only 1 disk in)
-- All old data available
- So I changed the NAS back to the old IP address and did a reboot
- It came back on with the message that one disk was missing
- I shut it down, added the second disk, and started it up
- In Raidar and Frontview I could see the new disk, but with a gray LED icon and the message that it was dead.
- Tried a hot-swap pulling it out, and sticking it back in (thats what she said)
- Got some "disk removed" "disk added" notification messages in front view.
- After it was added, it showed with a green LED icon and a red cross (Spare) in Raidar and Frontview.
- I then rebooted and it started mirroring.
- After a day it is now back to it's old self (Whoopie!)

I can't say I understand what happened. Not even sure if I actually did a factory reset, because everything looks exactly the same as before and my data was still there.

Thanks very much for your time and ideas mdgm and StephenB

A factory reset wipes all data. You probably did an OS Re-install (re-installs the firmware and resets some settings, but leaves data intact).

Ok, thanks.
I'm still having some problems. I can't install add-ons because every installation stops with the message: Invalid checksum.

Found some similar posts on this forum, and thats why I ran this:

Bertje:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/md0 1.9G 2.0G 18M 100% /
tmpfs 16k 0 16k 0% /USB
/dev/c/c 1.8T 1.7T 137G 93% /c
/c/home 1.8T 1.7T 137G 93% /home/ftp/homes
/c/backup 1.8T 1.7T 137G 93% /home/ftp/backup
/c/media 1.8T 1.7T 137G 93% /home/ftp/media
/c/shared 1.8T 1.7T 137G 93% /home/ftp/shared

Does this mean the OS disk is full?
How do I determine where the problem lies?

Yes the OS partition is full.

You could use the "du" command to isolate where the problem lies.

Ok. I did this:

Bertje:/var/log# du /dev/md0
0       /dev/md0

And this:

Bertje:/# du -sh /var/log/
655M    /var/log

Can I delete the logs by doing

rm /var/log/*

?

It would be better to look for which logs are too large rather than blindly removing all the logs.

It sounds like there may be some data in other areas of the OS partition taking up a lot of space (e.g. /tmp)

Ok..

Bertje:/var/log# du
3072    ./cups
496     ./exim
64      ./frontview/backup
18096   ./frontview
16      ./ksymoops
16      ./ntpstats
16      ./samba/cores/smbd
16      ./samba/cores/nmbd
48      ./samba/cores
688     ./samba
16      ./ddns
670624  .

So I guess I could delete the frontview logs.

tmp doesnt seem to big:
Bertje:/# du -sh tmp
15M tmp

Is there a way to "du" the OS partition without going through all 2TB of my data files?

I would still check to see which files are too large.

Do e.g.

# ls -la /

Then run du on the folders that are on the OS partition but not your shares on the data volume.

Ok. Notable to me:

Bertje:/# du -sh home
1.7T    home

Bertje:/# du -sh usr
642M    usr

Bertje:/# du -sh var
775M    var

Cant really see whats big in the usr folder. I cant scroll up far enough after the "du -h usr".