DSM-G600, DNS-3xx and NSA-220 Hack Forum

You want to look at:

http://www.inreto.de/dns323/fsck/

This is a package that reboots the machine into a special kernel so that you can run filesystem checks.

When you are done, you just type reboot and your system reboots back to the way you had it.

There is no need to change your current configuration, other than installing this package.

This is a darned nice way to do it.

The above procedure uses fsck to check your disks.  I don't know what you mean by "scandisk".  Another approach is to simply rename your fun_plug file and then reboot, if you want to keep those processes from starting.  Then, you may be able to check your disk.  When done, rename it back to fun_plug and reboot.  You can rename the fun_plug file via the disk share.

Last edited by karlrado (2010-10-15 20:33:39)

I guess those disk tools are not in the 1.07 version of the firmware.

I really would try the rename fun_plug and reboot approach, since that may be easier.  If you disable fun_plug, there should be no processes running that access your data disk and you should be able to scan it from the web page.

Yes, I did check my disks with fsck and it worked well.

the ko files are kernel modules.  If you look in the reload.sh file, you can see how they are used.  Basically that script loads a new kernel and starts running it.  If you follow the instructions to rsync the package, you shouldn't have to worry about the files.

Just be sure that you can get to the device with telnet before you do it.  That is, you have a computer on the same LAN that has a telnet client.

The nice thing about this approach is that simply rebooting the system will get you back to where you were.  You don't have to worry about doing something wrong in a fun_plug script.

The commands to use and pointers to more info are actually given in http://www.inreto.de/dns323/fsck/.

And it depends on what sort of checking you want to do.  It is probably a good idea to understand fsck before using it.  Since it can be used to fix disks, thus altering them, it is a powerful tool.

My RAID1 firmware 1.08 box appeared to be having disk problems: noise from box, on reboot the entire lot disappeared!  As in nfs mount the drive, cd to it, and nowt!

I removed each disk and each looked OK.  Mounted them on a linux box as ext3 and all the data seemed there.

Put them back, scandisk didn't work, and a large copy failed with stat errors indicating I might have a disk issue.

  So I tried the reboot to fsck as mentioned above. ran the RAID commands as specified in the readme.

No errors found.

But when I rebooted, now the GUI says

The hard drives have been installed incorrectly. Please shut down the system and swap hard drive locations.

The disks seem fine from funplug! and mounted as NFS.  So it appears the fsck did something odd to the RAID config info?

Going through the forum I can only find info for this error from much older firmware revisions, and they all seem to say 'reformat everything" which is not really something I want to do if I can avoid it!

mdadm seems to think all is OK.

/mnt/HD_a2/ffp/sbin # ./mdadm --detail /dev/md0
/dev/md0:
        Version : 00.90
  Creation Time : Sat May 29 17:30:01 2010
     Raid Level : raid1
     Array Size : 1462766336 (1395.00 GiB 1497.87 GB)
  Used Dev Size : 1462766336 (1395.00 GiB 1497.87 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Mon Oct 18 20:55:49 2010
          State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
  Spare Devices : 0

           UUID : e99bdb2b:2eb17602:58d61627:dcce2a11
         Events : 0.531559

    Number   Major   Minor   RaidDevice State
       0       8       18        0      active sync   /dev/sdb2
       1       8        2        1      active sync   /dev/sda2