1 |
On 08/18/2016 05:06 AM, Peter Humphrey wrote: |
2 |
> On Thursday 18 Aug 2016 15:56:50 Adam Carter wrote: |
3 |
>> On Thu, Aug 18, 2016 at 8:26 AM, Neil Bothwick <neil@××××××××××.uk> wrote: |
4 |
>>> I'm putting together a new desktop using a Samsung SM951 NVMe drive. I |
5 |
>>> booted sysrescd, partitioned the drive and ran |
6 |
>>> |
7 |
>>> mkfs.btrfs /dev/nvme0n1p3 |
8 |
>>> mount /dev/nvme0n1p3 /mnt/custom |
9 |
>>> |
10 |
>>> df -T, mount and findmnt all show this is mounted as a btrfs filesystem, |
11 |
>>> e.g. |
12 |
>>> |
13 |
>>> /dev/nvme0n1p3 on /mnt/custom type btrfs (rw,relatime,ssd,space_cache) |
14 |
>>> |
15 |
>>> I can create files in here but cannot do anything btrfs-y |
16 |
>>> |
17 |
>>> % btrfs filesystem show /mnt/custom |
18 |
>>> ERROR: not a valid btrfs filesystem: /mnt/custom |
19 |
>>> |
20 |
>>> % btrfs subvolume create /mnt/custom/test |
21 |
>>> Create subvolume '/mnt/custom/test' |
22 |
>>> ERROR: cannot create subvolume: Inappropriate ioctl for device |
23 |
>>> |
24 |
>>> Google has been no help at all. |
25 |
>> |
26 |
>> I'm assuming tools are expecting SATA (or SCSI) and need an update or |
27 |
>> alternative for nvm; |
28 |
>> |
29 |
>> # hdparm -i /dev/nvme0n1 |
30 |
>> |
31 |
>> /dev/nvme0n1: |
32 |
>> HDIO_DRIVE_CMD(identify) failed: Inappropriate ioctl for device |
33 |
>> HDIO_GET_IDENTITY failed: Inappropriate ioctl for device |
34 |
>> |
35 |
>> Maybe SCSI emulation could work around it? |
36 |
>> CONFIG_BLK_DEV_NVME_SCSI |
37 |
> |
38 |
> I don't have Neil's e-mail here - another KMail problem? |
39 |
> |
40 |
> Neil, have you tried inspecting your drive with sys-apps/nvme-cli? I don't |
41 |
> have any experience to relate as I haven't worked out how to use it yet, but |
42 |
> it may help you. |
43 |
> |
44 |
|
45 |
|
46 |
|
47 |
Did you see the doc:: |
48 |
NVMeSSD_User_Installation_Guide_whitepaper-0.pdf |
49 |
|
50 |
That's some fancy piece of hardware, that says it requires special drivers:: |
51 |
|
52 |
Chipset Intel 5520 or later generation chipset |
53 |
Slots |
54 |
• Require PCIe Gen3 x4 link width slot (For Max Performance) |
55 |
• Support PCIe Gen1/Gen2 slot |
56 |
|
57 |
|
58 |
The following operating systems are supported, with some requiring |
59 |
additional drivers: |
60 |
• Windows Server® 2008R2 (64bit) |
61 |
• Windows Server 2012/2012 R2 (64bit) |
62 |
• Windows 7, 8, 8.1 (32/64bit) |
63 |
• Red Hat® Enterprise Linux (RHEL) 7.0 (64bit) |
64 |
• Red Hat Enterprise Linux (RHEL) 6.4/6.5 (64bit) |
65 |
• SUSE® Linux Enterprise (SLES) 11SP3 (64bit) |
66 |
• Ubuntu® 12.04.02 LTS Server (64bit) |
67 |
• Ubuntu® 12.04.04 LTS Server (64bit) |
68 |
• Solaris 11 SP2 (64bit) |
69 |
|
70 |
|
71 |
Installing the Driver on a Linux System |
72 |
RHEL 6.4 / 6.5 64bit |
73 |
1. Turn the power on and log on to the system with the admin account. |
74 |
2. Copy the driver file package to the installation folder. |
75 |
3. Install the rpm with the command below. After installing, the NVMe |
76 |
driver will automatically load when the system is booted. |
77 |
# rpm --ivh nvme-kmp-default-1.17_3.0.76_0.11-0.x86.64.rpm |
78 |
(The file name could change depending on the driver version.) |
79 |
4. To upgrade from v1.9, execute the following command: |
80 |
# rpm --Uvh nvme-kmp-default-1.17_3.0.76_0.11-0.x86.64.rpm |
81 |
5. To uninstall the package, execute the following command: |
82 |
# rpm --e nvme-kmp-default-1.17_3.0.76_0.11-0.x86.64.rpm |
83 |
|
84 |
|
85 |
Verifying the Installation of the software package in the Linux System |
86 |
1. Turn the system power on, and then start the terminal window. |
87 |
2. Run “Modinfo mtip32xx.” If the NVMe driver has been installed |
88 |
successfully, the version and module information are shown. |
89 |
3. Run “fdisk –l | grep rssd*”; the NVMe SSD is shown as |
90 |
“/dev/rssd<x>drive”. |
91 |
Starting Re-Drive and Checking the NVMe SSD State |
92 |
1. Click the “Identify” tab and Name Space Button. |
93 |
2. The NVMe SSD information is displayed. |
94 |
|
95 |
Using the NVMe SSD as a boot Drive (etc etc etc) |
96 |
|
97 |
You might have to go digging around the kernel modules to find drivers, |
98 |
specs and such... |
99 |
|
100 |
|
101 |
good_hunting::hth, |
102 |
James |