Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
My left drive had a bad LBA. SeaTools for DOS claims it recovered it.
I put it back in and it re-synced. On the status screen it says:
HARD DRIVE INFO :
Total Drive(s): 2
Volume Name: Volume_1
Volume Type: RAID 1
Sync Time Remaining: Completed
Total Hard Drive Capacity: 981858 MB
Used Space: 485151 MB
Unused Space: 496707 MB
But if run Scandisk it displays:
SCAN DISK RESULT :
Volume Name Scan Disk Result
Volume_1 FAILED
With a button to RESTART the drive.
I have Fun_plug installed, is there a better disk check I can run from telnet?
Offline
Have you tried fonz' fsck? I periodically check my drives using that and it works great for me.
http://www.inreto.de/dns323/fsck/
Offline
Anyone else have problems with the fan controller steps? Most notably nothing exists under /sys/class/i2c-apater
WARNING: The fsck image does not include a fan controller!
You can set fan speed manually, e.g.:
echo 150 >/sys/class/i2c-adapter/i2c-0/0-003e/pwm1
and read current speed with:
cat /sys/class/i2c-adapter/i2c-0/0-003e/fan1_input
(100 in pwm1 = 3150 rpm, 150 in pwm1 = 4650 rpm)
You can read the current temperature with:
cat /sys/class/i2c-adapter/i2c-0/0-0048/temp1_input
# echo 150 >/sys/class/i2c-adapter/i2c-0/0-003e/pwm1
-sh: cannot create /sys/class/i2c-adapter/i2c-0/0-003e/pwm1: nonexistent directory
# cat /sys/class/i2c-adapter/i2c-0/0-003e/fan1_input
cat: can't open '/sys/class/i2c-adapter/i2c-0/0-003e/fan1_input': No such file or directory
# cat /sys/class/i2c-adapter/i2c-0/0-0048/temp1_input
cat: can't open '/sys/class/i2c-adapter/i2c-0/0-0048/temp1_input': No such file or directory
Last edited by cnk (2010-09-02 05:54:40)
Offline
I tried the Fonz FSCK but it got an error about a missing library. I have not had time to figure out what/how to fix it.
Offline
If you'd post the output of ldd, it would tell you which library is missing:
/ # which fsck /ffp/sbin/fsck / # ldd /ffp/sbin/fsck ldd: can't open cache '/ffp/etc/ld.so.cache' libblkid.so.1 => /ffp/lib/libblkid.so.1 (0x4000e000) libuuid.so.1 => /ffp/lib/libuuid.so.1 (0x4001e000) libc.so.0 => /ffp/lib/libc.so.0 (0x4002a000) ld-uClibc.so.0 => /ffp/lib/ld-uClibc.so.0 (0x40000000)
Offline
Thanks for the ideas. I was using ffp 0.4, I upgraded to 0.5 and following the FSCK how-to, and after I figured out the command to restore my RAID1 array, I got this:
dlink_NAS login: root root@dlink_NAS:~# mdadm -A /dev/md0 /dev/sda2 /dev/sdb2 mdadm: /dev/md0 has been started with 2 drives. root@dlink_NAS:~# e2fsck /dev/md0 e2fsck 1.41.0 (10-Jul-2008) Segmentation fault
So, now what do I do? I suppose that might explain why the DNS-built in drive scan fails....
Offline
I found another post with the same problem but for the underlying device. In their case running the command a second time worked....
On a hunch I re-ran the command: e2fsck /dev/md0
And it worked!
Of course, it did not take it long to print "/dev/md0 contains a file system with errors, check forced." and its off doing its thing....
Offline
It fixed a lot of cross-linked files. Now it says the system is OK. But the Dlink drive test still fails.
Offline