>> Really? I thought his old drive was SATA (hence his worries that his
>> new drive would need new drivers).
> No, the old original drive is PCIe 3.0 x4 AHCI. The new one is PCIe 3.0
> x4 NVMe.
If we can't get the two drives connected to the same system at the same
time, I guess I'd use a third
On 17/11/2018 16:50, Stefan Monnier wrote:
Really? I thought his old drive was SATA (hence his worries that his
new drive would need new drivers).
No, the old original drive is PCIe 3.0 x4 AHCI. The new one is PCIe 3.0
x4 NVMe.
>> 1- take out the old SSD and put it into an external reader that you can
>>connect via USB
> I think that's going to be difficult-to-expensive: it's not a
> SATA SSD, it connects through NVMe PCIe.
Really? I thought his old drive was SATA (hence his worries that his
new drive would need new
On 17 Nov 2018, at 16:06, Stefan Monnier wrote:
> Didn't use LVM? Too bad: that means there's a risk your new dirve and
> partitions will get new identifiers so your fstab may need to be adjusted.
Ehm.. no.. I didn’t!
> macOS doesn't touch EFI, AFAIK, so don't expect the Time Machine to
> touch
Stefan Monnier wrote:
> 1- take out the old SSD and put it into an external reader that you can
>connect via USB
I think that's going to be difficult-to-expensive: it's not a
SATA SSD, it connects through NVMe PCIe.
There are external boxes that can support PCIe via Thunderbolt,
but the chea
> 4 23.2GB 31.2GB 8000MB linux-swap(v1) swap
> 5 31.4GB 121GB 89.8GB ext4linux
Didn't use LVM? Too bad: that means there's a risk your new dirve and
partitions will get new identifiers so your fstab may need to be adjusted.
> Now, here is what I would perform:
>
>
On 16/11/2018 14:46, Stefan Monnier wrote:
I would expect the clone to work just fine. I'd expect your initrd
contains drivers for both SATA and NVMe anyway.
OK. Now that I know that initrd does contain NVMe drivers, I would ask
whether my strategy for cloning is sensible.
Firstly, here's m
Stefan Monnier wrote:
>> I've got 8 of them:
>
> So you should be all set.
It is worth trying, though Appli plays always dirty, but chances are good.
> I've got 8 of them:
So you should be all set.
Stefan
On 16/11/2018 14:46, Stefan Monnier wrote:
I would expect the clone to work just fine. I'd expect your initrd
contains drivers for both SATA and NVMe anyway.
But it's easy to check:
zcat /boot/initrd.img- | cpio -vt | grep nvm
will show you the relevant files in the your initrd.
You shou
> However my main concern is with the linux partition. How can I migrate it?
> If I simply clone the linux partition from the old drive to the new drive,
> I fear something would go wrong, as the new drive is different and would
> require different drivers, missing in the original linux system.
I
Another issue I have is--how to migrate my debian system from the old
original SSD to the new larger SSD?
As for macOS [1], it should be easy. There is a macOS application called
Time Machine that allows to backup macOS from the old SSD and to restore
it to the new SSD. This would work with a
On 15/11/2018 21:48, deloptes wrote:
Check first if someone has used it on your type
of hardware and what is the feedback - I assume you are not the first. NVMe
is working fine - debian provide the kernel which provides the support and
I have seen M.2 working just fine
Late 2016 - Mid 2017 MacB
solitone wrote:
> The thing is the form factor, which unfortunately is proprietary [1].
> The connector resembles the standard M.2, but in fact is different.
OK this is a valid argument. Check first if someone has used it on your type
of hardware and what is the feedback - I assume you are not th
On 15/11/2018 21:01, deloptes wrote:
I also do not think you have to stick to this specific
drive (JetDrive 850) - perhaps macOS certified, but from linux perspective
it would make no difference.
The thing is the form factor, which unfortunately is proprietary [1].
The connector resembles the
solitone wrote:
> What do you think in terms of compatibility with debian? What worries me
> is that JetDrive 850 requires macOS version 10.13 or later, and I wonder
> whether debian supports it. Is this only a matter of NVMe (macOS
> supports NVMe starting from version 10.13; linux since kernel v
Hi, I've got a compatibility question regarding SSDs.
I run debian 9.6 on a MacBookPro12,1 (Early 2015, 13"). I'm thinking of
upgrading the stock 128 GB SSD [1]. Specifically, I'm considering the
Trascend JetDrive 850 [2].
The original SSD uses a PCIe 3.0 x4 interface and the AHCI protocol.
17 matches
Mail list logo
