Thank you so much for the details. Every little bit adds confidence. Just to be absolutely clear, folks here are successfully running > 1TB partitions on S3 OLEDs using stock 11.0k/m kernels right? I know sometimes when I mod boxes, I can lose track of what I'm running or whether I did something first with a hacked kernel then went back to stock. Regarding JMFS dealing with the Apple Free partition created at the end of drive by MFS Live, would it have been possible to delete that partition using a partition editor (pdisk?) before running JMFS? I know it's not something you'll go back and try now, but perhaps something to keep in mind if it ever comes up again with someone else's upgrade. Regarding the 1TiB partition limit in the kernel, the following led me to that idea (I was wrong about jamie's patch being signed to unsigned int, it was 32-bit int to 64-bit int) From Spike http://www.mfslive.org/forums/viewtopic.php?f=11&t=257&start=45#p4818 From Spike http://mfslive.org/forums/viewtopic.php?p=4636#p4636 From Jamie I was also led to the impression that originally the latest versions (at the time) of MFSLive and WinMFS mfsadd would blindly expand to the end of a 2TB drive. Coupled with the 1TiB partition limit in the linux kernel, this made MFSLive incompatible with 2TB drives (unless you started with a 1TB factory image). I think Spike added that WinMFS question about whether to break the 1TB partition limit to stop the blindly expand behavior so people could use 1.5/2TB drives with kernels that didn't support > 1TB. So I *think* (but could be mistaken) MFSLive mfsadd would do the same expansion to end of drive that WinMFS is doing with 2TB drives, it just wouldn't ask you the question. I can't really verify at the moment since I don't have a 2TB drive (yet). Thank you for being patient with me, I'm slowly figuring things out and the cobwebs are clearing from long-term neglect.