Replacing the old, smaller DOM in AZbox HD old models...

gorski

Registered
Messages
1,553
Here is what I did today, since getting a new, 4 times larger DOM by Transcend...

Images instead of thousands of words... ;)

Titles of each image are 'nuff... :)

P.S. SPAZE is a larger, heavier, hence slower image, with all the goodies crammed inside it, so one needs a larger DOM or USB stick in collaboration with Flash Expander for AZ HD!!! See my guides etc.:cool:
 

gorski

Registered
Messages
1,553
Btw, all of those kernel module updates didn't solve the (NFS NAS and CIFS laptop, at my end) mounting in SPAZE, sadly...

And we are still waiting for a new, OpenPLi compatible kernel and related images for older models...

Maybe it will be 13 000th time lucky?:rolleyes::p:D:thum::clapping:
 

martin.nl

Registered
Messages
5
Hi Gorski,

I am just planning to do something similar.
How did you load image on DOM. Did you get IP when you boot with empty DOM?
 

gorski

Registered
Messages
1,553
In your router/modem you reserve an IP address for your STB, in relation to its MAC address (it's very straight forward).

Sorted! No DHCP but a static address and you know which one it is, even if you can't see it on the VFD.

Load the image as usual. Don't forget, it's the Loader that is already there and so it will work easily!
 

martin.nl

Registered
Messages
5
In your router/modem you reserve an IP address for your STB, in relation to its MAC address (it's very straight forward).

Sorted! No DHCP but a static address and you know which one it is, even if you can't see it on the VFD.
OK, that part is clear...

Load the image as usual. Don't forget, it's the Loader that is already there and so it will work easily!
When you put blank DOM and boot the receiver, it will load some basic system (loader) from some built-in memory. Right?
 

stuff.hunter

Registered
Messages
125
nice mod mate :)
btw saw somewhere something a bit different: it was standard IDE HDD hooked up with external psu for it, did anyone tried this?
 

gorski

Registered
Messages
1,553
Not good, for this purpose - not if there's any moving parts... constantly... if you get my drift... ;)
 

stuff.hunter

Registered
Messages
125
hiya Gorski,
got my new DOM and have a quick question:
what image did you load as first after replacing yours, official or spaze. cheers
 

gorski

Registered
Messages
1,553
As I wrote, Spaze 2.2...

But now I would always prefer PB image, with Fabry's script for larger DOMs...

You only have to edit it a little bit to suit your needs...

Good luck!
 

gorski

Registered
Messages
1,553
Here it is...

=============

Preparatory bits:

For newbies, how to do this:

Install PB E2 VX into your AZbug HD. Let it boot properly.

Plug in a USB stick (formatted in EXT3) at the back of your AZbug, go to PB Centre > Device Manager > see the commands/coloured buttons > mount it as media/usb, so it will be there under dev/sda1.

Then, go into Rescue Mode (switch the AZbug at the back, then ON again, press > button on the front panel and hold, 'till you see the IP address of the rec.).

Start Telnet SW (PuTTy) on your PC, log-in by typing "root" (without "" signs), then copy and paste one line of the script above at the time...

Do not try to put in the next one unless you see the # sign come up in the next row, below the command you just issued.

When 2 or 3 commands are given you will have to wait, 'till all the copying is done...

Copy the script from this thread into Notepad++ and then copy each line from it into PuTTy.

When you are in PuTTy, put the cursor where you need to paste a copied line, then right click and the message will be pasted, then hit the ENTER keyboard and watch... Then, the next one...

In AZbug with E2, under /etc > fstab insert the new partition manually:

Code:
/dev/hda5               /media/cf               auto    defaults                0  0

Sometimes it takes a few reboots until it is finally mounted, so don't give up easily...

Enough?

=============

So, if you have a larger DOM (mine is 1GB) I better repeat this, in case you have missed it, one can now safely enlarge your Enigma2, SWAP and add a /cf partition.

Install E2 first, then run this script and you will have plenty of space for all your plugins, emus, skins, EPG, picons, scripts, subtitle files and whichever debauchery you can think of...
biggrin.gif
)

Thanx to Fabry's script, I can now copy the DOM contents to a USB stick, then resize the partitions according to my needs (larger E2 partition for more stuff on it, without it being clogged up), then return the content to DOM.

Fabry's script has to be modified only slightly, depending on the mounted USB device, in my case dev/sda1 = media/usb:

Code:
/dev/sda1             1         64     514048+ 83 Linux

The script to do it with looks like this, in my case (you will have to edit the second line according to your mounts, whether it's USB or HDD and if it is dev/sda1 or something else etc.):

Code:
mkdir usb
mount -o noatime /dev/sda1 usb
mkdir dom
mount -o noatime /dev/hda1 dom
cd usb
mkdir backup
cd backup
mkdir dom
cd /home/root
cp -a dom/* usb/backup/dom/
umount dom
echo ",512,83" > hda.out
echo ",4,83" **** hda.out
echo ",128,82" **** hda.out
echo ",,5" **** hda.out
echo ",,83" **** hda.out
sfdisk -f -uM /dev/hda < hda.out
mkfs.ext3 /dev/hda1 -b 4096 -E stride=96
mkfs.ext3 /dev/hda2 -b 4096 -E stride=96
mkswap /dev/hda3
mkfs.ext3 /dev/hda5 -b 4096 -E stride=96
sync
mount -o noatime /dev/hda1 dom
cp -a usb/backup/dom/* dom/
sync
umount usb
umount dom
reboot -f

Results:

Code:
Powered by Opensat
Linux/mips 3.5.5-opensat

# mkdir usb
# mount -o noatime /dev/sda1 usb
# mkdir dom
# mount -o noatime /dev/hda1 dom
# cd usb
# mkdir backup
# cd backup
# mkdir dom
# cd /home/root
# cp -a dom/* usb/backup/dom/
# umount dom
# echo ",512,83" > hda.out
# echo ",4,83" **** hda.out
# echo ",128,82" **** hda.out
# echo ",,5" **** hda.out
# echo ",,83" **** hda.out
# sfdisk -f -uM /dev/hda < hda.out
Checking that no-one is using this disk right now ...
OK

Disk /dev/hda: 1942 cylinders, 16 heads, 63 sectors/track
Old situation:
Units = mebibytes of 1048576 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End MiB #blocks Id System
/dev/hda1         0+ 183- 184- 187487+ 83 Linux
/dev/hda2     183+ 187-     5-     4536 83 Linux
/dev/hda3     187+ 245- 59-     59472 82 Linux swap / Solaris
/dev/hda4     245+ 955- 711- 727272 5 Extended
/dev/hda5     245+ 955- 711- 727271+ 83 Linux
New situation:
Units = mebibytes of 1048576 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End MiB #blocks Id System
/dev/hda1         0+ 512- 513- 524663+ 83 Linux
/dev/hda2     512+ 516-     5-     4536 83 Linux
/dev/hda3     516+ 645- 129- 131544 82 Linux swap / Solaris
/dev/hda4     645+ 955- 311- 318024 5 Extended
/dev/hda5     645+ 955- 311- 318023+ 83 Linux
Warning: no primary partition is marked bootable (active)
This does not matter for LILO, but the DOS MBR will not boot this disk.
Successfully wrote the new partition table

Re-reading the partition table ...

If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)
to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1
(See fdisk(8).)
# mkfs.ext3 /dev/hda1 -b 4096 -E stride=96
mke2fs 1.41.12 (17-May-2010)
warning: 93 blocks unused.

Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=96 blocks, Stripe width=0 blocks
32832 inodes, 131072 blocks
6558 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=134217728
4 block groups
32768 blocks per group, 32768 fragments per group
8208 inodes per group
Superblock backups stored on blocks:
    32768, 98304

Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 38 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
# mkfs.ext3 /dev/hda2 -b 4096 -E stride=96
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=96 blocks, Stripe width=0 blocks
1152 inodes, 1134 blocks
56 blocks (4.94%) reserved for the super user
First data block=0
1 block group
32768 blocks per group, 32768 fragments per group
1152 inodes per group

Writing inode tables: done

Filesystem too small for a journal
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 28 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
# mkswap /dev/hda3
Setting up swapspace version 1, size = 134696960 bytes
UUID=7349eff7-f42c-42d9-ab6d-f58403b9793d
# mkfs.ext3 /dev/hda5 -b 4096 -E stride=96
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=96 blocks, Stripe width=0 blocks
79584 inodes, 79505 blocks
3975 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=83886080
3 block groups
32768 blocks per group, 32768 fragments per group
26528 inodes per group
Superblock backups stored on blocks:
    32768

Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 26 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
# sync
# mount -o noatime /dev/hda1 dom
# cp -a usb/backup/dom/* dom/
# sync
# umount usb
# umount dom
# reboot -f

After the (successful E2) reboot, the partition table looked like this:

Code:
# fdisk -l

Disk /dev/hda: 1002 MB, 1002258432 bytes
16 heads, 63 sectors/track, 1942 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes

Device Boot     Start         End     Blocks Id System
/dev/hda1             1     1041     524663+ 83 Linux
/dev/hda2         1042     1050     4536 83 Linux
/dev/hda3         1051     1311     131544 82 Linux swap
/dev/hda4         1312     1942     318024 5 Extended
/dev/hda5         1312     1942     318023+ 83 Linux

Disk /dev/mtdblock0: 8 MB, 8388608 bytes
255 heads, 63 sectors/track, 1 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

So, now I have:

1/2 GB hda1 = E2 partition - meaning, lots of space to experiment with emus, skins, plugins and whatnot...
4 MB hda2 = who knows what this is for???
128 MB hda3 = SWAP partition - when big updates are available, this makes them possible...
over 300MB of hda4/5 = extended partition, i.e. /cf > where one directs EPG, picons, subtitles etc. (via HD Glass skin etc.).

Enjoy!:thum:
 

stuff.hunter

Registered
Messages
125
thx mate, ill try PB later on as cant register to their forum :(
trying to load spaze as we speak but jazup gave error : cant find destination at 30%, should DOM be set as master or slave? cheers
error log:
Your AZbox CPU mode is normal

Description Kernel : 2.6.22

FTP sending data kernel...
FTP Connected Send : kernel-jazup
FTP Send is true

FTP Transfer Ok!

Copying kernel (Hot!)... Please wait, this operation takes time!
FirmwareSize -> 53850112

ID Team : Spaze_TeamFinal_Version

ID Enigma : 2.2

Version : Quantum
DOM is selected for Upgrade

Your current kernel doesn't support ext4, back to ext3.

Checking availability of destination...

Sorry, destination not found...
Disconnect

JaZUp! is disconnected from your AZBOX
 

gorski

Registered
Messages
1,553
Master, I think - what else?

I didn't have any such problems...

Try PB and tell - just follow the instructions, the "manual" - always!!!
 
Last edited:

gorski

Registered
Messages
1,553
40-PIN? Which one exactly?

Exchange it for a smaller compatible one, like mine - tried and tested!!! :)
 
Top