Ubuntu 11.10 64bit

[Samir]

Pozdrav .... Imam problem ne mogu instalirati ubuntu 11.10 64 bit unutar windows 7 64 bit, . Kad rest comp nesto mi izadje ntfs nije pronadjeno a ubuntu 32 bit instaliram bez problema .Pa ako netko zna sta bi mogao biti problem nek napise . Hvala puno

[max360se]

Mislis instalirati kao aplikaciju ili kao virtualnu masinu?

Nesmijes nasilu resetirati dok se Windowsi gase jer se NTFS particija ne zatvori kako treba i onda joj Linux nezeli pristupiri ili nemoze kako kad, jer je moze zeznuti.

[Lutherus]

Kao aplikaciju. Radi preko wubija.

[max360se]

ajde ja cu sad probat isto pa javim.

[Samir]

Mislis instalirati kao aplikaciju ili kao virtualnu masinu?

Nesmijes nasilu resetirati dok se Windowsi gase jer se NTFS particija ne zatvori kako treba i onda joj Linux nezeli pristupiri ili nemoze kako kad, jer je moze zeznuti.

Kao virtualnu preko wubija i nista ne diram samo odem na ono sto ponudi da odma rest. i sam se rest i izaberem ubuntu i onda mi izadje nfts nije pronadjen eroor 025

[Samir]

ajde ja cu sad probat isto pa javim.

ajd pa javi

[max360se]

Nista od toga, imam LiLo instaliran i to smeta wubiju.

[Lutherus]

Ne to nije virtualna. Virtualna je da radiš instalaciju unutar virtualboxa.

Evo kaj kaže Ubuntu wiki za ovaj problem

Corrupted NTFS filesystem

All reported cases of damaged filesystems were from users who hard rebooted (pulling the plug).

When you hard reboot, there is always a chance of damaging your filesystem, whether you use Wubi or not.

New users, unfamiliar with a new operating system, tend to hard reboot more often than necessary when they encounter problems.

If Wubi becomes damaged as a result of a hard reboot, there is a chance that Windows may also become corrupted since the principle behind Wubi is that of a virtual disk within the host operating system.

Sometimes people blame Wubi for these issues even though a quick Google search will reveal numerous cases of NTFS corruption without users having ever installed Wubi or ntfs-3g (and a full software industry lurking on that…).

If the NTFS filesystem becomes corrupted you need to run chkdsk /r from the Windows Recovery Console on the Windows CD (or other recovery CD available on the web) or in the msdos console (if you can boot into Windows).

At the moment there is no fsck for NTFS on the Linux side, otherwise it would be possible to fix these errors automatically within Linux itself, without having to rely on Windows tools.

The best advice is to simply avoid hard rebooting, whatever OS you may be using.

[max360se]

shvatio sam ja da nije virtualka i u prvom postu sam objasnio sto mu je sa NTFS-om. Mora prvo restarta Windowse normalno, pustit da prodju checkiranja diska ako se ponude i onda pokusati sa instalaciju.
Ja imam Linux Loader u MBR-u jer imam Slackware, pa wubi nemoze nac Windows boot.

[Samir]

Ne to nije virtualna. Virtualna je da radiš instalaciju unutar virtualboxa.

Evo kaj kaže Ubuntu wiki za ovaj problem

Corrupted NTFS filesystem

All reported cases of damaged filesystems were from users who hard rebooted (pulling the plug).

When you hard reboot, there is always a chance of damaging your filesystem, whether you use Wubi or not.

New users, unfamiliar with a new operating system, tend to hard reboot more often than necessary when they encounter problems.

If Wubi becomes damaged as a result of a hard reboot, there is a chance that Windows may also become corrupted since the principle behind Wubi is that of a virtual disk within the host operating system.

Sometimes people blame Wubi for these issues even though a quick Google search will reveal numerous cases of NTFS corruption without users having ever installed Wubi or ntfs-3g (and a full software industry lurking on that…).

If the NTFS filesystem becomes corrupted you need to run chkdsk /r from the Windows Recovery Console on the Windows CD (or other recovery CD available on the web) or in the msdos console (if you can boot into Windows).

At the moment there is no fsck for NTFS on the Linux side, otherwise it would be possible to fix these errors automatically within Linux itself, without having to rely on Windows tools.

The best advice is to simply avoid hard rebooting, whatever OS you may be using.

ne znam ajd sad cu pokusati ponovo pa valjda bude moglo . pa javim da li sam mogao instalirati Hvala na pomoci