Hi
I installed Alt-F and tried using the wizard to setup my DNS323 but i
got a few errors so I went through and did it manually and setting up
time host etc went fine no prob but setting up disks has been a bit more
problematic.
They seem to be ok, this is what i am told on the status screen:
I think partitioning is in order, below is a screen shot for one disk (the other says practically the same)
When i go to the RAID section it doesn't let me setup RAID1 first time i tried i got:
Stopping all services and disks... done.
GPT partitioning disk sda.../dev/sda raid equal 5860531120 done.
GPT partitioning disk sdb.../dev/sdb raid equal 5860531120 done.
fdisk: device has more than 2^32 sectors, can't use all of them fdisk: device has more than 2^32 sectors, can't use all of themCreating and activating swap in disk sda... done.
Creating and activating swap in disk sdb... done.
Creating raid1... failed:
Then i tried formating the disks with ext4 then went back to the RAID section and tried again and got
mdadm: /dev/sda2 appears to contain an ext2fs file system
size=-1365226024K mtime=Tue Oct 30 20:48:32 2012
mdadm: /dev/sdb2 appears to contain an ext2fs file system
size=-1365226024K mtime=Tue Oct 30 20:49:46 2012
Sorry for my noobness but any help would really be appreciated!!
Cheers,
-Gaiko
it doesn't let me setup RAID1 first time i tried i got:
Stopping all services and disks... done.
GPT partitioning disk sda.../dev/sda raid equal 5860531120 done.
GPT partitioning disk sdb.../dev/sdb raid equal 5860531120 done.
fdisk: device has more than 2^32 sectors, can't use all of them fdisk: device has more than 2^32 sectors, can't use all of themCreating and activating swap in disk sda... done.
Creating and activating swap in disk sdb... done.
Creating raid1... failed:
Then i tried formating the disks with ext4 then went back to the RAID section and tried again and got
Anyway, from the Disk Partitioner screen shot your manual partitioning seems to be OK.-As the Disk Wizard that you run afterwards destroyed your manual partitioning, you have to re-partition again and then you should go to Disk->RAID, select RAID1 as the RAID type, select sda2 and sdb2 as the RAID components, and hit the Create button. Then, go to Disk->Filesystem, select the recently created RAID array, probably 'md0', create a filesystem on it and mount it. *But* you still have to create and activate swap *before* trying to create the filesystem!
The Disk Wizard does it all: partition, create and activate swap, create RAID, create filesystem, mount it.-Or you could try the fix posted.
On Wednesday 31 October 2012 21:26:57 Gaiko wrote:
> Hi Joao, Thanks for the response.
>
> On Tuesday, October 30, 2012 10:33:32 PM UTC+4, Joao Cardoso wrote:
> > On Tuesday, October 30, 2012 5:08:22 PM UTC, Gaiko wrote:
...
> Thanks, At the risk of being more annoying, I actually had read that post
> before but it wasn't clear to me how to apply the fix (I am assuming you
> are refering to the diskwiz_proc.cgi you posted on the 30th?)
Please use the group's top search entry-form and
search for 'As this is one of the most read topics' in Alt-F
You will find instructions there. Download all the 4 attached files, plus the updated diskwiz_proc.cgi posted in the "3TB debug topic".
Just a question: How did you partition the disks whose screen shoots you show in your first post? The partitioning is OK, did you used the command line? or the Disk Partitioner?
On Wednesday 31 October 2012 21:26:57 Gaiko wrote:
> Hi Joao, Thanks for the response.
>
> On Tuesday, October 30, 2012 10:33:32 PM UTC+4, Joao Cardoso wrote:
> > On Tuesday, October 30, 2012 5:08:22 PM UTC, Gaiko wrote:
...
> Thanks, At the risk of being more annoying, I actually had read that post
> before but it wasn't clear to me how to apply the fix (I am assuming you
> are refering to the diskwiz_proc.cgi you posted on the 30th?)
Please use the group's top search entry-form and
search for 'As this is one of the most read topics' in Alt-F
You will find instructions there. Download all the 4 attached files, plus the updated diskwiz_proc.cgi posted in the "3TB debug topic".
Just a question: How did you partition the disks whose screen shoots you show in your first post? The partitioning is OK, did you used the command line? or the Disk Partitioner?
This does not work.
Pleas release RC3 including the fixes soon.
Hi Joao
On Friday, November 9, 2012 4:57:33 AM UTC+4, Joao Cardoso wrote:On Thursday, November 8, 2012 4:56:29 PM UTC, Tom_1967 wrote:
> Hello Joao,
>
> I would be glad to test it. It cannot go worse as it already is.
I'm currently "out of town".
Funny, i just got back intown (hence my silence this past week)
Early next week I will start a new topic with instructions and files, as this subject is spread across several topics.
If you are in a hurry, you can search the several 3TB threads, as there are several partial succes reports.
Or perhaps someone can help you with the gory comand line details.
Well while i am not cmd line guru I think i can hold my own (used/installed slackware back in the 90s, thats gotta count for something).
to kind of follow up on both my last post and tom's post.
When i go to the disk/RAID page md0 is indeed an option and i select sda2/sdb2, see below:
https://dl.dropbox.com/u/507145/RAID1.jpg
but when i try to create i get an error:
https://dl.dropbox.com/u/507145/RAID2.jpg
not quite sure where to go there except the patches you posted which unfortunately lead me to my next question:
How to upload those files to my dns323?
I bit the bullet and putty'd (ssh) into my box just to make sure i could (all the necessary services seem to be running ftp, telnet, ssh) and was able to no prob. the problem comes when i tried to ftp in to put/mput the files on my dns323. It tells me it can't read the vsftpd.user_list (which is because it doesn't exist, i checked) and i don't think there are any other users setup by default other than root (but i can't ftp via root? [i know not exactly secure but in this case i am not worried]). Its been a loooong time since i have tried putting/getting anything via ftp so perhaps i am missing something? Any thoughts on this would be appreciated.
Cheers
Hi Joao
On Friday, November 9, 2012 4:57:33 AM UTC+4, Joao Cardoso wrote:On Thursday, November 8, 2012 4:56:29 PM UTC, Tom_1967 wrote:
> Hello Joao,
>
> I would be glad to test it. It cannot go worse as it already is.
I'm currently "out of town".
Funny, i just got back intown (hence my silence this past week)Early next week I will start a new topic with instructions and files, as this subject is spread across several topics.
If you are in a hurry, you can search the several 3TB threads, as there are several partial succes reports.
Or perhaps someone can help you with the gory comand line details.
Well while i am not cmd line guru I think i can hold my own (used/installed slackware back in the 90s, thats gotta count for something).
to kind of follow up on both my last post and tom's post.
When i go to the disk/RAID page md0 is indeed an option and i select sda2/sdb2, see below:
https://dl.dropbox.com/u/507145/RAID1.jpg
execute the following commands on the command line (copy/paste them) and post their output?
Can you please telnet/ssh the box and login as the 'root' user, same password as the webgui password,
blkid # show current filesystems
mdadm --examine /dev/sda2 # show sda2/sdb2 RAIDcomponent
status
mdadm --examine /dev/sdb2
mdadm --create --run --level=raid1 --metadata=0.9 --bitmap=internal --raid-devices=2 /dev/md0 /dev/sda2 /dev/sdb2 # create the RAID
echo $?
On Saturday, November 10, 2012 9:18:51 AM UTC, Gaiko wrote:Hi Joao
On Friday, November 9, 2012 4:57:33 AM UTC+4, Joao Cardoso wrote:On Thursday, November 8, 2012 4:56:29 PM UTC, Tom_1967 wrote:
> Hello Joao,
>
> I would be glad to test it. It cannot go worse as it already is.
I'm currently "out of town".
Funny, i just got back intown (hence my silence this past week)Early next week I will start a new topic with instructions and files, as this subject is spread across several topics.
If you are in a hurry, you can search the several 3TB threads, as there are several partial succes reports.
Or perhaps someone can help you with the gory comand line details.
Well while i am not cmd line guru I think i can hold my own (used/installed slackware back in the 90s, thats gotta count for something).
to kind of follow up on both my last post and tom's post.
When i go to the disk/RAID page md0 is indeed an option and i select sda2/sdb2, see below:
https://dl.dropbox.com/u/507145/RAID1.jpg
Everything seems OK. You have partitioned the disks using the Disk Partitioner, right?
execute the following commands on the command line (copy/paste them) and post their output?
Can you please telnet/ssh the box and login as the 'root' user, same password as the webgui password,
blkid # show current filesystems
mdadm --examine /dev/sda2 # show sda2/sdb2 RAIDcomponent
status
mdadm --examine /dev/sdb2
mdadm --create --run --level=raid1 --metadata=0.9 --bitmap=internal --raid-devices=2 /dev/md0 /dev/sda2 /dev/sdb2 # create the RAID
echo $?
When i go to the disk/RAID page md0 is indeed an option and i select sda2/sdb2, see below:
https://dl.dropbox.com/u/507145/RAID1.jpg
Everything seems OK. You have partitioned the disks using the Disk Partitioner, right?
yes
execute the following commands on the command line (copy/paste them) and post their output?
Can you please telnet/ssh the box and login as the 'root' user, same password as the webgui password,
Sure!
blkid # show current filesystems
mdadm --examine /dev/sda2 # show sda2/sdb2 RAIDcomponent
status
mdadm --examine /dev/sdb2
mdadm --create --run --level=raid1 --metadata=0.9 --bitmap=internal --raid-devices=2 /dev/md0 /dev/sda2 /dev/sdb2 # create the RAID
echo $?
# blkid
/dev/mtdblock0: TYPE="minix"
/dev/loop0: TYPE="squashfs"
/dev/mtdblock1: TYPE="minix"
/dev/sda1: TYPE="swap"
/dev/sdb1: TYPE="swap"
# mdadm --examine /dev/sda2
mdadm: No md superblock detected on /dev/sda2.
# mdadm --examine /dev/sdb2
mdadm: No md superblock detected on /dev/sdb2.
# mdadm --create --run --level=raid1 --metadata=0.9 --bitmap=internal --raid-dev
ices=2 /dev/md0 /dev/sda2 /dev/sdb2
# echo $?
1
#
mdadm --create
/dev/md0
--run --level=raid1 --metadata=0.9 --bitmap=internal --raid-devices=2 /dev/sda2 /dev/sdb2 # create the RAID
echo $?
If this works then an unnoticied/unreported bug exists in RC2.
If this does not works also, then I'm puzzled, as everything else looks fine.
Thanks
If this works then an unnoticied/unreported bug exists in RC2.
If this does not works also, then I'm puzzled, as everything else looks fine.
Thanks
mdadm --create
/dev/md0
--run --level=raid1 --metadata=0.9 --bitmap=internal --raid-devices=2 /dev/sda2 /dev/sdb2 # create the RAID
echo $?
# mdadm --create /dev/md0 --run --level=raid1 --metadata=0.9 --bitmap=internal --raid-devices=2 /dev/sda2 /dev/sdb2 # create the RAID
# echo $?
1
If this works then an unnoticied/unreported bug exists in RC2.
If this does not works also, then I'm puzzled, as everything else looks fine.
Hmmm, then i will hope it is a bug (not a common hope but better than an enigma) (though i am guessing an enigma as this is outputting the same "1" as before?)
mdadm --create /dev/md0 --run --level=raid1 --bitmap=internal --raid-devices=2 --verbose --verbose /dev/sda2 /dev/sdb2
echo $?
mdadm --create
/dev/md0
--run --level=raid1 --metadata=0.9 --bitmap=internal --raid-devices=2 /dev/sda2 /dev/sdb2 # create the RAID
echo $?
# mdadm --create /dev/md0 --run --level=raid1 --metadata=0.9 --bitmap=internal --raid-devices=2 /dev/sda2 /dev/sdb2 # create the RAID
# echo $?
1
If this works then an unnoticied/unreported bug exists in RC2.
If this does not works also, then I'm puzzled, as everything else looks fine.
Hmmm, then i will hope it is a bug (not a common hope but better than an enigma) (though i am guessing an enigma as this is outputting the same "1" as before?)It's an enigma :-OThe printed '1' means that the command failed. What is strange is that no error message appears, so we don't know what is wrong. Please tryBut the mdadm manual says about the metadata option:metadat 0.90Use the original 0.90 format superblock. This format... limits component devices of levels 1 and greater to 2 terabytes.So it is explained!So, removing the '--metadata 0.9' option make it use the now default 1.2 metadata format.The reason why I use the 0.9 metadata is to enable users to revert the box to the DLink firmware, that only accepts the 0.9 format. But this is a nonsense, because the DLink firmware does not supports 3TB disks.
So, try
mdadm --create /dev/md0 --run --level=raid1 --bitmap=internal --raid-devices=2 --verbose --verbose /dev/sda2 /dev/sdb2
echo $?If, again, a '1' is printed, meaning that the command failed, and in order to have more information on your setup, please post those commands output (otherwise just reply Worked! -- but don't forget that you still have to create a filesystem on the newly create md0 RAID device)sfdisk -luS /dev/sda /dev/sdbsgdisk -p /dev/sdasgdisk -p /dev/sdbcat /proc/mdstatcat /etc/mdadm.conflsmod
If you remember: When you used the Disk Partitioner to partition your disks, how did you proceed? Used the Advanced Button and copied the start sector/lenght values from another thread? Or used the Size (GB) entry only?
On Tuesday, November 13, 2012 10:42:34 PM UTC+4, Joao Cardoso wrote:mdadm --create
/dev/md0
--run --level=raid1 --metadata=0.9 --bitmap=internal --raid-devices=2 /dev/sda2 /dev/sdb2 # create the RAID
echo $?
# mdadm --create /dev/md0 --run --level=raid1 --metadata=0.9 --bitmap=internal --raid-devices=2 /dev/sda2 /dev/sdb2 # create the RAID
# echo $?
1
If this works then an unnoticied/unreported bug exists in RC2.
If this does not works also, then I'm puzzled, as everything else looks fine.
Hmmm, then i will hope it is a bug (not a common hope but better than an enigma) (though i am guessing an enigma as this is outputting the same "1" as before?)It's an enigma :-OThe printed '1' means that the command failed. What is strange is that no error message appears, so we don't know what is wrong. Please tryBut the mdadm manual says about the metadata option:metadat 0.90Use the original 0.90 format superblock. This format... limits component devices of levels 1 and greater to 2 terabytes.So it is explained!So, removing the '--metadata 0.9' option make it use the now default 1.2 metadata format.The reason why I use the 0.9 metadata is to enable users to revert the box to the DLink firmware, that only accepts the 0.9 format. But this is a nonsense, because the DLink firmware does not supports 3TB disks.oi, i used to be so proud of myself being able to install slackware, mount disks via command line and even understand the basics of differences between filesystems... but this is a few levels above that :( think i thought it though.So, try
mdadm --create /dev/md0 --run --level=raid1 --bitmap=internal --raid-devices=2 --verbose --verbose /dev/sda2 /dev/sdb2
echo $?
If, again, a '1' is printed, meaning that the command failed, and in order to have more information on your setup, please post those commands output (otherwise just reply Worked! -- but don't forget that you still have to create a filesystem on the newly create md0 RAID device)sfdisk -luS /dev/sda /dev/sdbsgdisk -p /dev/sdasgdisk -p /dev/sdbcat /proc/mdstatcat /etc/mdadm.conflsmod
On Wednesday, November 14, 2012 8:03:33 PM UTC+4, Gaiko wrote:
Anyway, all seems to work. Yeah!!!!
https://dl.dropbox.com/u/507145/status.jpg
Before I start to fill up my box please let me know if there is anything you'd like me to try out first!
Thx again!
Do you have an idea how long did the filesystem creation took?
Thanks
fdisk: device has more than 2^32 sectors, can't use all of them HTTP/1.0 200 OK Content-Type: text/html; charset=UTF-8 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html style="height: 100%;"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <title></title></head><body style="height: 100%;"> <center><h2>Disk Partitioner</h2></center> <script type="text/javascript"> document.body.style.cursor = 'wait'; </script> <p>Stopping disk... done.</p> <p>Partitioning disk sda... done</p><p>Setting up partitions details... done</p><p>Reloading all disks... done</p> <script type="text/javascript"> document.body.style.cursor = ''; </script> <p><strong>Success</strong></p> <script type="text/javascript"> function err() { window.location.assign(document.referrer) } setTimeout("err()", 3000); </script> </body></html>
Well i uploaded the files, overwrote the existing files made them executable (actually they already were rwx since copied from ntfs) tried out the wizard and got the following:
https://dl.dropbox.com/u/507145/Wizzard.jpg
i=/dev/sda
nextstart=$(sgdisk --set-alignment=8 --first-in-largest $i)
nextend=$(sgdisk --set-alignment=8 --end-of-largest $i)
nextleng=$(expr $nextend - $nextstart)
echo $nextstart $nextend $nextleng
Now this could be because of the fact that I have a RAID1 setup and didn't "break it up" (how would i do that?)
after trying to use the partition wizard:
fdisk -l /dev/sda 2> /tmp/foo > /tmp/bar
cat /tmp/foo
cat /tmp/bar
rm /tmp/foo /tmp/bar
fdisk: device has more than 2^32 sectors, can't use all of them HTTP/1.0 200 OK Content-Type: text/html; charset=UTF-8 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html style="height: 100%;"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <title></title></head><body style="height: 100%;"> <center><h2>Disk Partitioner</h2></center> <script type="text/javascript"> document.body.style.cursor = 'wait'; </script> <p>Stopping disk... done.</p> <p>Partitioning disk sda... done</p><p>Setting up partitions details... done</p><p>Reloading all disks... done</p> <script type="text/javascript"> document.body.style.cursor = ''; </script> <p><strong>Success</strong></p> <script type="text/javascript"> function err() { window.location.assign(document.referrer) } setTimeout("err()", 3000); </script> </body></html>
Well i uploaded the files, overwrote the existing files made them executable (actually they already were rwx since copied from ntfs) tried out the wizard and got the following:
https://dl.dropbox.com/u/507145/Wizzard.jpgDamn!
Can you please execute the following commands after using the Disk Wizard?
i=/dev/sda
nextstart=$(sgdisk --set-alignment=8 --first-in-largest $i)
nextend=$(sgdisk --set-alignment=8 --end-of-largest $i)
nextleng=$(expr $nextend - $nextstart)
echo $nextstart $nextend $nextleng
# i=/dev/sda
# nextstart=$(sgdisk --set-alignment=8 --first-in-largest $i)
# nextend=$(sgdisk --set-alignment=8 --end-of-largest $i)
# nextleng=$(expr $nextend - $nextstart)
# echo $nextstart $nextend $nextleng
5860531184 5860533134 1950
Now this could be because of the fact that I have a RAID1 setup and didn't "break it up" (how would i do that?)No, the partition table is erased at start.
after trying to use the partition wizard:Damn again!
In the Disk Partitioner page itself, or after hitting the Partition button?
Have you used any other button/menu?
Some of the "Partition Table" operations in the upper section (Loading/saving/Copying...) might yet not be working for 3TB.
Stopping disk... done.
Copying partition table from sda to sdb... done
Reloading all disks... done
Success
After erasing sda:
Disk Partitioner
Stopping disk... done.
Erasing partition table from sda... done
Reloading all disks... done
Success
After trying to load; to be totally honest I didn't quite follow what i was "loading" but hey, all disks are blank didn't think it would brick my box so i tried it and:can you please execute the following commands and post the output?
fdisk -l /dev/sda 2> /tmp/foo > /tmp/bar
cat /tmp/foo
cat /tmp/bar
rm /tmp/foo /tmp/bar
# fdisk -l /dev/sda 2> /tmp/foo > /tmp/bar
# cat /tmp/foo
fdisk: device has more than 2^32 sectors, can't use all of them
# cat /tmp/bar
Found valid GPT with protective MBR; using GPT
Disk /dev/sda: 4294967295 sectors, 4095M
Logical sector size: 512
Disk identifier (GUID): 0f9a1402-8821-4949-9609-41f612d1887c
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 5860533134
Device Start (sector) End (sector) Size (sectors) Code Name
/dev/sda1 64 1048639 1048576 8200
/dev/sda2 1048640 5860531183 5859482544 fd00
# rm /tmp/foo /tmp/bar
Thanks for your collaboration and patience,Joao
On Thursday 15 November 2012 10:04:24 Gaiko wrote:
> On Thursday, November 15, 2012 9:39:09 PM UTC+4, Joao Cardoso wrote:
> > Well i uploaded the files, overwrote the existing files
> > made them
> >
> >> executable (actually they already were rwx since copied from ntfs)
> >> tried
> >> out the wizard and got the following:
> >> https://dl.dropbox.com/u/507145/Wizzard.jpg
> >
> > Damn!
> >
> > sorry
> >
> > Can you please execute the following commands after using the Disk
> > Wizard?
...
> > # i=/dev/sda
> > # nextstart=$(sgdisk --set-alignment=8 --first-in-largest $i)
> > # nextend=$(sgdisk --set-alignment=8 --end-of-largest $i)
> > # nextleng=$(expr $nextend - $nextstart)
> > # echo $nextstart $nextend $nextleng
> > 5860531184 5860533134 1950
Something is not OK.
In the screenshot you posted, the message says that the start of partition 3 (tipically a small partition at the disk end) is at sector "1 565 565 839", about 801GB (which is wrong), but now it is at sector "5 860 531 184", about 3TB (which is OK).
I don't know if you have read the following, added some minutes after my post:
[Added: the .cgi uploaded files do not survive a reboot, you have to copy them again.
And you should not have any Alt-F package installed before copying them. If you have, please hit the RemoveAll button in the "Installed packages" section of the Packages->Alt-F web page]
I was expecting a message similar to "Error creating second partition...", what you posted is the RC2 stock message, so you was not using the files I posted.
Can you please repeat the procedure from the beginning?
To make sure you are using the right files, run the command
grep creating /usr/www/cgi-bin/diskwiz*
after putting the files in the box, and you should get something like:
/usr/www/cgi-bin/diskwiz_proc.cgi: err "Error creating swap: $res"
/usr/www/cgi-bin/diskwiz_proc.cgi: err "Error creating first partition: $res"
/usr/www/cgi-bin/diskwiz_proc.cgi: err "Error creating second partition: $res"
Make sure that you have no Alt-F packages installed, the command
ls -l /
should *not* display a 'Alt-F -> /mnt/<anything>/Alt-F'
Then run the Disk Wizard and after getting the error, if any, don't do anything more, just run at the command line
sgdisk -p /dev/sda
sgdisk -p /dev/sdb
...
> >> after trying to use the partition wizard:
> > Damn again!
> >
> > sorry again
> >
> > In the Disk Partitioner page itself, or after hitting the Partition
> > button?
> After hitting the partition button
>
> > Have you used any other button/menu?
>
> no, not yet.
OK.
...
> > can you please execute the following commands and post the output?
> >
> > fdisk -l /dev/sda 2> /tmp/foo > /tmp/bar
> > cat /tmp/foo
> > cat /tmp/bar
> > rm /tmp/foo /tmp/bar
> >
> >
> > # fdisk -l /dev/sda 2> /tmp/foo > /tmp/bar
> > # cat /tmp/foo
> > fdisk: device has more than 2^32 sectors, can't use all of them
> > # cat /tmp/bar
> > Found valid GPT with protective MBR; using GPT
> >
> > Disk /dev/sda: 4294967295 sectors, 4095M
> > Logical sector size: 512
> > Disk identifier (GUID): 0f9a1402-8821-4949-9609-41f612d1887c
> > Partition table holds up to 128 entries
> > First usable sector is 34, last usable sector is 5860533134
> >
> > Device Start (sector) End (sector) Size (sectors) Code
> > Name
> >
> > /dev/sda1 64 1048639 1048576 8200
> > /dev/sda2 1048640 5860531183 5859482544 fd00
> > # rm /tmp/foo /tmp/bar
Thanks.
That will help removing the "fdisk: device has more than 2^32 sectors, can't use all of them" error message.
I will post the fixed files as soon as I write them, now I've to cook the dinner :-)
> > Thanks for your collaboration and patience,
> > Joao
>
> Well #1 I've been waiting to get 3tb drives for awhile (months) so i can
> wait a bit longer and #2 You spoon fed me through getting it working via
> cmd line so I'm trying to get my karma in order :)
Your karma is OK for me :-), you already helped with the metadata issue, there is more people interested in using 3TB disks, so let them improve their karma!
Thanks,
Joao
I was expecting a message similar to "Error creating second partition...", what you posted is the RC2 stock message, so you was not using the files I posted.
Can you please repeat the procedure from the beginning?
To make sure you are using the right files, run the command
grep creating /usr/www/cgi-bin/diskwiz*
after putting the files in the box, and you should get something like:
/usr/www/cgi-bin/diskwiz_proc.cgi: err "Error creating swap: $res"
/usr/www/cgi-bin/diskwiz_proc.cgi: err "Error creating first partition: $res"
/usr/www/cgi-bin/diskwiz_proc.cgi: err "Error creating second partition: $res"
Make sure that you have no Alt-F packages installed, the command
ls -l /
should *not* display a 'Alt-F -> /mnt/<anything>/Alt-F'
Joao