Print

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

[dcmwai]

Just to update some test result...

Format the RAID in other linux can't seem to be see or display on the system.
Even I've copy over the HD_a4/b4 completely...

Hum... damn hard

[craftsman]

So, in getting telnet access there seems to be two different ways.  The first I followed and worked.  That is installing the full .5 version of Fonz Fun Plug (FFP).  The problem with that one was I couldn't unmount the drives.   The other methoed I've seen mentioned on here, are the instructions listed on http://wiki.dns323.info/howto:telnet.    This seems to be a much more minimalist version which has you download utelnetd, busybox3 and a version of starttelnet.sh.   However, I cannot get that version to run with the updated starttelnet.sh which places the files into a ram drive.  When I do that, and telnet I get something like "c0  s3, ..." on the telnet screen and then it disconnects.  Any ideas what might be wrong there? And can someone tell me if once I get this working, there is a way to add parted to the minimal install or a way to get the full FFP in a ram disk?

[TimeZlicer]

sorry guys (previously, i was replying from memory),
i forgot that the sh module of  busybox3 had some problem running on DNS-343
(i don't know how to fix it)

i am using /sbin/sh from the firmware
please modify your starttelnet.sh

Code: [Select]

<the path you copied to>utelnetd -l /bin/sh -d

you will not get a prompt unless you type 5784468
read the following for details

Code: [Select]

http://wiki.dns323.info/howto:ffp#the_root_user

[dcmwai]

Ok That make telnet running from RAM Disk.

But still the fdisk don't run...

I'm using the fdisk from this thread
http://forum.dsmg600.info/viewtopic.php?id=3375

# ./fdisk -l /dev/sda
./fdisk: No such file or directory

It seem that we have to use the original fdisk

It support some input and that might be what the vendor have modified it (mostly the cause of the segment fault as well)

something like

sh -c fdisk /dev/sdc n 4 83 1024 w
Create a new partation "4"
Type 83
Size 1024
I don't know what it meant for the w
Maybe for "write"

To remove a patation
sh -c fdisk /dev/sda d -1 w
I think this will be for delete all (-1)

But things is I donno how they
calculate the size....

[TimeZlicer]

did you try chmod? maybe there is no execute permission when you unpack your fdisk...

Code: [Select]

chmod +x fdisk
it should work, i am using if,
filesize and cksum as follows

Code: [Select]

root@DNS-343:~# ls -l fdisk
-rwxr-xr-x    1 root     root       181440 Mar  1 02:28 fdisk
root@DNS-343:~# cksum fdisk
4117949009 181440 fdisk

sda is the new WDC EARS
sdb is the old WDC EADS

note: i am not using raid, just using rsync to mirror the disks,
because i want sdb to be asleep most of the time unless i need to restore data or accidental deletion

Code: [Select]

root@DNS-343:~# ./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     1060287      530112   82  Linux swap / Solaris
Partition 1 does not end on cylinder boundary.
/dev/sda2         3164800  3907029167  1951932184   83  Linux
Partition 2 does not end on cylinder boundary.
/dev/sda4         1060288     3164799     1052256   83  Linux
Partition 4 does not end on cylinder boundary.

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              63     1060289      530113+  82  Linux swap / Solaris
/dev/sdb2         3164805  3907024064  1951929630   83  Linux
/dev/sdb4         1060290     3164804     1052257+  83  Linux

Partition table entries are not in disk order


[dcmwai]

That was the really strange part. Size is correct but I don't have the cksum things...

Code: [Select]

# ls -al fdisk
-rwxr-xr-x    1 root     root       181440 Mar 10 08:35 fdisk
#
# ./fdisk -ul
./fdisk: No such file or directory

something really wrong...

[TimeZlicer]

sharks, i just realized,
the fdisk that guy compiled needs some libs from ffp
and i have already installed ffp, hence i am not getting the error you got

Code: [Select]

root@DNS-343:~# ldd fdisk
        libc.so.0 => /ffp/lib/libc.so.0 (0x4000e000)
        ld-uClibc.so.0 => /ffp/lib/ld-uClibc.so.0 (0x40000000)

i have uploaded the libs here,
http://forum.dsmg600.info/viewtopic.php?pid=35163#p35163

there should be enough space to put these 2 libs in /

Code: [Select]

drwxr-xr-x admin/500         0 2010-03-10 16:14:29 /ffp/
drwxr-xr-x admin/500         0 2010-03-10 16:14:40 /ffp/lib/
-rwxr-xr-x admin/500     21168 2010-03-10 16:14:09 /ffp/lib/ld-uClibc.so.0
-rw-r--r-- admin/500    322696 2010-03-10 16:14:09 /ffp/lib/libc.so.0


That was the really strange part. Size is correct but I don't have the cksum things...

Code: [Select]

# ls -al fdisk
-rwxr-xr-x    1 root     root       181440 Mar 10 08:35 fdisk
#
# ./fdisk -ul
./fdisk: No such file or directory

something really wrong...

[dcmwai]

I've been successfully doing the fdisk things

But the raid is the problem..
I try startraid and it automatically format the new /dev/md0

But when I reboot the system...
I cannot see any volume any more...

I really have no idea what do to next...
Other then waiting for new firmware (if any)...

[TimeZlicer]

could you post the commands and responds which you tried...

I've been successfully doing the fdisk things

But the raid is the problem..
I try startraid and it automatically format the new /dev/md0

But when I reboot the system...
I cannot see any volume any more...

I really have no idea what do to next...
Other then waiting for new firmware (if any)...

[dcmwai]

I don't kept the log...
What I do is that I create 3 partation.
P 1 -> 512MB (Swap)
P 2 -> 1395G (Raid1)
P 4 -> 1G

And do the same for the 2nd drive.

mkswap /dev/sda1
mkswap /dev/sdb1

mke2fs -j /dev/sda4 (Fail as it say the partation was being use)
mke2fs -j /dev/sdb4

However I've kill most of the application on the device like FTP, UPNP and the iTunes server 

raidstart and it will start to format the /dev/md0 --> (dev/sda2 + dev/sdb2) and etc
It is quite a long process.

I try smbstart to see if I can read the volume without reboot but unfortunatelly no.
So I reboot and it is over....

[TimeZlicer]

if you format partition 4 you will lose the config files,
you will need to backup the config files somewhere
and copy them back (which will make the process much more tedious)

my original suggestion was to only recreate partition 1 and 2 and leave 4 alone
since partition 2 is the most (and probable the only 1 used, it should be sufficient

mke2fs -j /dev/sda4 (Fail as it say the partation was being use)
mke2fs -j /dev/sdb4

[dcmwai]

hum...

Never think of that...
I just thinking that because of Partation 4 is also affected and thus need to re-creat as well...

Maybe that was the issue...hum...
TimeZlicer do you have any idea on the size of partation 1 and partation 4?

because when I try to recreate it on another linux system and put in back the HDD it said that it is a new HDD (Partation 4 is populated with the old configuration...) any idea?

Thank You

[TimeZlicer]

partition 1(type:82 linux swap) is about 512MB
partition 4(type 83:linux) is about 1GB

i don't think D-Link firmware checks the size,
it just check the existence based on the admin data in partition 4

here's a command sequence on how to resize partition 1 and 2 while leaving 4 alone

Code: [Select]

fdisk -u /dev/sdb

The number of cylinders for this disk is set to 243201.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p

Disk /dev/sdb: 2000.4 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              63     1060289      530113+  82  Linux swap / Solaris
/dev/sdb2         3164805  3907024064  1951929630   83  Linux
/dev/sdb4         1060290     3164804     1052257+  83  Linux

Partition table entries are not in disk order

Command (m for help): d
Partition number (1-4): 1

Command (m for help): n
Command action
   e   extended
   p   primary partition (1-4)
p
Partition number (1-4): 1
First sector (63-3907029167, default 63): 64
Last sector, +sectors or +size{K,M,G} (64-1060289, default 1060289):
Using default value 1060289

Command (m for help): d
Partition number (1-4): 2

Command (m for help): n
Command action
   e   extended
   p   primary partition (1-4)
p
Partition number (1-4): 2
First sector (63-3907029167, default 63): 3164808
Last sector, +sectors or +size{K,M,G} (3164808-3907029167, default 3907029167):
Using default value 3907029167

Command (m for help): t
Partition number (1-4): 1
Hex code (type L to list codes): 82
Changed system type of partition 1 to 82 (Linux swap / Solaris)

Command (m for help): p

Disk /dev/sdb: 2000.4 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         3164808  3907029167  1951932180   83  Linux
/dev/sdb4         1060290     3164804     1052257+  83  Linux

Partition table entries are not in disk order

Command (m for help): w


[dcmwai]

Strange...
My fdisk can only start with 63 and not configurable...

I found that..
My single enter in putty will make it two...

Something wrong?

Code: [Select]

# ./fdisk -u /dev/sda

The number of cylinders for this disk is set to 182401.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): Command (m for help): p

Disk /dev/sda: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders, total 2930277168 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x5c25e06f

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1              63     1060289      530113+  82  Linux swap / Solaris
/dev/sda2         3164805  2930272064  1463553630   83  Linux
/dev/sda4         1060290     3164804     1052257+  83  Linux

Partition table entries are not in disk order

Command (m for help): Command (m for help): d

Partition number (1-4): 1

Command (m for help): Command (m for help): d

Partition number (1-4): 2

Command (m for help): Command (m for help): p


Disk /dev/sda: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders, total 2930277168 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x5c25e06f

   Device Boot      Start         End      Blocks   Id  System
/dev/sda4         1060290     3164804     1052257+  83  Linux

Command (m for help): Command (m for help): p

Disk /dev/sda: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders, total 2930277168 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x5c25e06f

   Device Boot      Start         End      Blocks   Id  System
/dev/sda4         1060290     3164804     1052257+  83  Linux

Command (m for help): Command (m for help): n

Command action
   e   extended
   p   primary partition (1-4)

Command action
   e   extended
   p   primary partition (1-4)

p

Partition number (1-4): Value out of range.
Partition number (1-4): 1

First sector (63-2930277167, default 63): Using default value 63
Last sector, +sectors or +size{K,M,G} (63-1060289, default 1060289):

Using default value 1060289



[TimeZlicer]

tip#1: don't just press enter, you can type 64 yourself
you don't have to use the default which is not aligned
see the transcript in my previous post, the default is 63 and i punch in 64 when i create partition 1

Code: [Select]

First sector (63-2930277167, default 63): Using default value 63