Installing images on USB?

[luis]

I have OoZooN in flash and 2 images on USB: Nemesis 2.4 101r1 and DE 2.1. Both worked OK until I updated online Nemesis to 2.5 104r4. After updating images on USB can´t boot any more (both of them). Booting hangs on "starting enigma".

So I wanted to install on USB the previous Nemesis 2.4 101r1 again, using BA 6.2.0. Ftp-ed the image into /media/ba/MB_Images folder, started BA > Wizard for images at /MB_Images > extract nfi Image from /MB_Images. But there´s no file in that folder to select for installation. What am I doing wrong? Is there some other folder in OoZooN I should put the image file into for extracting? Both OoZooN and Nemesis 2.4 have ssl #84. Would someone tell me what to do?

[oldfart]

can't remember - have a look at the english translation for BA - its on OoZooN;s web site

[luis]

It looks like USB stick problem. After I updated Nemesis and then couldn´t boot I had a look at Menu > Setup > System > Storage devices. There I saw my USB stick > OK on it and got the message: "No mountpoint defined!". So it probably unmounted in the updating process???
Went to "Manually select a mountpoint for this storage device now" > "Enable partition automount?" > "Yes". "Mountpoint" appeared and I wrote: /media/usb > Save (green). "Use these settings?" > "Yes". Then I got the message again: "No default storage device defined! Please make sure to set up default storage device in menu: Setup > System > recording path".
Here I stopped and gave up since I don´t know what I´m doing any more. Should I put down some other mountpoint instead of /media/usb??? If so, what? Thank you for your answers.

[brain]

Hi there
I think you may need to go through the menu to mass storage and format and umount the usb if you can afford to lose the data on the usb. Also make sure in BA r that you then define the media/usb path before putting images on. I could be barking up the wrong tree here but I can remember something similar a few months ago> Hope it helps - Cheers - Brain

[oldfart]

what devices have you got?
hdd/usb

[luis]

Yes, hdd and usb. If I ftp the image into MB_Images > media/hdd/backup/, it can be found in BA > "list nfi images at /MB_Images", or "extract nfi image from /MB_Images" (for installation). But then the image would be installed on hdd. I want it installed on USB. But if I put it in /media/usb/MB_Images/ it´s not there when I start BA. That´s why I think something went wrong with USB.
And no, I wouldn´t like to format USB and lose what´s on. I stil hope in can be mounted the right way.

[brain]

Format your stick with comp as FAT32 and put stick pen in dm box so dont think there is a way around not losing what is on it - you can always reload it again afterwards. After that you need to flash box from beginning. If your stick is compatible it will be recognized usually as usb via the BA media/usb/ route. Some usb are not always compatible with DM but obviously the one you have was and still should be. In menu you can then check mounting in hardware management and also mount any HDD, but unlike old 7000's it does seem that with BA the usb has to be added at flashing time and is very difficult to add later when hdd is in place. hope this may help - brain

[luis]

Thank you brain. Yes, the USB stick is, no doubt, compatible with the box since it has worked OK for a long time. I can´t decide whether to reflash the box and start everything from the beginning again, I had a big problem the last time to format and mount the stick and made it work. I don´t know if it´s worth the hassle again. I can use OoZooN in flash with no problem at the moment, so I might think of something else to try.

I can still remember the good old times of DM7000, when activating an USB with FlashWizard was a piece of cake.

[oldfart]

The USB is probably not mounted
Telnet into the box
mount
Will tell you what is mounted where
fdisk -l (lowercase L)
Will tell you what drives you have
Assuming the USB is /dev/sdb1
Type mount /dev/sdb1 /media/usb
This will not survive a reboot, but useful to test
You have to edit /etc/fstab to survive a reboot

[luis]

Thank you m8, I´ll try that.

[luis]

@oldfart

How do I edit the fstab file to revive the booting in USB images? What do I change?
It looks that, when updating, the new enigma overwrote something to do with booting...

[oldfart]

post
1. the results of fdisk -l
and
2. your current fstab file

[luis]

Here you are m8:

fdisk –l:


root@dm8000:~# fdisk -l

Disk /dev/sda: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 243201 1953512032 83 Linux

Disk /dev/sdc: 2082 MB, 2082471936 bytes
65 heads, 62 sectors/track, 1009 cylinders
Units = cylinders of 4030 * 512 = 2063360 bytes

Device Boot Start End Blocks Id System
/dev/sdc1 1 1009 2033104 83 Linux


fstab file:

#automatically edited by enigma2, Mon, 20 Feb 2012 21:51:46
rootfs / auto defaults 1 1
proc /proc proc defaults 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
usbfs /proc/bus/usb usbfs defaults 0 0
/dev/mtdblock2 /boot jffs2 ro 0 0
tmpfs /var tmpfs defaults 0 0
tmpfs /tmp tmpfs defaults 0 0
/dev/disk/by-uuid/14ce550c-d93a-476a-bc1e-4c1bfa2ad829 /media/hdd noauto defaults 0 0
/dev/disk/by-uuid/37916f19-72d2-436f-822d-14789bec755e /media/Mini noauto defaults 0 0
/dev/disk/by-uuid/37916f19-72d2-436f-822d-14789bec755e /media/usb noauto defaults 0 0

[oldfart]

ok
can you post the results of
ls -alh /dev/disk/by-uuid/*

[luis]

Gave the command and got: "-sh: alh: not found"

[oldfart]

copy it from the forum
paste into telnet/putty
that way the spacing and letters will be correct

[luis]

Here m8:

dm8000 login: root
Password:
root@dm8000:~# ls -alh /dev/disk/by-uuid/*
lrwxrwxrwx 1 root root 10 Jan 1 2000 /dev/disk/by-uuid/14ce55
0c-d93a-476a-bc1e-4c1bfa2ad829 > ../ ../sda1
lrwxrwxrwx 1 root root 10 Jan 1 2000 /dev/disk/by-uuid/37916f
19-72d2-436f-822d-14789bec755e > ../ ../sdc1
lrwxrwxrwx 1 root root 9 Jan 1 2000 /dev/disk/by-uuid/a07f2d
38-f92b-471f-9a8c-06c756ac7df3 > ../ ../sdc
root@dm8000:~# ls -alh /dev/disc/by-uuid/*

[oldfart]

wierd
you have the same device mounted twice
sdc1 is mounted as /media/usb and as media/Mini
no idea where that came from

I assume you're OK with editing linux files - you can't use notepad
try puting a # in front of the line in /etc/fstab

/dev/disk/by-uuid/37916f19-72d2-436f-822d-14789bec755e /media/Mini noauto defaults 0 0
then reboot

[luis]

No problem editing the files m8. I use UltraEdit. So I´ll put the # in front of the .../media/Mini line to disable it.
Regarding the telnet answers I posted, can you tell me if USB stick is properly mounted?

[oldfart]

you didn't post the results from the mount command

but fstab should correctly mount both the hdd & usb

BA stores the nfi files (images) in /media/hdd/MB_Images with a symbolic link pointing to that directory called MB_Images
the actual 'flash' backups of each image is then stored on the usb drive
if the usb is not mounted - then ba won't work
in your case, you have 2 mount points for the one device (according to fstab)- this could be causing problems

[luis]

Here´s the missing telnet "mount":

dm8000 login: root
Password:
root@dm8000:~# mount
rootfs on / type rootfs (rw)
proc on /proc type proc (rw)
/dev/mtdblock3 on / type jffs2 /rw
/dev/sdc1 on /media/ba type ext3 (rw,data=ordered)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/mtdblock2 on /boot type jffs2 (ro)
tmpfs on /var type tmpfs (rw)
tmpfs on /tmp type tmpfs (rw)
automount(pid860) on /autofs type autofs (rw,fd=4,pgrp=860,timeout=5,minpr oto=2,maxproto=4,indirect)
/dev/disk/by-uuid/14ce550c-d93a-476a-bc1e-4c1bfa2ad829 on /media/hdd type ext3 (rw,data=ordered)
/dev/disk/by-uuid/37916f19-72d2-436f-822d-14789bec755e on /media/usb type ext3 (rw,data=ordered)
root@dm8000:~#


Have put # in front of the .../media/Mini... line in fstab file, rebooted the box into Nemesis on USB, but no such luck. It still hangs on "starting enigma".

I´m thinking about installing Nemesis 2.4 101r1 (which is a stable image) on USB anew and then not updating it online. As I said, if I put .nfi file in /media/USB/MB_Images for the installation, BA doesn´t find it there. But if I put it in the folder MB_Images > /media/hdd/backup, BA finds it there alright.

As I understand from your last post - if I put the .nfi file into /media/hdd/backup, it will still be installed on USB, not HDD. IS THAT RIGHT??? No way would I like images installed on HDD, which would then run all the time.

[oldfart]

no
the image (nfi) files go onto the hdd, then from ba install image puts it onto usb

everything looks right - your mount points are correct
did you start with OoZooN in flash, then put ba on, then images
you need the loop driver, which is in the OoZooN image - if you started with Nemesis - that might be the problem.

can you boot (from BA) into flash?

[luis]

I can only start on OoZooN in flash. Can´t start on the images on USB since I can´t boot on them. Yes, I can boot into flash, it´s the only image where the booting procedes normally. Booting in flash I can select all the images (in USB also) when BA appears. They all start booting but hang at "starting enigma" except if I select flash.

So, putting the .nfi file into /media/hdd/backup for installation is OK, it will be installed on USB, right?

[oldfart]

dunno - its gone beyond me!
its probably better if you ask gutemine directly - he is on OoZooN forum

[luis]

Thank you anyway m8, you´ve done what you could. After all, I can´t use more than one image at the same time. It´s essential that I have a stable one that works OK, which OoZooN certainly is. It´s welcome to have some others on USB to compare and play a little, but it´s not a must.

[oldfart]

I did the same
had about 10 images on usb
had a look at them all
My opinion - thay are all the same - they allow you to watch telly!
some have more bells & whistles - but not at all stable
I have used OoZoon for over a year, I know how it works - which is probably the most important bit
and
it hasn't got loads of confusing menus