Re: [ros-dev] ROS Livecd issue

[Mikhail Y. Zvyozdochkin]

Felipe Villarroel wrote:
> On 1/5/07, Muguntharaj Subramanian [e-mail] wrote:
> > ...
> > partition signature != 55AA
> > ...
>
> You have a corrupted MBR or partition table. Reinstall ReactOS and do
> proper partitioning.

Hm, Hm... It's not so simply.
I got same error with _fresh-installed_ ReactOS.

WBR, DarkHobbit

[Felipe Villarroel]

Yep, i knew that they were some problems with ReactOS partitioning
code, although i haven't had problems with it (i always install
ReactOS over a previously partitioned disk :P). Maybe its fixed by now
(latest SVN).

Best regards,
Logan_V8

On 1/7/07, Mikhail Y. Zvyozdochkin [e-mail] wrote:
> Felipe Villarroel wrote:
> > On 1/5/07, Muguntharaj Subramanian [e-mail] wrote:
> > > ...
> > > partition signature != 55AA
> > > ...
> >
> > You have a corrupted MBR or partition table. Reinstall ReactOS and do
> > proper partitioning.
>
> Hm, Hm... It's not so simply.
> I got same error with _fresh-installed_ ReactOS.
>
> WBR, DarkHobbit
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev

[Muguntharaj Subramanian]

Hi All,
I checked out the source again yesterday and built a fresh iso (bootcd). And
again i find the same issue i.e "partition signature != 55AA" error while
trying out the created iso with VMware.

Has anybody else tried the same way? My objective is to compile the reactos
iso from source first. Then plan to add applications and try to fix some
bugs in my free time. For that i feel its better  to use VMware instead of
running fresh install (also i dont have spare machine to do fresh
installation).

Is the current builds working in QEMU?

Regards,
Mugunth

On 1/8/07, Mikhail Y. Zvyozdochkin [e-mail] wrote:
> Felipe Villarroel wrote:
> > On 1/5/07, Muguntharaj Subramanian [e-mail] wrote:
> > > ...
> > > partition signature != 55AA
> > > ...
> >
> > You have a corrupted MBR or partition table. Reinstall ReactOS and do
> > proper partitioning.
>
> Hm, Hm... It's not so simply.
> I got same error with _fresh-installed_ ReactOS.
>
> WBR, DarkHobbit
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev
-- 

http://mugunth.blogspot.com
http://thamizha.com
http://tamilblogs.com


-- 
http://webspace2host.com
"Your friendly hosting provider"

[Muguntharaj Subramanian]

Some  more info on this...
Checked the vmware logs. Following are the log entries. Hope this might
offer some help to those debugging this issue. Thanks.

Jan 09 14:34:38: vcpu-0| SVGA: Registering MemSpace at
0xf0000000(0xf0000000) and 0xec000000(0xec000000)
Jan 09 14:34:38: vcpu-0| SVGA: Unregistering MemSpace at
0xf0000000(0xf0000000) and 0xec000000(0xec000000)
Jan 09 14:34:38: vcpu-0| SVGA: Registering IOSpace at 0x1400 (0x0)
Jan 09 14:34:38: vcpu-0| SVGA: Registering MemSpace at
0xf0000000(0xf0000000) and 0xec000000(0xec000000)
Jan 09 14:34:39: mks| VNCENCODE 1 encoding mode change:
(640x480x16depth,16bpp)
Jan 09 14:34:40: vcpu-0| VIDE: Curr CHS info cyls: 17475 heads: 15 sects: 63
lba_cap: 16777216
Jan 09 14:34:42: vcpu-0| BIOS-UUID is 56 4d c8 6f 74 47 6f fb-bf fd 87 d9 7f
61 2d 9f
Jan 09 14:34:42: vcpu-0| DISKUTIL: ide0:0 : toolsVersion = 0
Jan 09 14:34:42: vcpu-0| DISKUTIL: Offline toolsVersion = 0
Jan 09 14:34:42: mks| VNCENCODE 1 encoding mode change:
(720x400x16depth,16bpp)
Jan 09 14:44:38: vmx| TOOLS setting the tools version to '0'
Jan 09 14:44:38: vmx| VmdbDbCheckDataType failed for
path=/vm/#feba309633015371/vmx/guestTools/versionStatus/ and
value=notAvailable: (-11) Type mismatch
Jan 09 14:44:38: vmx| Vmdb_Set: Failed to set
/vm/#feba309633015371/vmx/guestTools/versionStatus/ to notAvailable (Type
mismatch)
Jan 09 14:44:38: vmx| VMXVmdb_SetToolsVersionState failed. ret = Type
mismatch
Jan 09 16:21:38: mks| MKS set guest selection request with invalid state 2
Jan 09 16:21:49: vcpu-0| CPU reset: soft
Jan 09 16:21:50: vcpu-0| SVGA: Unregistering IOSpace at 0x1400 (0x1400)
Jan 09 16:21:50: vcpu-0| SVGA: Unregistering MemSpace at
0xf0000000(0xf0000000) and 0xec000000(0xec000000)
Jan 09 16:21:50: vcpu-0| SVGA: Registering MemSpace at
0xf0000000(0xf0000000) and 0xe8000000(0xec000000)
Jan 09 16:21:50: vcpu-0| SVGA: Unregistering MemSpace at
0xf0000000(0xf0000000) and 0xe8000000(0xe8000000)
Jan 09 16:21:50: vcpu-0| SVGA: Registering MemSpace at
0xf0000000(0xf0000000) and 0xe8000000(0xe8000000)
Jan 09 16:21:50: vcpu-0| SVGA: Unregistering MemSpace at
0xf0000000(0xf0000000) and 0xe8000000(0xe8000000)
Jan 09 16:21:50: vcpu-0| SVGA: Registering IOSpace at 0x1400 (0x0)
Jan 09 16:21:50: vcpu-0| SVGA: Registering MemSpace at
0xf0000000(0xf0000000) and 0xe8000000(0xe8000000)
Jan 09 16:21:50: mks| VNCENCODE 1 encoding mode change:
(640x480x16depth,16bpp)
Jan 09 16:21:51: mks| SOCKET 1 new update req with non-empty pending:
logical error on server/client?
Jan 09 16:21:51: vcpu-0| VIDE: Curr CHS info cyls: 17475 heads: 15 sects: 63
lba_cap: 16777216
Jan 09 16:21:53: vcpu-0| BIOS-UUID is 56 4d c8 6f 74 47 6f fb-bf fd 87 d9 7f
61 2d 9f
Jan 09 16:21:53: vcpu-0| DISKUTIL: ide0:0 : toolsVersion = 0
Jan 09 16:21:53: vcpu-0| DISKUTIL: Offline toolsVersion = 0
Jan 09 16:21:53: mks| VNCENCODE 1 encoding mode change:
(720x400x16depth,16bpp

On 1/9/07, Muguntharaj Subramanian [e-mail] wrote:
> Hi All,
> I checked out the source again yesterday and built a fresh iso (bootcd).
> And again i find the same issue i.e "partition signature != 55AA" error
> while trying out the created iso with VMware.
>
> Has anybody else tried the same way? My objective is to compile the
> reactos iso from source first. Then plan to add applications and try to fix
> some bugs in my free time. For that i feel its better  to use VMware instead
> of running fresh install (also i dont have spare machine to do fresh
> installation).
>
> Is the current builds working in QEMU?
>
> Regards,
> Mugunth
>
> On 1/8/07, Mikhail Y. Zvyozdochkin <[e-mail] > wrote:
> > Felipe Villarroel wrote:
> > > On 1/5/07, Muguntharaj Subramanian < [e-mail]> wrote:
> > > > ...
> > > > partition signature != 55AA
> > > > ...
> > >
> > > You have a corrupted MBR or partition table. Reinstall ReactOS and do
> > > proper partitioning.
> >
> > Hm, Hm... It's not so simply.
> > I got same error with _fresh-installed_ ReactOS.
> >
> > WBR, DarkHobbit
> >
> > Ros-dev mailing list
> > [e-mail]
> > http://www.reactos.org/mailman/listinfo/ros-dev
>
> --
>
> http://mugunth.blogspot.com
> http://thamizha.com
> http://tamilblogs.com
>
> --
> http://webspace2host.com
> "Your friendly hosting provider"
-- 

http://mugunth.blogspot.com
http://thamizha.com
http://tamilblogs.com


-- 
http://webspace2host.com
"Your friendly hosting provider"

[Aleksey Bragin]

Hi,
to be 100% safe you should partition the drive using other tool than  
reactos' setup (that should be done once).

As for formatting from ReactOS setup - it works without problems  
(this should be done).

WBR,
Aleksey.

On Jan 9, 2007, at 10:17 AM, Muguntharaj Subramanian wrote:
> Hi All,
> I checked out the source again yesterday and built a fresh iso  
> (bootcd). And again i find the same issue i.e "partition signature ! 
> = 55AA" error while trying out the created iso with VMware.
>
> Has anybody else tried the same way? My objective is to compile the  
> reactos iso from source first. Then plan to add applications and  
> try to fix some bugs in my free time. For that i feel its better   
> to use VMware instead of running fresh install (also i dont have  
> spare machine to do fresh installation).
>
> Is the current builds working in QEMU?
>
> Regards,
> Mugunth
>
> On 1/8/07, Mikhail Y. Zvyozdochkin <[e-mail] > wrote:
> Felipe Villarroel wrote:
> > On 1/5/07, Muguntharaj Subramanian < [e-mail]> wrote:
> > > ...
> > > partition signature != 55AA
> > > ...
> >
> > You have a corrupted MBR or partition table. Reinstall ReactOS and do
> > proper partitioning.
>
> Hm, Hm... It's not so simply.
> I got same error with _fresh-installed_ ReactOS.
>
> WBR, DarkHobbit

[David Hinz]

Hi Mugunth,

It would be nice if you would tell us the revision you built, when you 
want to get help on a ROS problem.
If nobody knows which revision you used, it's quite hard to find the bug.

Greets,

David Hinz

Muguntharaj Subramanian schrieb:
> Hi All,
> I checked out the source again yesterday and built a fresh iso (bootcd). 
> And again i find the same issue i.e "partition signature != 55AA" error 
> while trying out the created iso with VMware.
>
> Has anybody else tried the same way? My objective is to compile the 
> reactos iso from source first. Then plan to add applications and try to 
> fix some bugs in my free time. For that i feel its better  to use VMware 
> instead of running fresh install (also i dont have spare machine to do 
> fresh installation).
>
> Is the current builds working in QEMU?
>
> Regards,
> Mugunth

[Samuel serapion]

Instaling on a vmware scsi disk was broken for a while (afaik) it's now fixed.

I have seen that when creating a new vmware disk reactos setup fails
to properly format the disk and then aborts and attempts to restart,
when you restart vmware now tryies to boot to hard disk. When vmware
reads the disk it bails with "partition signature != 55AA" . To fix te
issue you have to go to the vmware bios setup and change the boot disk
back to cd-rom and re-run reactos setup.  Now you can format the disk
and setup  will (if you're lucky) now install.

On 1/9/07, Muguntharaj Subramanian [e-mail] wrote:
> Hi All,
> I checked out the source again yesterday and built a fresh iso (bootcd). And
> again i find the same issue i.e "partition signature != 55AA" error while
> trying out the created iso with VMware.
>
> Has anybody else tried the same way? My objective is to compile the reactos
> iso from source first. Then plan to add applications and try to fix some
> bugs in my free time. For that i feel its better  to use VMware instead of
> running fresh install (also i dont have spare machine to do fresh
> installation).
>
> Is the current builds working in QEMU?
>
> Regards,
> Mugunth
>
> On 1/8/07, Mikhail Y. Zvyozdochkin <[e-mail] > wrote:
> > Felipe Villarroel wrote:
> > > On 1/5/07, Muguntharaj Subramanian < [e-mail]> wrote:
> > > > ...
> > > > partition signature != 55AA
> > > > ...
> > >
> > > You have a corrupted MBR or partition table. Reinstall ReactOS and do
> > > proper partitioning.
> >
> > Hm, Hm... It's not so simply.
> > I got same error with _fresh-installed_ ReactOS.
> >
> > WBR, DarkHobbit
> >
> > Ros-dev mailing list
> > [e-mail]
> > http://www.reactos.org/mailman/listinfo/ros-dev
>
> --
>
> http://mugunth.blogspot.com
> http://thamizha.com
> http://tamilblogs.com
>
> --
> http://webspace2host.com
> "Your friendly hosting provider"
> _______________________________________________
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev

--
encoded
Samuel Serapión Vega
Computer Engineering, Polytechnic University of Puerto Rico.

[Muguntharaj Subramanian]

Thanks a lot Samuel and all who have responded,
Will try that option.  Meanwhile I tried using QEMU and was able to boot
reactos using QEMU.

Next I will be trying to build in ubuntu and also going thro the documents
in the reactos - hope to start contributing patches soon.

Regards,
Mugunth

On 1/11/07, Samuel serapion [e-mail] wrote:
> Instaling on a vmware scsi disk was broken for a while (afaik) it's now
> fixed.
>
> I have seen that when creating a new vmware disk reactos setup fails
> to properly format the disk and then aborts and attempts to restart,
> when you restart vmware now tryies to boot to hard disk. When vmware
> reads the disk it bails with "partition signature != 55AA" . To fix te
> issue you have to go to the vmware bios setup and change the boot disk
> back to cd-rom and re-run reactos setup.  Now you can format the disk
> and setup  will (if you're lucky) now install.
>
> On 1/9/07, Muguntharaj Subramanian [e-mail] wrote:
> > Hi All,
> > I checked out the source again yesterday and built a fresh iso (bootcd).
>
> And
> > again i find the same issue i.e "partition signature != 55AA" error
>
> while
> > trying out the created iso with VMware.
> >
> > Has anybody else tried the same way? My objective is to compile the
>
> reactos
> > iso from source first. Then plan to add applications and try to fix some
> > bugs in my free time. For that i feel its better  to use VMware instead
>
> of
> > running fresh install (also i dont have spare machine to do fresh
> > installation).
> >
> > Is the current builds working in QEMU?
> >
> > Regards,
> > Mugunth
> >
> > On 1/8/07, Mikhail Y. Zvyozdochkin <[e-mail] > wrote:
> > > Felipe Villarroel wrote:
> > > > On 1/5/07, Muguntharaj Subramanian < [e-mail]> wrote:
> > > > > ...
> > > > > partition signature != 55AA
> > > > > ...
> > > >
> > > > You have a corrupted MBR or partition table. Reinstall ReactOS and do
> > > > proper partitioning.
> > >
> > > Hm, Hm... It's not so simply.
> > > I got same error with _fresh-installed_ ReactOS.
> > >
> > > WBR, DarkHobbit
> > >
> > > Ros-dev mailing list
> > > [e-mail]
> > > http://www.reactos.org/mailman/listinfo/ros-dev
> >
> > --
> >
> > http://mugunth.blogspot.com
> > http://thamizha.com
> > http://tamilblogs.com
> >
> > --
> > http://webspace2host.com
> > "Your friendly hosting provider"
> > _______________________________________________
> > Ros-dev mailing list
> > [e-mail]
> > http://www.reactos.org/mailman/listinfo/ros-dev
>
> --
> encoded
> Samuel Serapión Vega
> Computer Engineering, Polytechnic University of Puerto Rico.
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev
-- 

http://mugunth.blogspot.com
http://thamizha.com
http://tamilblogs.com


-- 
http://webspace2host.com
"Your friendly hosting provider"