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

It would be interesting to know what changes were made in the disk error detect and format routines.

I upgraded with a "mismatched" RAID1 pair - a Seagate & a Maxtor, both 7200 rpm 250GB drives - and after looking through the changes in the web admin, shut it down and replaced the Maxtor with a Seagate, something that I had been planning to do so as to get matched pairs, not only in the DNS-323, but in an IBM xSeries server as well.

The first thing I noticed is the box did not give me any error indications - no pink LED and no email - which is what it had done in a similar situation with fw 1.04 - I logged into the web admin page and was greeted with the expected offer to format the drive, but this time, there is a check box in the corner that apparently will let you configure it as a RAID pair - so it looks like you can now start with a single disk and then upgrade to a RAID pair.

I allowed the unit to format and ....

Well - I don't know where to start - first it appears to have formatted the wrong drive - and second it appears to be really confused (or maybe I am).

The status page shows that I have a degraded RAID1 array - and it does not mention anything about how long it will to resync, there appears to be no resync activity, and attempt to access the drives now shows TWO separate drives, one of which is accessible and the other is not - AND the one which is accessible contains data from "a previous life" in the DNS-323 (which is why I said earlier it appears to have formatted the wrong drive.

Needless to say I am quite disappointed - and I will be duplicating this post on the DLink forum.

It might be a better idea to put a format menu which will allow a user to choose which drive is to be formatted - if there is more than one drive and which drive should be rebuilt if replacing a drive in a RAID1 pair.

I'll probably spend a few days playing with it before I recreate my RAID array and put it back into service, but, this could get really tiring if I had to do it with every firmware upgrade.

Jeff

That was actually on my to-do list for later today - if the thing ever completes formatting my 250 GB disks - it gave me format failure messages when trying to format in RAID1 and now appears to be stuck at 94% formatting as standard volumes.

It was my intention not to swap disks between DNS-323s but to swap two different RAID pairs a 250GB and an 80GB.

A hang at 94% on the new drive was the first step in my failure. I messed with some stuff; re-cleared the new drive (wrote zeros to it to clear all MBR, etc) and tried again... second time around wrong disk got formatted... although everything went through - didn't stick at 94%; go figure.

I thought I was golden when the "right" drive tried to format the first time; too bad it hung up...

-Jeff

I just installed the new firmware and was happy to read that it had an option to reconfigure the RAID configuration (by inserting a new HD) to RAID1 without having to format the first (with data) harddrive. Since i started using the NAS with 1 750gb HD and after a couple weeks inserted a second 750GB HD I had 2 separate drives. I know want to make a RAID1 configuration. (haven't been using the second drive). Although when i go to the RAID option and click on RAID1 it still says : Warning re-formating drive(s). And don't dare to click it
Does anybody know how to deal with my situation? It says after inserting a new drive, although i have inserted the 'new' drive a while ago (and formated as blank disc) however it's still blank and haven't been using it.

any suggestions? (besides backing up all data from the first drive... it has 300GB on it and i don't have the storage space)

regards,
Philippe

Ok... i need to 'hold my horses' or something... it ended up formating my drive (with data) ... altough i was very sure it didn't say All Data Will be lost... in fact.. it said data on the existing drive will not be erased... so far for that then. I ended up with 2 empty drives well luckely I didn't had any important data on besides some music and picture backups and well yeah.. movies... but i guess that's not the most important! anyway I'm not sure what i did wrong but, it should have been more clear in their alert messages.

ps the drive with the data was the one on the right, the empty/new one was on the left, (the right is mounted as HD_a2)

better backup data before setting a raid1 (if you can at least!)

So anyways I went ahead and tested both ways. I start with 1 Disk on the left hand side formated as standard. Copied over about 4Gb of data, Powered down and inserted a 2nd disk. Once powered up I clicked reconfigure as Raid 1. The correct(right hand side) drive was formated and the data began syncing.

Next, I removed the left hand side drive, formated the right hand side as a standard disk, Removed the raid1 partitions from the 1st hard drive(left hand side). Once the DNS-323 finished formatting the right drive bay as standard I copied over another 4Gb of data, powered down, inserted a drive into the left bay and powered back on. Again I clicked reconfigure as Raid1. The left bay was formatted and the drives are now syncing with about 180min left and I have access to all data on the drive as well as I can see both drive links blinking showing they are syncing.

Something to note though is that the drive being inserted as a "new" drive does have all of its partitions removed and in essence is a new disk. My next tests will be to insert a Fat32/NTFS formatted drive as well as an EXT3 (ubuntu) formatted drive and see if I can get the same results.

Last edited by Dlink (2008-05-15 23:49:12)

skydreamer wrote:

fdisk is finally working :-)
I wonder what is the purpose of the fourth disk partition /dev/sda(b)4? Was this inherited from the old firmware i.e. when you format the disks under the new firmware v1.05 you get only two partitions?

DLINK 1

/ # fdisk -l

Disk /dev/sda: 750.1 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 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       91118   730861110  83 Linux
/dev/sda4              67         130      514080  83 Linux

Partition table entries are not in disk order

Disk /dev/sdb: 750.1 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 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       91118   730861110  83 Linux
/dev/sdb4              67         130      514080  83 Linux

Partition table entries are not in disk order


DLINK 2

/ # fdisk -l

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 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      121404   974133405  83 Linux
/dev/sda4              67         130      514080  83 Linux

Partition table entries are not in disk order

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 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      121404   974133405  83 Linux
/dev/sdb4              67         130      514080  83 Linux

Partition table entries are not in disk order

mine was not formated after flashing to 1.05

/ # fdisk -l

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 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              67       60801   487853887+ 83 Linux

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 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              67       60801   487853887+ 83 Linux
/ # fdisk

richneo wrote:

/ # fdisk
BusyBox v1.10.1 (2008-04-19 12:53:41 CEST) multi-call binary
... #

I suspect you using fun_plug through which you have BusyBox v1.10.1 running.  The version shipped with 1.05 firmware is the old one:

~ # /bin/busybox
BusyBox v1.00-pre1 (2007.12.10-08:03+0000) multi-call binary

Usage: busybox [function] [arguments]...
   or: [function] [arguments]...

...

I wonder if there are different 1.05 firmware revisions floating around.

Jaya

richneo wrote:

hmm i am using fonz's fun plug 0.5

So that is where your fdisk is coming from.  DLINK have not got further than pre 1.00 build of BusyBox and I believe I know why.

Regards,

Jaya

skydreamer wrote:

fdisk is finally working :-)

Is this native Fdisk or fun_plug fdisk?  My built in fdisk still does not work with 1.05.  Still getting the segmentation fault.

Cheers!
bspvette

skydreamer wrote:

Uhmmm, it is the busy box one that works, /usr/bin/fdisk still reports seg_fault as you have correctly noticed.

I could not get even the busybox fdisk working with the release 1.04 so I suppose it is a small progress....

-SD

Gotcha.  I have been using a link to the busybox3 used for telnet with no problems.

Cheers!
bspvette

Are you using the new version of EasySearch?