From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id E713913832E for ; Thu, 18 Aug 2016 10:50:01 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7929621C094; Thu, 18 Aug 2016 10:49:47 +0000 (UTC) Received: from omr-a002e.mx.aol.com (omr-a002e.mx.aol.com [204.29.186.56]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 792B421C03E for ; Thu, 18 Aug 2016 10:49:46 +0000 (UTC) Received: from mtaout-aag02.mx.aol.com (mtaout-aag02.mx.aol.com [172.26.126.78]) by omr-a002e.mx.aol.com (Outbound Mail Relay) with ESMTP id 662053800090 for ; Thu, 18 Aug 2016 06:49:45 -0400 (EDT) Received: from [192.168.1.52] (0x5b3139322e3136382e312e35325d [71.122.242.106]) by mtaout-aag02.mx.aol.com (MUA/Third Party Client Interface) with ESMTPA id 10FA138000084; Thu, 18 Aug 2016 06:49:45 -0400 (EDT) Subject: Re: [gentoo-user] Can't create valid btrfs on NVMe To: gentoo-user@lists.gentoo.org References: <20160817232613.47d780b3@digimed.co.uk> <12824311.xoTMXCyb4d@peak> From: james Message-ID: <86bed682-a864-12e8-c25b-780e4fa80a7b@verizon.net> Date: Thu, 18 Aug 2016 06:49:31 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 In-Reply-To: <12824311.xoTMXCyb4d@peak> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit x-aol-global-disposition: G x-aol-sid: 3039ac1a7e4e57b592c978c8 X-AOL-IP: 71.122.242.106 X-Archives-Salt: 023ae594-b4e7-4650-bac7-c23497895520 X-Archives-Hash: 829194b3aad52e19af0be4fc2669087b On 08/18/2016 05:06 AM, Peter Humphrey wrote: > On Thursday 18 Aug 2016 15:56:50 Adam Carter wrote: >> On Thu, Aug 18, 2016 at 8:26 AM, Neil Bothwick wrote: >>> I'm putting together a new desktop using a Samsung SM951 NVMe drive. I >>> booted sysrescd, partitioned the drive and ran >>> >>> mkfs.btrfs /dev/nvme0n1p3 >>> mount /dev/nvme0n1p3 /mnt/custom >>> >>> df -T, mount and findmnt all show this is mounted as a btrfs filesystem, >>> e.g. >>> >>> /dev/nvme0n1p3 on /mnt/custom type btrfs (rw,relatime,ssd,space_cache) >>> >>> I can create files in here but cannot do anything btrfs-y >>> >>> % btrfs filesystem show /mnt/custom >>> ERROR: not a valid btrfs filesystem: /mnt/custom >>> >>> % btrfs subvolume create /mnt/custom/test >>> Create subvolume '/mnt/custom/test' >>> ERROR: cannot create subvolume: Inappropriate ioctl for device >>> >>> Google has been no help at all. >> >> I'm assuming tools are expecting SATA (or SCSI) and need an update or >> alternative for nvm; >> >> # hdparm -i /dev/nvme0n1 >> >> /dev/nvme0n1: >> HDIO_DRIVE_CMD(identify) failed: Inappropriate ioctl for device >> HDIO_GET_IDENTITY failed: Inappropriate ioctl for device >> >> Maybe SCSI emulation could work around it? >> CONFIG_BLK_DEV_NVME_SCSI > > I don't have Neil's e-mail here - another KMail problem? > > Neil, have you tried inspecting your drive with sys-apps/nvme-cli? I don't > have any experience to relate as I haven't worked out how to use it yet, but > it may help you. > Did you see the doc:: NVMeSSD_User_Installation_Guide_whitepaper-0.pdf That's some fancy piece of hardware, that says it requires special drivers:: Chipset Intel 5520 or later generation chipset Slots • Require PCIe Gen3 x4 link width slot (For Max Performance) • Support PCIe Gen1/Gen2 slot The following operating systems are supported, with some requiring additional drivers: • Windows Server® 2008R2 (64bit) • Windows Server 2012/2012 R2 (64bit) • Windows 7, 8, 8.1 (32/64bit) • Red Hat® Enterprise Linux (RHEL) 7.0 (64bit) • Red Hat Enterprise Linux (RHEL) 6.4/6.5 (64bit) • SUSE® Linux Enterprise (SLES) 11SP3 (64bit) • Ubuntu® 12.04.02 LTS Server (64bit) • Ubuntu® 12.04.04 LTS Server (64bit) • Solaris 11 SP2 (64bit) Installing the Driver on a Linux System RHEL 6.4 / 6.5 64bit 1. Turn the power on and log on to the system with the admin account. 2. Copy the driver file package to the installation folder. 3. Install the rpm with the command below. After installing, the NVMe driver will automatically load when the system is booted. # rpm --ivh nvme-kmp-default-1.17_3.0.76_0.11-0.x86.64.rpm (The file name could change depending on the driver version.) 4. To upgrade from v1.9, execute the following command: # rpm --Uvh nvme-kmp-default-1.17_3.0.76_0.11-0.x86.64.rpm 5. To uninstall the package, execute the following command: # rpm --e nvme-kmp-default-1.17_3.0.76_0.11-0.x86.64.rpm Verifying the Installation of the software package in the Linux System 1. Turn the system power on, and then start the terminal window. 2. Run “Modinfo mtip32xx.” If the NVMe driver has been installed successfully, the version and module information are shown. 3. Run “fdisk –l | grep rssd*”; the NVMe SSD is shown as “/dev/rssddrive”. Starting Re-Drive and Checking the NVMe SSD State 1. Click the “Identify” tab and Name Space Button. 2. The NVMe SSD information is displayed. Using the NVMe SSD as a boot Drive (etc etc etc) You might have to go digging around the kernel modules to find drivers, specs and such... good_hunting::hth, James