On 08/05/2011 09:39 PM, Cristian Rodríguez wrote:
El 05/08/11 09:32, David C. Rankin escribió:
I don't know. Maybe the ntfs-3g mount type includes a default 'ro'
No, The old ntfs driver did that, ntfs-3g behaves like a regular filesystem where defaults to rw.
Could failing to explicitly mount the ntfs-3g share ro cause changes that impact the disk signature of the vista/w7 BCD bootmgr that render windows unable to boot?
If it overwrites the MBR... yes... but I dont see how in your situation..
Thanks Christian, I think it is just something in the way Vista recognizes the 640G Western Digital drive in my laptop. I have another 320G drive for the same box and I've experimented with dual-boot on that drive without the "required device inaccessible" I get on the Western Digital drive. (possible Msahci related??) Grub always boots windows on the 640G drive. It is just the windows boot that gets 1/2 through and spontaneously reboots itself due to issues that at the root cause look like drive signature differences between windows boots. I think you are correct in your assessment that as long as the MBR isn't touched, suse shouldn't do anything to the partition itself that would cause the issue. However, one clue I get on the win side is that the last driver/module loaded before the reboot is a crcdisk app that I assume calculates the disk signature based on (god knows what). It is this app that got me thinking about the lack of mounting the partition 'ro' with ntfs-3g. Even though it shouldn't, it the partitions isn't mounted 'ro' and some temporary file gets dropped in a folder on the vista partition, I could see how that could change what is reported as the disk signature by the vista crcdisk module. Thanks again! -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org