Jump to content


Photo

OpenPLi 3.0: new alpha experimental images!


  • This topic is locked This topic is locked
369 replies to this topic

Re: OpenPLi 3.0: new alpha experimental images! #301 MiLo

  • PLi® Core member
  • 14,055 posts

+298
Excellent

Posted 7 August 2012 - 19:57

You don't have to. The fix works both ways.

The problem occurred in the installation script that came with a "new" kernel. Since you now get a fixed version of that script along with today's kernel, you can upgrade any old image.

(though I wonder why you'd want to "upgrade" a backup, that kinda defeats its purpose.)

Edited by MiLo, 7 August 2012 - 19:59.

Real musicians never die - they just decompose

Re: OpenPLi 3.0: new alpha experimental images! #302 rtzhjgg0

  • Senior Member
  • 568 posts

+13
Neutral

Posted 7 August 2012 - 20:34

You say that the fix works both ways (flashing the latest image and/or updating older ones).
So I falshed again the backup image of 2 Aug and made a simple online update. But after the reboot the box starts again in STOP-mode...
Selfsat H50M4
Ultimo4K /2xTwinS2, VTI, PLi, ATV...
NAS: Qnap221

Re: OpenPLi 3.0: new alpha experimental images! #303 gregoire

  • Senior Member
  • 82 posts

0
Neutral

Posted 7 August 2012 - 22:01

Oops just did an opkg update ; opkg upgrade and then a reboot and my DM8k don't goes further than the stop... is there any other way than a reflash ?

Re: OpenPLi 3.0: new alpha experimental images! #304 pieterg

  • PLi® Core member
  • 32,766 posts

+245
Excellent

Posted 7 August 2012 - 22:12

you could assemble an nfi with just the 'boot' partition in it, and flash that, keeping your root partition.
Alternatively, you can boot from usb, and resque your rootfs data (search the forum, a pretty detailed step by step was posted)

Re: OpenPLi 3.0: new alpha experimental images! #305 gregoire

  • Senior Member
  • 82 posts

0
Neutral

Posted 7 August 2012 - 23:37

Very good to know :-)
As I did "an error" in my first install (I installed crossepg which even after removal stayed in the plugins) I did it from scratch.
The only more or less important things I got on my DM are the channels which I have backup in DreamBoxEdit :-)

I missunderstood the previous comments about "STOP" which I thought were about the mediaplayer (I had a crash in pli3.0 while playing a file which was the reason I wanted to update).

Thank you for all !!!

Re: OpenPLi 3.0: new alpha experimental images! #306 rtzhjgg0

  • Senior Member
  • 568 posts

+13
Neutral

Posted 8 August 2012 - 06:16

...The fix works both ways.
The problem occurred in the installation script that came with a "new" kernel. Since you now get a fixed version of that script along with today's kernel, you can upgrade any old image...

Now (2012/08/08 06:30) your '/boot fix' works and I can seamlessly update my "precious" nfi backups ;)

Thanks for solving the problem :) B) :)
Selfsat H50M4
Ultimo4K /2xTwinS2, VTI, PLi, ATV...
NAS: Qnap221

Re: OpenPLi 3.0: new alpha experimental images! #307 rtzhjgg0

  • Senior Member
  • 568 posts

+13
Neutral

Posted 8 August 2012 - 06:21

...you can boot from usb, and resque your rootfs data...

...or you can use a Lowfat-stick. Here some useful operations you can do with this tool that is more than a Multiboot:

Flash can be:
-saved as nfi
-flashed from nfi
-embedded to stick as multiboot image
-mounted to /tmp/lowfat/lowfat (so you can copy, add or edit flash files from stick)

Multiboot images can be:
-saved as nfi
-renamed
-copied
-mounted to /tmp/lowfat/lowfat (so you can copy, add or edit files)
Selfsat H50M4
Ultimo4K /2xTwinS2, VTI, PLi, ATV...
NAS: Qnap221

Re: OpenPLi 3.0: new alpha experimental images! #308 exsat

  • Member
  • 21 posts

0
Neutral

Posted 8 August 2012 - 19:19

Hi,last time files in /media are missing.
There are no hdd directory, and this make problem to mount a nfs or a cifs mount.
Seems for me this problem also are in the latest 2.1 version.
When i create the hdd directory it is deleted after a reboot

Exsat.

Edited by Frenske, 8 August 2012 - 20:00.
I moved your issue to the english section.


Re: OpenPLi 3.0: new alpha experimental images! #309 antipop

  • Member
  • 10 posts

0
Neutral

Posted 8 August 2012 - 22:27

After today's update xtrend logo can be seen again ... of it was so nice.. :(
Of course, on the box Clarke in v.3.0.

Edited by antipop, 8 August 2012 - 22:28.


Re: OpenPLi 3.0: new alpha experimental images! #310 Dimitrij

  • PLi® Core member
  • 10,326 posts

+350
Excellent

Posted 9 August 2012 - 09:02

To Milo
Is there a solution for a double mount for UUID?
http://openpli.org/f...post__p__290087

GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K


Re: OpenPLi 3.0: new alpha experimental images! #311 ims

  • PLi® Core member
  • 13,783 posts

+214
Excellent

Posted 9 August 2012 - 09:16

It is after flash new firmware?

btw, you can try my mdev-mount.sh ( but i am not using swap file => is not solved ). In addition, you can use f.eg. with
/dev/sdd1 /media/front auto defaults 0 0
there in /etc/fstab => always all in usb reader is mounted under same name. I am using it long time... Only after change must be rebooted box, of source (and 755).

Attached Files


Kdo nic nedělá, nic nezkazí!

Re: OpenPLi 3.0: new alpha experimental images! #312 Dimitrij

  • PLi® Core member
  • 10,326 posts

+350
Excellent

Posted 9 August 2012 - 15:39

It is after flash new firmware?

PLi 3.0 but the new, I just update the software periodically.

btw, you can try my mdev-mount.sh ( but i am not using swap file => is not solved ). In addition, you can use f.eg. with

/dev/sdd1 /media/front auto defaults 0 0
there in /etc/fstab => always all in usb reader is mounted under same name. I am using it long time... Only after change must be rebooted box, of source (and 755).

Сhecked your mdev-mount.sh,but there is one:
fstab
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
tmpfs			    /var/volatile	    tmpfs	  defaults			  0  0
UUID=EA38F2FD38F2C819  /media/usb-hdd  auto    defaults	    0  0 # Usb-disk Trancend 500GB NTFS
UUID=24f3ec02-cb3e-427e-824d-bf15ad48325f /media/usb auto defaults 0  0 # Usb DT101 8GB EXT 3/4
UUID=CE51-3BCE		 /media/sdb auto defaults 0  0 # Usb Generic Multi-Card 1GB FAT32
UUID=0AF2285BF2284D6F	   /media/XtrenBootI auto defaults 0  0 # Usb takeMS 2GB NTFS
df -h
Filesystem			    Size	  Used Available Use% Mounted on
ubi0:rootfs			 105.1M	 79.1M	 25.9M  75% /
devtmpfs			    142.2M	  4.0K    142.2M   0% /dev
tmpfs				    64.0K		 0	 64.0K   0% /media
tmpfs				   142.4M    256.0K    142.1M   0% /var/volatile
/dev/sdd1				 7.4G    283.7M	  7.1G   4% /media/usb
/dev/sde1			   959.0M	  4.0K    959.0M   0% /media/sdb
/dev/sdc1				 2.0G	 33.8M	  1.9G   2% /media/XtrenBootI
/dev/sdb1			   465.8G	 71.2G    394.5G  15% /media/usb-hdd
fdisk -l
Disk /dev/sda: 640.1 GB, 640135028736 bytes
255 heads, 63 sectors/track, 77825 cylinders, total 1250263728 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
   Device Boot	  Start		 End	  Blocks   Id  System
/dev/sda1			   8  1250263727   625131860   83  Linux
Disk /dev/sdc: 2098 MB, 2098200576 bytes
255 heads, 63 sectors/track, 255 cylinders, total 4098048 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00e7fbd0
   Device Boot	  Start		 End	  Blocks   Id  System
/dev/sdc1			  63	 4098047	 2048992+   7  HPFS/NTFS
Disk /dev/sdd: 7920 MB, 7920943104 bytes
158 heads, 42 sectors/track, 2331 cylinders, total 15470592 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
   Device Boot	  Start		 End	  Blocks   Id  System
/dev/sdd1			   1    15470591	 7735295+  83  Linux
Disk /dev/sde: 1009 MB, 1009778176 bytes
255 heads, 63 sectors/track, 122 cylinders, total 1972223 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00e2b790
   Device Boot	  Start		 End	  Blocks   Id  System
/dev/sde1			  63	 1972222	  986080    c  W95 FAT32 (LBA)
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x4b125252
   Device Boot	  Start		 End	  Blocks   Id  System
/dev/sdb1			  63   976768064   488384001    7  HPFS/NTFS
You see, the disk /dev/sda is not mounted.
Because it is not written in fstab.
The result is not quite universal.

GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K


Re: OpenPLi 3.0: new alpha experimental images! #313 ims

  • PLi® Core member
  • 13,783 posts

+214
Excellent

Posted 9 August 2012 - 17:36

may be, sda1 is my internal hdd and i am using UUID for it...
Kdo nic nedělá, nic nezkazí!

Re: OpenPLi 3.0: new alpha experimental images! #314 exsat

  • Member
  • 21 posts

0
Neutral

Posted 9 August 2012 - 22:29

I am still wonder how a nfs mount can be done when there are missing the directory "hdd" inside the /media . The /hdd symlink are pointed to /media/hdd . Adding a hdd directory in /media will be deleted after reboot. Is there anybody that know how this can be done ? I know i can of course make a script that start after every reboot " mkdir /media/hdd" ,but this is a workaround and i assume this is not the way it should be done

Exsat

Re: OpenPLi 3.0: new alpha experimental images! #315 macnuts

  • Senior Member
  • 420 posts

+14
Neutral

Posted 10 August 2012 - 06:52

There is a 'use as hdd' [yes/no] option in the nfs mount settings. I can't recall if it really uses /media/hdd but I used nfs mount as the only storage and with this option set to yes it was working ok.

Regards.

Edited by macnuts, 10 August 2012 - 06:53.


Re: OpenPLi 3.0: new alpha experimental images! #316 macnuts

  • Senior Member
  • 420 posts

+14
Neutral

Posted 10 August 2012 - 07:06

As far as I can remember /media/hdd is a symlink to /media/net/nfssharename then.

(New post, I couldn't edit the previous one).
Regards.

Edited by macnuts, 10 August 2012 - 07:06.


Re: OpenPLi 3.0: new alpha experimental images! #317 MiLo

  • PLi® Core member
  • 14,055 posts

+298
Excellent

Posted 10 August 2012 - 11:23

I am still wonder how a nfs mount can be done when there are missing the directory "hdd" inside the /media . The /hdd symlink are pointed to /media/hdd . Adding a hdd directory in /media will be deleted after reboot. Is there anybody that know how this can be done ? I know i can of course make a script that start after every reboot " mkdir /media/hdd" ,but this is a workaround and i assume this is not the way it should be done


Any directory in /etc/fstab is automatically created at boot. So if you use fstab to mount your NFS share, no "scripts" are needed.

If you use the enigma2 mounting functionality, the /media/hdd directory (or whatever mountpoint you chose) will also be created automatically.

Which method are you using to mount your nfs share?
Real musicians never die - they just decompose

Re: OpenPLi 3.0: new alpha experimental images! #318 exsat

  • Member
  • 21 posts

0
Neutral

Posted 12 August 2012 - 12:42

ok,,thank you,,i did not know that the fstab would create a directory.

Re: OpenPLi 3.0: new alpha experimental images! #319 MiLo

  • PLi® Core member
  • 14,055 posts

+298
Excellent

Posted 12 August 2012 - 14:04

On normal posix systems, fstab wouldn't create directories, it's a special OpenPLi feature that it does so.

The "/media" directory is in RAM, not on the flash, for a few good reasons:
- In case the mount fails, you may end up with the box recording to flash memory, which in a sort time will fill it up and crash the system. If something like this happens now, it will fill only 64k RAM and them harmlessly stop.
- It's a waste to write to flash memory (twice) just to have a mount point that is just an empty directory.
- It makes it possible for the mount scripts to assume that any directory in that location is really a mount point, and use it for "housekeeping".
Real musicians never die - they just decompose

Re: OpenPLi 3.0: new alpha experimental images! #320 veskop

  • Senior Member
  • 364 posts

+2
Neutral

Posted 14 August 2012 - 08:05

No updates from 2-3 days???

Gigablue Quad +250GB HDD ~ Xtrend ET5000 ~ Triax110 Black Multifeed 36E/28E/23E ~ Total TV88 Multifeed 19E/16E/13E/9-7E ~ EMP Centauri 9/1 DiSEqC ~ Panasonic L42G20



1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users