On Thu, 18 Feb 2021 13:36:15 -0800
wes dijo:
>On Thu, Feb 18, 2021 at 1:24 PM John Jason Jordan
>wrote:
>
>>
>> It's definitely not the cable. I have three TB3 cables, and they have
>> been swapped, yet the problem remains.
>So the next logical step is to swap the other bits of hardware. Which
On Thu, Feb 18, 2021 at 1:24 PM John Jason Jordan wrote:
>
> It's definitely not the cable. I have three TB3 cables, and they have
> been swapped, yet the problem remains.
>
>
So the next logical step is to swap the other bits of hardware. Which is
really difficult when you only have 1 of each.
On Thu, 18 Feb 2021 10:40:04 -0800
David dijo:
>On 2/17/21 4:40 PM, John Jason Jordan wrote:
>
>> Yes, device names may change on booting or when plugged in, but don't
>> device names stay put once you are booted or a drive is plugged in?
>
>This sounds like a cable or hardware issue to me. If a
On 2/17/21 4:40 PM, John Jason Jordan wrote:
Yes, device names may change on booting or when plugged in, but don't
device names stay put once you are booted or a drive is plugged in?
This sounds like a cable or hardware issue to me. If a drive is mounted
and something happens and the kernel
On Thu, Feb 18, 2021, 02:18 John Jason Jordan wrote:
>
>
> >There are two ways to cleanly stop raid array:
> > 1. Easiest:
> > sudo shutdown -h
> > 2. If you need to change configuration, add/remove disks, etc.
> > Copy
> > paste from:
>
> What does -h reference? How do I
On Wed, 17 Feb 2021 22:57:55 -0800
TomasK dijo:
>On Wed, 2021-02-17 at 21:59 -0800, John Jason Jordan wrote:
>> On Thu, 18 Feb 2021 00:27:25 -0500
>> Tomas Kuchta dijo:
>> I never heard of 'sync.' Is that a command?
>>
>> > Definitely not a good idea to unplug disk array without clean
>> >
On Wed, 2021-02-17 at 21:59 -0800, John Jason Jordan wrote:
> On Thu, 18 Feb 2021 00:27:25 -0500
> Tomas Kuchta dijo:
>
> > > And before umount/mount I pulled the TB3 plug from the enclosure,
> > > waited a couple of minutes, then plugged it back in, but I was
> > > still
> > > unable to access
On Thu, 18 Feb 2021 00:27:25 -0500
Tomas Kuchta dijo:
>> And before umount/mount I pulled the TB3 plug from the enclosure,
>> waited a couple of minutes, then plugged it back in, but I was still
>> unable to access any of the files. It should have automatically
>> mounted, because that's what
On Wed, Feb 17, 2021, 19:41 John Jason Jordan wrote:
> On Wed, 17 Feb 2021 18:55:11 -0500
> Tomas Kuchta dijo:
>
> >On Wed, Feb 17, 2021, 17:30 John Jason Jordan wrote:
> >
> >> On Wed, 17 Feb 2021 14:05:20 -0800
> >> John Jason Jordan dijo:
> >>
> >> >This is driving me nuts.
> >>
> >>
On Wed, 17 Feb 2021 18:55:11 -0500
Tomas Kuchta dijo:
>On Wed, Feb 17, 2021, 17:30 John Jason Jordan wrote:
>
>> On Wed, 17 Feb 2021 14:05:20 -0800
>> John Jason Jordan dijo:
>>
>> >This is driving me nuts.
>>
>> Before rebooting I tried to umount md127p1, but got the 'busy' error
>> message,
On Wed, Feb 17, 2021, 17:30 John Jason Jordan wrote:
> On Wed, 17 Feb 2021 14:05:20 -0800
> John Jason Jordan dijo:
>
> >This is driving me nuts.
>
> Before rebooting I tried to umount md127p1, but got the 'busy' error
> message, which I solved with the 'lazy' -l option. But although umount
>
On Wed, 17 Feb 2021 14:05:20 -0800
John Jason Jordan dijo:
>This is driving me nuts.
Before rebooting I tried to umount md127p1, but got the 'busy' error
message, which I solved with the 'lazy' -l option. But although umount
-l executed without error, it didn't umount the array. Eventually I
On Tue, 2 Feb 2021 12:31:45 -0800
John Jason Jordan dijo:
>nvme0
>nvme0n1
>nvme1
>nvme1n1
>nvme2
>nvme2n1
>nvme3
>nvme3n1
>nvme4
>nvme4n1
>nvme4n1p1
>nvme4n1p2
>
>And scrolling up a bit I see md127 and md127p1.
>
>Everything is back to normal. My only problem is what happens when the
>md127 and
On Wed, 3 Feb 2021, John Jason Jordan wrote:
jjj@Devil-Thinkpad:~$ sudo /proc/mdstat
John,
The /proc/files are text. Use:
sudo less /proc/mdstat
Rich
___
PLUG: https://pdxlinux.org
PLUG mailing list
PLUG@pdxlinux.org
On Wed, Feb 3, 2021 at 4:14 PM John Jason Jordan wrote:
>
> $ /proc/mdstat
>
>
Ah, yeah, we could have been clearer about that too. try cat /proc/mdstat
-wes
___
PLUG: https://pdxlinux.org
PLUG mailing list
PLUG@pdxlinux.org
On Wed, 3 Feb 2021 15:05:33 -0800
wes dijo:
>On Wed, Feb 3, 2021 at 2:19 PM John Jason Jordan
>wrote:
>
>> On Wed, 3 Feb 2021 12:48:48 -0800 Larry Brigman
>> dijo:
>> >/proc/mdadm will give you the status of the assembled arrays
>> >directly without the need to go through the mdadm util.
>>
>>
On Wed, Feb 3, 2021 at 2:19 PM John Jason Jordan wrote:
> On Wed, 3 Feb 2021 12:48:48 -0800 Larry Brigman
> dijo:
> >/proc/mdadm will give you the status of the assembled arrays directly
> >without the need to go through the mdadm util.
>
> /proc/mdadm
> bash: /proc/mdadm: No such file or
On Wed, 3 Feb 2021 12:48:48 -0800
Larry Brigman dijo:
>You can use mdadm to examine the superblock on each drive and it will
>give you the details of the array that the drive thinks it is in.
>Without a mdadm.conf, the kernel will attempt to assemble the array
>based on what it finds in the
You can use mdadm to examine the superblock on each drive and it will
give you the details of the array that the drive thinks it is in.
Without a mdadm.conf, the kernel will attempt to assemble the array
based on what it finds in the drive superblocks and will default to
md127 and count up from
On Tue, 2 Feb 2021 19:46:51 -0800
wes dijo:
>If you create the RAID array with UUIDs, it (probably) won't break when
>your system renames devices.
Brilliant!
___
PLUG: https://pdxlinux.org
PLUG mailing list
PLUG@pdxlinux.org
On Tue, Feb 2, 2021 at 7:36 PM John Jason Jordan wrote:
> It's nice to know that you can get the UUID from /dev/disk, but there
> is also a command (that I have forgotten) to get the UUID. For a long
> time I used LABEL= for mounting, where I had give the partition a
> label. Labels are great,
On Tue, 2 Feb 2021 18:49:21 -0800
wes dijo:
>On Tue, Feb 2, 2021 at 6:32 PM John Jason Jordan
>wrote:
>
>> I have long been aware that drive labeling like sda, sdb, etc. can
>> annoyingly swap around. Apparently NVMe drives can be just as
>> exasperating.
>Do you have a /dev/disk directory? If
On Tue, Feb 2, 2021 at 6:32 PM John Jason Jordan wrote:
> I have long been aware that drive labeling like sda, sdb, etc. can
> annoyingly swap around. Apparently NVMe drives can be just as
> exasperating.
>
>
Do you have a /dev/disk directory? If so, within it you should find various
ways of
On Tue, 2 Feb 2021 17:07:45 -0800
Ben Koenig dijo:
> smartctl -a /dev/nvme0n1
OK, this is really weird. All this time nvme0 has been the 1TB m.2
Samsung drive inside the Thinkpad, which holds / and /home. I was amazed
when I ran the command exactly as above and it said the drive was a
7.68TB
On 2/2/21 3:20 PM, John Jason Jordan wrote:
On Tue, 2 Feb 2021 05:50:57 -0800 (PST)
Rich Shepard dijo:
On Tue, 2 Feb 2021, John Jason Jordan wrote:
And one more thought: I'd consider LVM instead of RAID0. But whatever
system I set up, I need the four 7.68TB NVMe drives to appear as one
On Tue, 2 Feb 2021 05:50:57 -0800 (PST)
Rich Shepard dijo:
>On Tue, 2 Feb 2021, John Jason Jordan wrote:
>
>> And one more thought: I'd consider LVM instead of RAID0. But whatever
>> system I set up, I need the four 7.68TB NVMe drives to appear as one
>> big-ass 31TB drive.
>That's what LVM
On 2/2/21 12:31 PM, John Jason Jordan wrote:
On Tue, 2 Feb 2021 12:09:06 -0800
John Jason Jordan dijo:
On Mon, 1 Feb 2021 23:48:03 -0800
Ben Koenig dijo:
A simple test to help everyone here understand what your machine is
doing would be to run through a few reboots and grab the list of
On Tue, 2 Feb 2021 12:09:06 -0800
John Jason Jordan dijo:
>On Mon, 1 Feb 2021 23:48:03 -0800
>Ben Koenig dijo:
>
>>A simple test to help everyone here understand what your machine is
>>doing would be to run through a few reboots and grab the list of
>>devices, like so
>>
>>1) unplug your TB-3
On 2/2/21 12:09 PM, John Jason Jordan wrote:
On Mon, 1 Feb 2021 23:48:03 -0800
Ben Koenig dijo:
A simple test to help everyone here understand what your machine is
doing would be to run through a few reboots and grab the list of
devices, like so
1) unplug your TB-3 drives and reboot.
2)
On Mon, 1 Feb 2021 23:48:03 -0800
Ben Koenig dijo:
>A simple test to help everyone here understand what your machine is
>doing would be to run through a few reboots and grab the list of
>devices, like so
>
>1) unplug your TB-3 drives and reboot.
>
>2) record the output of 'ls -l /dev/nvme*' here
On Tue, 2 Feb 2021, John Jason Jordan wrote:
And one more thought: I'd consider LVM instead of RAID0. But whatever
system I set up, I need the four 7.68TB NVMe drives to appear as one
big-ass 31TB drive.
John,
That's what LVM does. You have four physical drives. They can be collected
into
On Mon, 1 Feb 2021 23:48:03 -0800
Ben Koenig dijo:
>On 2/1/21 11:35 PM, John Jason Jordan wrote:
>> On Mon, 1 Feb 2021 22:15:12 -0800
>> Ben Koenig dijo:
>>
Perhaps now would be the time to dig out those old emails and
consider some of the native alternatives rejected in favor of
On 2/1/21 11:35 PM, John Jason Jordan wrote:
On Mon, 1 Feb 2021 22:15:12 -0800
Ben Koenig dijo:
Perhaps now would be the time to dig out those old emails and
consider some of the native alternatives rejected in favor of RAID0.
Unfortunately it looks like RAID might not be the culprit if
On Mon, 1 Feb 2021 22:15:12 -0800
Ben Koenig dijo:
>> Perhaps now would be the time to dig out those old emails and
>> consider some of the native alternatives rejected in favor of RAID0.
>Unfortunately it looks like RAID might not be the culprit if his NVMe
>/dev nodes are moving around. RAID0
On 2/1/21 9:16 PM, TomasK wrote:
On Mon, 2021-02-01 at 16:19 -0800, John Jason Jordan wrote:
About a week ago I finally was successful in creating a RAID0 array
on
my four NVMe drives that are installed in a Thunderbolt 3 enclosure.
After creating the array it appeared in /dev as md0. After
On Mon, 2021-02-01 at 16:19 -0800, John Jason Jordan wrote:
> About a week ago I finally was successful in creating a RAID0 array
> on
> my four NVMe drives that are installed in a Thunderbolt 3 enclosure.
> After creating the array it appeared in /dev as md0. After rebooting
> it
> became md127.
About a week ago I finally was successful in creating a RAID0 array on
my four NVMe drives that are installed in a Thunderbolt 3 enclosure.
After creating the array it appeared in /dev as md0. After rebooting it
became md127. I copied the UUID from Gparted and used it in a line
that I added to
37 matches
Mail list logo
