Opened 14 years ago
Closed 12 years ago
#7399 closed bug (duplicate)
Not able to mount NTFS volume
Reported by: | Disreali | Owned by: | 3dEyes |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | File Systems/NTFS | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | #8332 | Blocking: | |
Platform: | All |
Description
Experienced on hrev41022-4h-nightly.
After installing I noticed that my WinXP NTFS volume was no longer listed in the Mount sub-menu. DriveSetup also does not list the NTFS volume's information anymore.
I have no problems with mounting the same NTFS volume on a hrev40968-4h-alpha that I have installed on a separate partition on the same system.
Attachments (2)
Change History (7)
by , 14 years ago
Attachment: | r41022_DriveSetup_no_longer_lists_ntfs_volume_info.png added |
---|
follow-up: 2 comment:1 by , 14 years ago
comment:2 by , 14 years ago
There was no hibernating on xp. I have disabled hibernation on that WinXP install.
I just built and installed a hrev41076 gcc4hybrid alpha image and was able to mount and see in DriveSetup the XP volume. Could it be that the hrev41022 was a nightly? Is there something missing in the nightly images that would account for this?
Attaching syslog from the 41022-nightly install.
by , 14 years ago
Attachment: | syslog_r41022-4h-nightly.txt added |
---|
comment:3 by , 14 years ago
Component: | - General → File Systems/NTFS |
---|---|
Owner: | changed from | to
This looks like a dup of #7019.
comment:4 by , 14 years ago
comment:5 by , 12 years ago
Blocked By: | 8332 added |
---|---|
Resolution: | → duplicate |
Status: | new → closed |
It would be nice to have a syslog as always.
The code which identifies the partition for ntfs isn't verbose enough to explain why it's not recognized anyway. Do you know whether the OS was hibernated on this partition? That's a common reason for not being able to identify, though the code should handle this better (ie identify but not allow mount) to bring a message to the user.