Yes. I tested this case. In addition to putting in a new HDD, you'll have to flash the firmware.Quote:
Originally Posted by iczfirz
- K.C.
Printable View
Yes. I tested this case. In addition to putting in a new HDD, you'll have to flash the firmware.Quote:
Originally Posted by iczfirz
- K.C.
Woww. May I know the details?Quote:
Originally Posted by kfurge
I did try putting my new disk into the brick and flash the firmware with recovery tools. Seems no luck. The tools always failed to flash.
So if yes, then I can change my internal 250G to 200G, let the external 250G be a mirror and internal 200G as the base.
~May
i think you have to do the same steps if you go back from openwrt to the asus firmware as there is written:
http://wl700g.homelinux.net/drupal/index.php?q=node/54
grat182
suprise to do such action for a disk replacement.:eek:
I just assume if a new harddisk insert, the firmware will clever enough to help me work it out.
~May
thanks KC and gr.
I follow the given link. It works!
The reason why such elaborate steps are necessary is because only the kernel and a *very* minimal filesystem is stored in flash. All of the rest of the "firmware" is on the HDD in a cramfs located redundantly in the first two partitions.
Therefore, when you replace the HDD, the bulk of the firmware is no longer present. Upon boot-up, the kernel detects this case and boots with the filesystem in flash that only knows enough to talk to the reflash tool from Asus. Reflashing builds the firmware paritions and the router completes the rebuild of MYVOLUME1 with the next reboot.
- K.C.
Thanks KC.
btw, will the build in mirror feature spindown the mirror disk or not?
~May
all your thoughts are going boldly nowhere !
The wl700g uses the linux 2.4 softraid feature to build the mirror.
simply type :
cat /proc/mdstat
and you see the raid configurations
i have not used this on my own linux systems, so my knowledge is purely theoretical.
when using the mirror disk on knoppix you should use
mdadm -A /dev/md0/ /dev/xxx
mount /dev/md0 /mnt/softraid
with xxx the linux devicename (hda or sda etc.) sould give you the disk on a linux box with reiserfs and softraid support build into the kernel ( or as modules )
why sould asus implement its own raid/mirroring feature if the kernel has a buildin raid?
I know the problems when you use mirroring from my old PC System with onboard raid. At first linux didn't understand the raid feature and could not mount the disks (fat/ntfs) it wouldn't even see a valid partition map because of the administrative information stored on the disks. This also applies to softraid.
I don't know if mdadm is exactly the tool you need, but you must prepare a raid/mirror only containing your disk to access it's informations.
cu
Harald
Hi all
I ran into this same problem myself where I couldn't access the mirror but I know why! Linux software RAID doesn't support the /boot partition being mirrored. I mirrored the /boot partition anyway and found that while my drives would mirror I could only boot from one of them. This is despite making up a boot floppy with Grub that tried to boot the mirrored drive that wouldn't boot.
Thanks for the advice above to remove raid by using Expert Partitioner in SLES 10 because it didn't erase my data and I was then able to mount the mirrored drive and access my data. I've documented this att http://www.solvedit.com.au/content/view/81/42/.
I had a Xen VM on this now unmirrored drive and I was able to run this VM from the new pc. This is documented at http://www.solvedit.com.au/content/view/82/42/
No. Spin-down and mirroring are completely independent functions.Quote:
Originally Posted by iczfirz
- K.C.