|
|
Post by tairus on Aug 24, 2007 0:10:49 GMT 7
I tried to backup internal flash in order to write image to a bigger flash (8GB CF card) to have more space for customization.
I used Acronis True Image.
True Image is always stuck on backing up first partition. Why?
I noticed one thing: Trie Image reports 32MB of all partitions, while my DOM is 128MB. It looks like i already have a plenty of free space. Ok.
Then i went to SSH in 5200 and tried to use fdisk to create one more partition, but fdisk reported that there is no free space on disk to allocate new partition.
Now i'm confusing.. Have anybody tried to create new partition on internal flash? It's strange to have a lot of free space and don't use it.
Using RAID space to store system files/configs isn't good idea, IMHO..
|
|
|
|
Post by hazelday on Aug 28, 2007 22:23:03 GMT 7
Can you explain why you think that flash is safer for configuration? Configuration is likely to change, and traditionally, flash is only good for a few thousand write cycles. Disks, especially RAID, are generally good for many times that.
Thanks,
-Peter
|
|
|
|
Post by tairus on Aug 29, 2007 2:33:20 GMT 7
if something wrong with RAID (or for example you pulled away disks) then your configs will not be loaded. Actually, N5200 flash used not only for reading but also for writting even in standard use. So, i don't see a reason why additional configs have to use RAID instead flash. by the way, i know why i couldn't backup DOM. It's because i connected it through IDE->USB converter which set wrong CHS parameters. Should be 8 heads, 32 sectors, but USB convertor set 255 heads, 53 sectors which doesn't work for DOM. After some tricks i could back it up. After that i re-partitioned DOM and restored backup. Now i have 56MB of free space on DOM  and later i successfully connected my 8GB CF as primary slave disk, so now i have a plenty of free flash space! |
|
|
|
Post by omega on Aug 29, 2007 2:34:43 GMT 7
Tairus,
what does fdisk show for the partition table on the disk?
Peter: even if you change the configuration every day, it will last at least for 3 years - plenty of time.
Storing the configuration on flash disk improves security as hard disk failures are more likely than flash disk failures.
Andreas
|
|
|
|
Post by tairus on Aug 29, 2007 3:09:40 GMT 7
now, after my repartitioning fdisk shows this:
Disk /dev/hda: 8 heads, 32 sectors, 978 cylinders
Nr AF Hd Sec Cyl Hd Sec Cyl Start Size ID
1 80 1 1 0 7 32 16 32 4320 83
2 00 0 1 17 7 32 113 4352 24832 83
3 00 0 1 114 7 32 370 29184 65792 83
4 00 0 1 371 7 32 977 94976 155392 05
5 00 1 1 371 7 32 451 32 20704 83
6 00 1 1 452 7 32 513 32 15840 83
7 00 1 1 514 7 32 977 32 118752 83
i didn't save original info, unfortunately.
But originally CHS values were completely wrong. fdisk refused to create any aditional partition while there were a lot of free space.
I think, originally DOM image has been created for 64MB, but thecus used some strange disk cloner and CHS values have been messed.
Actually, i want to move whole "modules" folder to flash drive, but seams it's impossible. Looks like /img folder is recreating with every boot and thus at least one module have to be on RAID. it will run to change /img to a new location where other modules and configs are.
Or is there any other way to put "modules" location permanently to flash drive? Actually, i don't have enough details about booting process of thecus firmware...
|
|
|
|
Post by omega on Aug 29, 2007 3:21:20 GMT 7
Tairus,
what fdisk are you using? Not the one on the N5200!?
The partition table you're showing looks really weird to me. I expected to see one or maybe two partitions, not 8....
Andreas
|
|
|
|
Post by tairus on Aug 29, 2007 3:44:46 GMT 7
i use standard fdisk from N5200.
Originally there were 6 partitions made by thecus.
I added 7th.
did you try to run fdisk /dev/hda on your N5200?
here is mounting info from my N5200
root@127.0.0.1:/img/www/htdocs# mount
rootfs on / type rootfs (rw)
/dev/root on / type ext2 (rw)
/dev/hda5 on /app type ext2 (rw,noatime)
tmpfs on /tmpfs type tmpfs (rw)
/dev/hda3 on /cloopfs type ext2 (rw)
proc on /proc type proc (rw,nodiratime)
sysfs on /sys type sysfs (rw)
none on /dev/pts type devpts (rw)
/dev/cloop0 on /lib/modules type ext2 (ro)
/dev/cloop1 on /opt type ext2 (ro)
/dev/cloop2 on /img.SAVE/www type ext2 (ro)
/dev/cloop3 on /img.SAVE/bin type ext2 (ro)
/dev/cloop4 on /lib/security type ext2 (ro)
/dev/cloop5 on /usr/share/zoneinfo type ext2 (ro)
sunrpc on /tmpfs/var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)
/dev/vg0/lv0 on /raid0/data type ext3 (rw,noatime)
/dev/vg0/syslv on /raid0/sys type ext3 (rw)
|
|
|
|
Post by koumeles on Nov 20, 2022 11:53:43 GMT 7
if something wrong with RAID (or for example you pulled away disks) then your configs will not be loaded. Actually, N5200 flash used not only for reading but also for writting even in standard use. So, i don't see a reason why additional configs have to use RAID instead flash. by the way, i know why i couldn't backup DOM. It's because i connected it through IDE->USB converter which set wrong CHS parameters. Should be 8 heads, 32 sectors, but USB convertor set 255 heads, 53 sectors which doesn't work for DOM. After some tricks i could back it up. After that i re-partitioned DOM and restored backup. Now i have 56MB of free space on DOM and later i successfully connected my 8GB CF as primary slave disk, so now i have a plenty of free flash space! Hallo, can You share somewhere image of Your backuped DOM, please? My data on my DOM are corupted, now... ;-[ Thank You, K. |
|
