albinorex

Has anybody had issues regarding data integrity on 6.0.2? I recently installed via this method over my FreeNAS box which has been working without any issues but wanted to give DSM a shot. I started noticing checksum error notifications inside of DSM that I chalked up to btrfs doing it's thing. It wasn't until I went to use an .iso that it became an issue when it failed a checksum. My immediate thought was that my data migration method might have fudged up the bits somehow so I downloaded the .iso again, hashed the file, copied up to the NAS and hashed the remote copy and noticed that it had been modified. This got me concerned so I fired back up my 5.2 and 6.0.2 VMs and ran the same tests. Both VMs preserved the data without modifcation. I went as far as to wiping a disk group and rebuilding as an ext4 volume when sure enough the issue was still occuring. At this point I think I've isolated to a hardware and/or driver issue. I do not believe it is the drives, as the original volume was on a different disk group. I'm running DSM 6.0.2 on a P5Q Pro LGA 775 w/ Core 2 Duo E8500 and 8GB DDR2. The NIC is an Atheros L1e, not sure off the top of my head what the SATA controller is. I'll be rebuilding to 5.2 tonight to see if I have the same results (at this point I'm not confident in my data, but luckily I've only made minor changes since I transferred from a backup)

For anyone else that stumbles upon this, I figured out the issue. I had my SATA config set to IDE and while booting up it was hanging on loading one of the components (sataii.xxx) or something like that. I read that AHCI mode was required for DSM anyway so I flipped it. After that, voila DSM booted up just fine. Easy enough to do, I just didn't think that would be the fix.

Hi all, First off huge thanks to everyone out there that has committed so much time and effort to this project - fantastic work. I'm currently running FreeNAS and found out about xpenology from a coworker and decided to give it a shot. I demoed 5.2 in a VM and absolutely loved the feature set so started the process of rebuilding my box with it. Unfortunately I've hit a snag, I'm booting off of USB for install and with 5.2-5644.5 or 5.2-5967.1 my box pulls a self-assigned 169.x address which leads me to believe the NIC driver didn't load up properly. I've recycled some old hardware into my NAS box, and it looks like the P5Q Pro runs an Atheros L1e NIC which is on the comparability list. Anybody else running on this hardware and/or had any issues with this before? One other odd thing is that my USB keyboard goes dark after booted up to xpenology (which worked seconds before when picking the install/upgrade option). Thanks in advance for any help.