Print

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

[jeffers.r]

Pavlo,

It seems the files included within utelnetd-ram.tar.gz have some lines commented out that shouldn't be. Have a look here for the correct details on getting telnet working:

http://wiki.dns323.info/howto:telnet

[pavlo]

Hello everyone and thanks for help,


Actually I've resolved the trouble by just connecting second (temporary) 80GB HDD together with those 2TB WD.

This scenario is more simple to be done as does not require using of RAM DRIVE.

I would lovely try other cases to give something back for community but I am afraid to make my HDD inaccessible while having important data there.

[slalonde]

Hello everyone,

I don't know if any of you is still watching this thread, but I had a question for any of you that was able to repartition/reformat the drives for the 4K alignement issue.

First of all, thanks a lot to dcmwai for his step by step procedure and also to maxbis who was kind enough to post corrections to dcmwai's guide. I followed these steps, had a bit of problems at the begining, but in the end, I managed to partition and format my disks properly (well I think). After synching completed, I ran some last checks (as suggested by dcmwai), I was able to start/stop the raid array properly and I rebooted the device.

The smb share is up, I can read/write stuff on it. However, when I start dlink's web page, it asks me to configure my drivers (raid type, format, etc...). If I click skip, most of the settings are available, under Tools -> Raid, it says:

Current RAID Type :
   Volume_1 : RAID 1 (Degraded)
 

And I have a button "Set RAID Type and Re-Format"

Under Tools -> Disk Tools, I can't use the Scan Disk feature.

Anyone experienced the same thing? Any suggestion? Could it be related to the fact that the guid of my raid changed (i.e., could linksys's software refer to that guid?)

Thanks,
Sebastien

[derek_c_lee]

Have you seen this thread?  http://forums.dlink.com/index.php?topic=14484.0
I believe I hit the same problem and it was due to

WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
The kernel still uses the old table.
The new table will be used at the next reboot.

Try:

Code: [Select]

swapoff /dev/sdb1
in step (6).

[redrome76]

please help !

I get stuck at the end...
when I type

#mdadm -Es > /mnt/HD_b4/.systemfile/mdadm.conf
response is
cannot create /mnt/HD_b4/.systemfile/mdadm.conf: No such file or directory

what I have to do ?

[redrome76]

I tried one more time to align in RAID1 but unsuccessful

just finished to sync and #cat /proc/mdstat give this:

Personalities : [linear] [raid0] [raid1]
md0 : active raid1 sdb2[1] sda2[2](F)
      1951171776 blocks [2/1] [_U]
        resync=DELAYED
unused devices: <none>

# mdadm --detail /dev/md0
/dev/md0:
        Version : 00.90.01
  Creation Time : Thu Nov 25 02:28:21 2010
     Raid Level : raid1
     Array Size : 1951171776 (1860.78 GiB 1998.00 GB)
    Device Size : 1951171776 (1860.78 GiB 1998.00 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Thu Nov 25 06:15:23 2010
          State : active, degraded
 Active Devices : 1
Working Devices : 1
 Failed Devices : 1
  Spare Devices : 0

           UUID : 93671b49:337d2c92:cdb3fb02:17f99cc2
         Events : 0.4

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

       2       8        2        -      faulty spare   /dev/sda2

# /tmp/fdisk -ul

Disk /dev/sda: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1              64     1060289      530113   82  Linux swap / Solaris
/dev/sda2         2088456  3904432206  1951171875+  83  Linux
/dev/sda4         1060290     2088449      514080   83  Linux

Partition table entries are not in disk order

Disk /dev/sdb: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1              64     1060289      530113   82  Linux swap / Solaris
/dev/sdb2         2088456  3904432206  1951171875+  83  Linux
/dev/sdb4         1060290     2088449      514080   83  Linux

Partition table entries are not in disk order

Please can someone give me help ?

[redrome76]

 

[dP21]

Does anyone know if fdisk should show the same (properly aligned information) after formatting and rebooting?  I just happened to check and it shows this now:

Code: [Select]



Command (m for help): p

Disk /dev/sdb: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xb6b1183f

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1          66      530112   82  Linux swap / Solaris
Partition 1 does not end on cylinder boundary.
/dev/sdb2             197      243202  1951932184   83  Linux
/dev/sdb4              66         197     1052256   83  Linux
Partition 4 does not end on cylinder boundary.

Partition table entries are not in disk order

Command (m for help):


[quest0126]

Hi,

If one of the hhd failed and requires rebuild of the raid after align of the sector, do we need to re-align again?? or just let it rebuild the raid will do?

[Bun-Bun]

Ok... following this thread and the guide... and ripping my hair out (don't worry I was already balding...) I have finally gotten this to mostly work.

EDIT: I am using a DNS-323 with two 2TB seagate drives.

However the first time the partition wasn't unmounted (sdb4 was sticking for some reason) and upon reboot I had individual volumes instead of raid... I just tried again making sure no partitions were mounted and now I got through everything without error except for one thing...

Code: [Select]

# mdadm -Es > /mnt/HD_b4/mdadm.conf
cannot create /mnt/HD_b4/mdadm.conf: No such file or directory

# mdadm -Es > /mnt/HD_a4/mdadm.conf
cannot create /mnt/HD_b4/mdadm.conf: No such file or directory

# mdadm -Es > /etc/mdadm.conf

# cat /mnt/HD_b4/mdadm.conf
cat: /mnt/HD_b4/mdadm.conf: No such file or directory

# cat /mnt/HD_a4/mdadm.conf
cat: /mnt/HD_b4/mdadm.conf: No such file or directory

# write_hdverify
write_hdverify: No such file or directory

# hd_verify -w
hd verify v1.23.10072009
Force write verify to hd
WriteMagicNumToMTD 486036
Can not mount md0


There is nothing in HD_[ab]4 (except an empty folder called backup) and the hd_verify -2 can not mount md0?

I just finished formatting and am waiting for the sync to complete so I can reboot and see if this worked...

EDIT: It finished and from the web interface it showed the raid 1 with sync completed but upon restarting the unit I had two separate volumes...

Just telneted back in and fdisk shows all the partitons are still correctly there and both volumes work fine... it just didn't stick with the raid...

EDIT2: Since the partitioning stuck I just tried recreating the raid 1 array. This time when I did hd_verify -w it was able to mount md0 and write something but then spat out

Code: [Select]

hd verify v1.23.10072009
Force write verify to hd
WriteMagicNumToMTD 328986
WriteMagicNumToHD 328986
cp: /mnt/HD_a4/.systemfile/hd_magic_num: No such file or directory
rm: cannot remove `/tmp/hd_verify_warning': No such file or directory

Also this time I had to umount md0 first before it would let me format... not sure why this time it was mounted and last time it wasn't... I followed all the same steps.

Waiting for it to finish syncing again...

I should also note the first time I did this when I created the raid array I had the right side giving an yellow degraded light. This time both lights are normal and blue.

[Bun-Bun]

sync completed successfully. raidstop and start did not trigger another sync. Restart DNS-323 and back to to separate volumes...

Help?

EDIT:

Ok went back in... after after going through each step I found that sda4 and sdb4 were unmounting when attempting to start md0 without a FS on it or when doing hd_verify. So I went back in, recreated the raid, formatted it, then did raidstart md0, checked mount and I had md0 as HD_a2 and sda4/sdb4 as HD_a4/HD_b4 and when I did mdadm -Es > /mnt/HD_[ab]4/mdadm.conf it worked as well as hd_verfiy -w didn't give the one error...

Waiting for sync again...

Sorry for the crampness of this post... posting quickly from my phone at work...