Update on V4 progression

[thomasfonville]

Hello, as you may already know firmware V4 has been released.
I never expericenced any trouble before updating the version. But this time I did.
While copying the data from the usb stick the process stops.
The mede8er doesn't even want to start up normally. I cannot startup the previous firmware version which was the beta version of 4 released 6th of december.
Any suggestions what to do next...
Has anyone experienced the same problem?
Thank you for any feed back.

[Maasbommel]

Hello, as you may already know firmware V4 has been released.
I never expericenced any trouble before updating the version. But this time I did.
While copying the data from the usb stick the process stops.
The mede8er doesn't even want to start up normally. I cannot startup the previous firmware version which was the beta version of 4 released 6th of december.
Any suggestions what to do next...
Has anyone experienced the same problem?
Thank you for any feed back.

Probably one of the root causes mentioned here:
http://www.mede8erforum.com/index.php/topic,4277.msg29547.html#msg29547

And several more topics if you read around. First install the 17L patch to update your bootloader.
After that install V4 again.

[Roof]

Thanks for this stable version! Updating was a breeze, videowall works perfect without creating 'extra folders' ,but most importantly I can watch a movie now without jumping off the couch everytime the SPDIF passthrough failed and created some LOUD static noise on my surround system.

Now all I need is YAMJ-to-Mede8er to run on my Mac...

[panter92]

Now all I need is YAMJ-to-Mede8er to run on my Mac...

Why don't you try this one
http://www.mpcclub.com/forum/showthread.php?t=24436

[siggwiz]

V4 is great. Would like to know the best way to upgrade from firmware 2.1 to V4. Should I update the Bootloader17 first before updating to V4 or can I go directly to update V4. Thanks.

[thomasfonville]

Thank you for the tip maasbommel i'll give it a try

[Chrissieboy123]

Hello, med owners well i am impressed i upgraded both my med500x and 400x with ease and no probs. i just downloaded each seperate update and installed taking a couple of mins. cheers guys, i shall have a play 2niote to see what its like

[Bigbot3]

I have installed V4 final and it works great. thank you.
but i have noticed a strange thing, I now have a local disc C and an extra disk E when i choose local HDD
 from the media library. Disc E is labeled ext3 and on this disk is a directory lost and+found.
The installed disc is a Samsung Ecogreen 2 TB HD204UI .
At first i thought that the formatting of the disk was wrong because when i installed this disc in the mede8er firmware V4 Beta December was installed and i used this firmware to format the disc. So I copied 1 TB of movies from the disk and put them in a safe place and reformatted the internal disc with the V4 final firmware. At first it looked good , there was only a local disc C who was empty, then i copied the 1 TB of movies back on it from the safe place,5 hrs of copying data via sata, (i had the drive internal connected to my windows xp system).
After that i connected the mede8er back to the tv and  there was the ext3 disc back. Now i'am puzzled 
It looks that the internal Ext3 partition is not hidden but exposed in the media library. I also noticed it has doubled in size compared to the V4 beta. (533mb).
Did I do anything wrong? Or is this a bug / "undocumented feature" ?

[the-osiris]

hi Bigbot3,
This EXT3 is still under investigation. Other user also reporting this issue http://www.mede8erforum.com/index.php/topic,4367.0.html.
Could you specify firmware 4beta december is ? is it 4beta5 or else ?

[Bigbot3]

hi the-osiris,

the firmware that was inside when first formatting the Samsung HD204UI  was V4 beta5, the public beta.
I have read the thread you gave a link of and it looks like the same problem.
I don't know if it is happening because I had the drive out of the mede8er or because it is filled half up now.
Another thing is that this drive is using advanced format 4k sectors so after formatting in the mede8er i have recreated the ntfs partition with a Gparted live cd to get it aligned on a 1mb boundary. You need a 4k aligned partition to get the drive up to full speed, maybe that that is causing the problem.
It looks like the mede8er is treating the drive as an "foreign" drive, and not as its own internal drive with the linux swap and ext3 partitions.
How does the mede8er recognises its internal drive? If he does that as he recognise the gap before and the start of the main ntfs partition as a "trademark" of his internal formatting beeing done, than this check failes after realigning the partition.
With the V4 beta5 firmware i also realigned the main ntfs partition and this was then no problem.
I will investigate further with a smaller drive inside, moving the ntfs partition around to see if the ext3 partition "reappears" ie. the mede8er is not recognising its own internal drive.

greetz,
B

[Bigbot3]

I have tried to recreate the error with a much smaller disc (a 160 Gb WD drive from a notebook), but i had no luck.
First i put the drive inside the mede8er and formatted it
then i realigned the ntfs partition to a 1mb boundary with GParted.
Further i put it full with movies, and after that still it was correctly recognised as the internal harddisk HDD and not C: and E:.
So the only difference with the other disk is its size (2TB).

There must be a difference in disk handling between V4Beta5 and V4Final. but it is not the alignment of the NTFS partition.

[Maasbommel]

Hi Bigbot3,

I suspect some issue with the partition tables, maybe caused by the reallignment program.
As you say you have some backup made of your data, I suggest to try the procedure here:
http://www.mede8erforum.com/index.php/topic,633.msg3633.html#msg3633

So remove all the paritions that are on the disk by using the dd method.
Then after that do a reformat using mede8er format menu.
And let us know if you are still seeing that ext3 parition after that.

regards,
Maasbommel

[kuipje]

Hi there,

Since my update from 3.04 to 4 final I get a hazy layer. It appears only when I select 1080p 60.
With version 3.04 i had no problems selecting 1080P.

To uprade i used "MED500X_V4_NO_HD_AUDIO_25Jan2011"
My tv a samsung 37lea552 full HD.

{Dutch}
Sinds mijn update van versie 3.04 naar  V4 final krijg ik een wazige laag als ik 1080P 60 selecteer. Hiervoor had ik geen problemenals ik 1080P 60 selecteerde.

Voorstellen voor verbetering van de engelse tekst zijn altijd welkom.

[thomasfonville]

Thanks to the update information on the V4 release I was able to update the mede8er. One thing I did notice in the new version is that it can not connect wireless to a wep encrypted network. none encrypted networks and WPA networks do not have this problem. Maybe it can be something to look in to.

Thank you mede8erforum administrator for all the effort done to fix the update problem.

[Bigbot3]

Hi Bigbot3,

I suspect some issue with the partition tables, maybe caused by the reallignment program.
As you say you have some backup made of your data, I suggest to try the procedure here:
http://www.mede8erforum.com/index.php/topic,633.msg3633.html#msg3633

So remove all the paritions that are on the disk by using the dd method.
Then after that do a reformat using mede8er format menu.
And let us know if you are still seeing that ext3 parition after that.

regards,
Maasbommel

Hello Maasbommel,

Thanks for your response, When i first noticed the extra "ext3" partition being exposed in the local disc selection,
i thought something was wrong with the formatting of the V4Beta5 firmware who was on the unit when i placed this disc
so i reformatted  with firmware v4 final in place, at first everything was ok (even after alignment!) there was only an local HDD with nothing on it, but after i copied 1 TB of movies back onto the unit (5 hrs of work!) i saw the ext3 partition reappear.
Last night i put v4b5 back on the unit and everything was back to normal the internal drive was properly recognised again as HDD. and in the system info screen it gave also the correct information about the disc.
Now i have v4final put back in and its wrong again, so there must be a difference in recognising the internal HDD between
v4beta5 an v4 final.

i have made a connection with telnet to the unit and this is the fdisk information about the drive:

/ # fdisk -l

Mede8er 2 TB Samsung HD204UI  disc status: recognised as HDD C:(Mede8er) and E: (ext3)
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      243089  1952611328    7  HPFS/NTFS
/dev/sda2          243090      243109      160650   82  Linux swap
/dev/sda3          243110      243177      546210   83  Linux
/ #

/ # fdisk -l -u

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

   Device Boot             Start                   End          Blocks     Id  System
/dev/sda1                    2048  3905224703  1952611328    7  HPFS/NTFS
/dev/sda2      3905224785  3905546084           160650   82  Linux swap
/dev/sda3      3905546085  3906638504           546210   83  Linux
/ #

I will try the reformat procedure later I will let you know the results.