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

Unfortunately no one can be told what fun_plug is - you have to see it for yourself.

You are not logged in.

Announcement

#1 2011-02-04 23:49:52

Kermit2064
New member
Registered: 2011-02-04
Posts: 3

How to partition 2TB HDs with fun_plug, running out of a ramdisk

Hello,

maybe a linux / fun_plug expert can help me out of the following problem:

I have a DNS-323 updated to FW 1.08 and two 2TB HDs WD20EARS, which I want to use in RAID1 mode with 4k aligned partition sizes.

For nearly one week I am now trying various ways to get access to my WD20EARS HDs via fun_plug and "fdisk" or "parted" -> in vain!
It is no problem, to get fun_plug 0.5 installed on HD, telnet to the DNS-323 and start fdisk, but to repartition the two drives and setup RAID1 new, I need a fun_plug with a working fdisk running off a ramdisk or off an usb-stick.

I downloaded therefore the tiny busybox fun_plug version including the new 4k sector fdisk from http://dns323.kood.org/_media/howto:utelnetd-ram.tar.gz
I also modified the included starttelnet.sh script according the explanations on http://dns323.kood.org/howto:telnet to fully run everything out off the ramdisk. With this installation I can telnet to the DNS-323 succesfully, but fdisk, even with the trick "cat | fdisk /dev/sda", doesn't work and a segmentation fault occurs every time it is called.
Calling fdisk with option -ul also doesn't work and the following message is printed:

fdisk -ul
*** Starting fdisk...
fdisk -ul

Unable to open -ul
exit status 1

I therefore downloaded parted from http://www.inreto.de/dns323/fun-plug/0. … .8.8-1.tgz and installed it together with the other files in the ffp-folder of the root.
But I can not start parted in the ffp/bin folder, even if I set all execution rights with:

chown root parted
chmod 777 parted

I also copied parted to /tmp, where fdisk also lies, but neither fdisk, nor parted can be started from that location. Linux always says: "no such file or directory", even if I try to start them via ./parted or ./fdisk.

How can I manage to start "parted" and what fdisk is running on my system, when calling fdisk directly in the /tmp-folder doesn't work?
I hope a Linux expert can help me here to get any of the two programs running (preferably fdisk), so I can realign my HD partitions.

The other way, installing fun_plug V0.5 on a usb-stick, fails during boot.
The boot script doesn't find the stick at /dev/sdc1, where it is mounted during installation. It seems the usb device moves during startup phase.
First it is detected at /dev/sdb1 and after the boot process it has moved to /dev/sdc1 and so uncompressing of the fun_plug fails (ffp.log output).
I tried thousands of modifications of the start.sh script, but nothing succeeded. Here my experience in Linux is too weak.

Please give me your much valued advice, how I get any fdisk running!

Thanks a lot in advance

fipsi2064

Offline

 

#2 2011-02-05 12:48:58

Mijzelf
Member / Developer
Registered: 2008-07-05
Posts: 709

Re: How to partition 2TB HDs with fun_plug, running out of a ramdisk

The other way, installing fun_plug V0.5 on a usb-stick, fails during boot.
The boot script doesn't find the stick at /dev/sdc1, where it is mounted during installation. It seems the usb device moves during startup phase.
First it is detected at /dev/sdb1 and after the boot process it has moved to /dev/sdc1 and so uncompressing of the fun_plug fails (ffp.log output).

Can you post your mount script and the ffp.log?

Offline

 

#3 2011-02-06 01:50:37

Kermit2064
New member
Registered: 2011-02-04
Posts: 3

Re: How to partition 2TB HDs with fun_plug, running out of a ramdisk

Hi Mijzelf,

thanks a lot for your quick response.

Meanwhile I managed to install Fonz's latest fun_plug V0.5 on an USB-Stick.
I did it according to the great tutorial found at http://wolf-u.li/1318/fun_plug-05-auf-d … betrieben/
It is a German site, but I think the Linux steps should also be clear for English speaking guys ;-)

This system boots from USB via an USB kernel module driver and a script, located in a system folder ".bootstrap", located at /mnt/HD_a4 (root of NAS).
And exactly this is, what actually seems to cause problems establishing the new RAID1 on my system.
After setting up the new RAID1 via:

mdadm --create /dev/md0 --level=1 --raid-devices=2 --spare-devices=0 /dev/sd
[ab]2

The right LED begins flashing orange. What does this mean? I thought only HW-failures are indicated by orange flashing LED?
Resyncing of the RAID1 needs 360 min. to finish. I hope after finishing the resync and doing a reboot afterwards, everything will work fine and the LED goes back to blue.
In another forum, I read one has to do a "reset to default" before establishing the new RAID respectively writing the partition table to /dev/sda.
But I don't now how to do such a "reset to default".

Maybe someone can give me an advice here, how to stop all processes / tasks on /dev/sda
I have posted the whole output of my trial to realign the partition sizes and establishing the new RAID1 with ext3 filesystem.
I hope a specialist can detect any mistake in my process.

I would appreciate any advice.

Thanks a lot so far!

Greetings

kermit2064


Attachments:
Attachment Icon dump.txt, Size: 23,061 bytes, Downloads: 371

Offline

 

#4 2011-02-06 10:55:23

FunFiler
Member
Registered: 2010-05-23
Posts: 577

Re: How to partition 2TB HDs with fun_plug, running out of a ramdisk

I've seen the orange LED caused by running out of space in root (/) and/or /tmp.


3 * (DNS-323 with 2 * 2TB) = 12TB Running FW v1.08 & FFP v0.5
Useful Links: Transmission, Transmission Remote, Automatic

Offline

 

#5 2011-02-06 11:45:31

Kermit2064
New member
Registered: 2011-02-04
Posts: 3

Re: How to partition 2TB HDs with fun_plug, running out of a ramdisk

First Resyncing finished meanwhile, but a raidstop / raidstart test failed afterwards. It seems there was no RAID on /dev/md0 built successfully.
But there were no error messages printed during the build up!

After a "Reset to default" via the Web-Interface and a reboot of the DNS-323, the right orange LED turned off again and both LEDs started blinking blue during the whole boot process. At the end of the boot however, the left LED is now orange !?

When entering the Web-Interface the DNS-323 wants to build up any HD configuration. It doesn't recognize / accept the partitions.
When pressing skip and entering the Status page a RAID with 2TB is displayed. Also both HDs are shown with their correct size.

Establishing once again the .bootstrap folder and booting off from USB-Stick shows, that the partition table is still correct for both sda and sdb.
But there is no RAID1 running on /dev/md0, nor can it be started with "raidstart md0".

I did the RAID-setup once again from the point of

mdadm --create /dev/md0 --level=1 --raid-devices=2 --spare-devices=0 /dev/sd[ab]2

as dumped in me file, once again, but now with left LED orange.
I hope after the second resyncing and doing a reboot all will be fine (but I don't think so).

Please give me an advice, what's going wrong with my system.
Why do I have error messages after doing a hd_verify:

/ # hd_verify
hd verify v1.23.10072009
******* hd_verify start *********
Mount Hidden Partition
grep: /etc/codepage: No such file or directory
Find raid table from hard disk
Mount normal
grep: /etc/codepage: No such file or directory
grep: /tmp/onedisk: No such file or directory
Build Shared Name Table version v1.05
grep: /tmp/onedisk: No such file or directory
mount: wrong fs type, bad option, bad superblock on /dev/sdb2,
       missing codepage or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

mount: wrong fs type, bad option, bad superblock on /dev/sdb2,
       missing codepage or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

mount: wrong fs type, bad option, bad superblock on /dev/sdb2,
       missing codepage or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

mount: wrong fs type, bad option, bad superblock on /dev/sdb2,
       missing codepage or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

grep: /tmp/onedisk: No such file or directory
RAID1 mode
RAID mount normal
hd_mgaic_num1 = 882338
mount device /dev/sdb2 fail
hd_mgaic_num2 = 0
error disk = 0 0
mdadm: stopped /dev/md0
mdadm: stopped /dev/md1
Refresh Shared Name Table version v1.04
.
.
.
Refresh Shared Name Table version v1.04
*************** hd_verify end ******************

How can I get rid of them?

Thanks a lot so far!

Offline

 

#6 2011-02-07 10:41:14

Mijzelf
Member / Developer
Registered: 2008-07-05
Posts: 709

Re: How to partition 2TB HDs with fun_plug, running out of a ramdisk

It seems those WD disks are not suitable for RAID purposes. Link.

/Edit:
These disks are known not to work in Raid1 on ZyXEL NASses. Link.

Last edited by Mijzelf (2011-02-07 13:46:55)

Offline

 

Board footer

Powered by PunBB
© Copyright 2002–2010 PunBB