Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Dear Fonz fun_plug experts:
I hope you can help with the following problem:
I bought my DNS-323 4 (or 5) years ago. I am not a big computing expert, but I've succeeded formatting two hard disks, installing the Fonz fun_plug, and accessing Volume_1 and Volume_2 from my networked PC.
The following problem showed up a couple of months ago, and I have no clue how to fix it: there was an accidental electricity shutdown. The Dlink-323 system got turned off unexpectedly. When turning it on again, the left amber light on the front stays on, and I can't access (or, on my PC, using Windows Explorer), I can't see Volume_2. Volume_2 contains important data.
I can log in to the Dlink-323 as usual but the opening web page asks me to format Volume_2. (Which I refrain from, of course).
I can also telnet to the unit.
I think I've seen somewhere, that such a problem can be solved by telnetting into the unit, and issuing some system commands?
What are the commands for:
1. Listing the available hdds
2. Investigating the health of the hdds
3. Mounting/unmounting the hdds
Any other ideas on the situation?
Many thanks in advance
Gail
Update 4-12 13: here is the df -h output:
/ # df -h
Filesystem Size Used Avail Use% Mounted on
%root% 9.7M 6.5M 2.8M 70% /
/dev/ram0 9.7M 6.5M 2.8M 70% /
/image.cfs 4.5M 4.5M 0 100% /sys/crfs
/dev/sda2 1.8T 235G 1.6T 13% /mnt/HD_a2
/dev/sda4 487M 13M 475M 3% /mnt/HD_a4
/dev/sdb4 487M 11M 476M 3% /mnt/HD_b4
/ #
Interestingly, fdisk does see two hdd's:
/ # fdisk -l
Disk /dev/sda: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 66 530113+ 82 Linux swap
/dev/sda2 131 243201 1952467807+ 83 Linux
/dev/sda4 67 130 514080 83 Linux
Disk /dev/sdb: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 1 66 530113+ 82 Linux swap
/dev/sdb2 131 243201 1952467807+ 83 Linux
/dev/sdb4 67 130 514080 83 Linux
/ #
*** -> Update 2: here is (a filtered) output of dmesg, as related to mounting the disks. It seems that on boot, there is an IO error when it's trying to mount /dev/sdb2:
SCSI device sda: 3907029168 512-byte hdwr sectors (2000399 MB) drive cache: write back
sda: sda1 sda2 sda4
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sdb: 3907029168 512-byte hdwr sectors (2000399 MB) drive cache: write back
sdb: sdb1 sdb2 sdb4
Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0
Adding 530104k swap on /dev/sda1. Priority:-1 extents:1
Adding 530104k swap on /dev/sdb1. Priority:-2 extents:1
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda4, internal journal
EXT3-fs: recovery complete. mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds
EXT3 FS on sdb4, internal journal
EXT3-fs: recovery complete. mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds
EXT3 FS on sda2, internal journal
EXT3-fs: recovery complete. mounted filesystem with ordered data mode.
SCSI error : <1 0 0 0> return code = 0x8000002
sdb: Current: sense key=0x3 ASC=0x0 ASCQ=0x0 Info fld=0x747bee12
end_request: I/O error, dev sdb, sector 1954278930 JBD: IO error reading journal superblock
EXT3-fs: error loading journal.
EXT2-fs: sdb2: couldn't mount because of unsupported optional features (4).
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda4, internal journal. mounted filesystem with ordered data mode.
EXT3 FS on sdb4, internal journal. mounted filesystem with ordered data mode.
It seems that the system gets an IO error trying to mount /dev/sdb2. All other mounts have succeeded.
Last edited by GailH (2013-04-12 19:32:24)
Offline
i also had the same problem from 2 days ago
and when i connect to the webpage it thinks that its a new drive and asks to format it
Offline
That I/O error is bad. In most cases it's a hardware error. I don't see how a power failure could cause that, but of course it is possible that the defect was already there, to show up on a reboot.
I think you should lowlevel copy (dd conv=noerror,sync or dd_rescue) the disk to an new one, and plug that in, and hope it just mounts, or can be repaired using chkfs.
Offline
Power failures often aren't simple off/on events. Brown-outs, power spikes and lot of other nasty things often occur at the same time. Power bars don't protect against 99% of the issues. Many UPSs don't either, it depends on what they are designed to do. A proper BPS (UPS where devices are always on conditioned power output) is the best solution, next time.
Offline