Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Tom]

Hardware Version: Unknown
Firmware Version: 1.08 beta
Software Version (Easy Search): N/A

Harddrive 1: WD10EADS-00L5B1
Harddrive 2: WD10EADS-00L5B1

Problem Type:

□ Error message  X Function does not work  □ Enhancement  □ UI Wording  □ Other:___________

Problem Description: The Web Gui only shows one disk although I have two in RAID 1.



But this is what dmesg tells me:

SCSI device sda: 1953525168 512-byte hdwr sectors (1000205 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 1953525168 512-byte hdwr sectors (1000205 MB)
SCSI device sda: drive cache: write back
 sda: sda1 sda2 sda4
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sdb: 1953525168 512-byte hdwr sectors (1000205 MB)
SCSI device sdb: drive cache: write back
SCSI device sdb: 1953525168 512-byte hdwr sectors (1000205 MB)
SCSI device sdb: 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 warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on sda4, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on sdb4, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on sda2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on sdb2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
md: md0 stopped.
md: md1 stopped.
md: md0 stopped.
md: bind<sdb2>
md: bind<sda2>

[whiteatom]

I have the same problem.. except I noticed that it worked perfectly for a few hours.. Then I started backing up to it and about 10 mins in - the drive light goes pink and the drive disappears the same way you have described. It's always bay 1 (right). I have swapped drives and reformatted many times.

Was using 1.07 - just installing 1.08 now and I'll give it a try again.

whiteatom

[ECF]

If you reboot the DNS-323 from the web UI does it report 2 drives when you log back into it?