Is this true: "Although it's not a recommended situation, you don't need to have the same disklayout on the secondary replica compared to the primary replica." For example: My primary relica is a full-blown multi-core server, connected to a multiple LUN SAN with datafiles spreaded over several driveletters. My secondary replica has almost the same CPU power, but has a local storage cabinet with different a drive configuration.
[Found this answer] 
http://www.tech-coffee.net/alwayson-availability-group-design/ > Note for Databases/Logs path on AAG: > > If you use the default instance path (which contains the instance name) for Databases and Logs, the paths on all the nodes participating to the AAG are different. This has an impact on AlwaysOn AG. > > TechNet: > > If the file path (including the drive letter) of a secondary database differs from the path the corresponding primary database, the following restrictions apply: > * New Availability Group Wizard/Add Database to Availability Group Wizard: The Full option is not supported (on the “Select Initial Data Synchronization” Page). > * RESTORE WITH MOVE: To create the secondary databases, the database files must be RESTORED WITH MOVE on each instance of SQL Server that hosts a secondary replica. > * Impact on add-file operations: A later add-file operation on the primary replica might fail on the secondary databases. This failure could cause the secondary databases to be suspended. This, in turn, causes the secondary replicas to enter the NOT SYNCHRONIZING state. :