-
Important Announcement for the TrueNAS Community.
The TrueNAS Community has now been moved. This forum has become READ-ONLY for historical purposes. Please feel free to join us on the new TrueNAS Community Forums
- Status
G
gcooper
Guest
The issue's a bit deeper than just fixing the "broken FUSE package" [installation issues].
1. I had to mount the NTFS volume with --force because it wasn't cleanly unmounted. This got me past the labeling issues.
2. Mounting doesn't work because of the fact that how we interact with fuse is broken, in particular:
a. The issue noted in 1. applies to mounting.
b. We don't kill mount_ntfs-fuse before unmounting the volume (according to the error messages).
3. ntfsfix doesn't work as advertised.
Does all this work on FreeNAS 0.7 and/or FreeNAS 8.0, and if so, to what degree (readonly, readwrite, etc)?
G
gcooper
Guest
Could you try manually backing out the debugger changes in FREENAS.amd64 to see if things change?
When I tested it for that ticket I posted, I did a freshly formatted NTFS 1G flash drive, full format, not quick, and it still complained about it not being clean. I was also careful to tell windows to 'safely remove' it. The labeling issue also happens with FAT/FAT32.
I can't answer for .7, never used it. It has never properly worked in 8.x that I'm aware of, I've tried every version. I posted a workaround in the FAQ, but when I just tried to verify the workaround again just recently, it didn't work. The workaround involved copying /usr/local/modules/fuse.ko to /boot/kernel and adding it to loader.conf and then I was able to mount from the GUI without any problems. That didn't work when I just tried it recently, so I'm not sure what I did differently, unless it was unloading ntfs.ko first???
I also used to be able to mount NTFS from the command line using ntfs-3g /dev/xx /mntpoint, but that doesn't work anymore either. I think it complains about the volume not being clean etc. also.
I know an awful lot of people would really like to see this work. Personally I don't really need it, but it's useful to import your data when you're trying to migrate it to your NAS, or occasionally copying something off a thumb drive. It would definitely help win over some new or old users! ;-)
Milhouse
Guru
- Joined
- Jun 1, 2011
- Messages
- 564
Other than having to kldload fuse.ko, I had no problem mounting NTFS drives and accessing their content under FreeNAS 0.7.x
AndroidCat
Cadet
- Joined
- Nov 29, 2011
- Messages
- 8
gcooper->
Appreciate all the work!
Will this small UPS script change make it into 8.0.3?
It was discussed in
http://forums.freenas.org/showthread.php?3086-Network-UPS-Support-information-changes
and Milhouse and William provided a patch then.
The patch makes FN recognise between "UPS reaches low battery" and "UPS goes on battery".
Thanks.
Appreciate all the work!
Will this small UPS script change make it into 8.0.3?
It was discussed in
http://forums.freenas.org/showthread.php?3086-Network-UPS-Support-information-changes
and Milhouse and William provided a patch then.
The patch makes FN recognise between "UPS reaches low battery" and "UPS goes on battery".
Thanks.
G
gcooper
Guest
I'll fish through the changes for ix-ups and pick out the items that should be included.
Once I can determine what the issue is for Accurus's issue (b/c I'm sure he's not the only one that will run into it in the field), I'll roll an official BETA3 image.
It looks like with the new BIOS version that I don't have any issues with version v9200. However, I do get a syntax error that will not allow the system to fully boot. States that there is a syntax error in loading python and django. But I think it folks update their BIOS that the error I was getting atleast with v 9200 will be gone. Thanks for troubleshooting with me gcooper.
G
gcooper
Guest
I just doublechecked, and yes... everything's fixed in ix-ups.
G
gcooper
Guest
Awesome -- thanks for the clarification. I'll be sure to note that in the release notes that folks with this motherboard need to update their BIOS prior to running the upgrade, because it looks like this motherboard was popular for FreeNAS based on my searching around the forums/Google.
I'll take a look at the latest trunk image to see what's up, but yeah.. it's still under major construction.
RC1 (I'm going to skip BETA3 like I originally planned because I don't need to add any additional code) images should be posted by the end of the day.
Sounds great. The motherboard is a great unit and runs well. This is the first hiccup I have had with it running FreeNAS.
You will also want to make note that using the F7 BIOS update is not an option on this motherboard as apparently the motherboard doesn't respond to F7 to load the BIOS updater. I had to get a bootable USB drive made and throw the BIOS on that way. I spent about 20 minutes trying to get he F7 updater to work and just gave up after searching forums and seeing that this feature while touted by Intel isn't working as well as they would claim.
You will also want to make note that using the F7 BIOS update is not an option on this motherboard as apparently the motherboard doesn't respond to F7 to load the BIOS updater. I had to get a bootable USB drive made and throw the BIOS on that way. I spent about 20 minutes trying to get he F7 updater to work and just gave up after searching forums and seeing that this feature while touted by Intel isn't working as well as they would claim.
G
gcooper
Guest
Documented that item in the release notes. A user asked about fixing an autosnap bug, so I did that, and I'm working on backporting one final fix for the periodic zfs scrub issue where it runs every 30 days instead of every 4 weeks on the weekend [it's something that some folks have identified as an issue that have deployed FreeNAS/TrueNAS in datacenters ;)..]. Once that's in, I'm calling it RC1 and running the final build with all of the changes, so it might be done later on tonight (2am~3am PST).
- Joined
- May 28, 2011
- Messages
- 10,996
Will you also be building a multimedia version after that? I don't mind building my own, just asking really for the other folks out there. Dang, 2-3am, I'll be sound asleep but I'll be up again at 5am getting ready for my day job. You work way too late.
G
gcooper
Guest
Afraid not. Again, that's only trunk ;)..
No rest for the wicked my friend -- besides, builds take 4 hours, so if I get everything queued up and automated properly, then I can be asleep by 11 ;).
G
gcooper
Guest
1. Automation didn't work because of a stupid stat(2) FreeBSD bug *grumbles*.
2. I forgot to upgrade nut (was going to do that last week but then I forgot).
2. I forgot to upgrade nut (was going to do that last week but then I forgot).
G
gcooper
Guest
And yet another late breaking development: r9244/r9246. My boosting the /var requirement will take away some of the savings I added in this release, but it'll also increase stability and increase uptimes.
- Joined
- May 28, 2011
- Messages
- 10,996
I'm building it right now with those recent changes you mentioned. Hopefully it will work nicely. I'll keep tabs on this thread to see if something else changes but I wanted to give all these changes a go.
G
gcooper
Guest
Builds are already done and being uploaded to SF as I type..
G
gcooper
Guest
Glad to hear :).
It's a moving target, but my first guess is sometime between January and February. It all depends on how much progress jhixson/william can make on the plugins stuff and how much we can get put together before the end of the year/mid-January.
In the meantime, I've reconsidered not posting 'multimedia' images of 8.0.3 -- I'll be glad to include them as 'sneak previews' of what's to come in 8.2.0 (basically what joeschmuck has been doing for a while now). I'll get things queued, so if RC1 goes to RELEASE without a hitch, then I'll be happy to post the images up before New Year's.
- Status
