How to access the data on an internal nvme

[makem]

I have a NAS with 2 parity drives and two data drives in the array. I also have a 2TB nvme used as an archive and I would like to access the data it contains. I don't know where to start and research seems to be only related to adding drives to the array or as external ones.

 

Is it a form of mapping?

 

My OS is Ubuntu 24.04

 

Can I get some pointers to start me off in the right direction please?

Edited September 22, 2024 by makem
added OS

[JonathanM]

Where was the nvme used before? What format is it? Probably could use the Unassigned Devices plugin to read it.

diagnostics might be useful

[makem]

Thank you for your time.

 

The nvme was new when I built the machine 2 or 3 years ago. There is another one too.

 

It has always been used as a place for an archive of stuff gathered over the years. It is formatted NTFS as it can also be accessed from a Windows dual boot OS.

nas-diagnostics-20240922-2119.zip

[JonathanM]

Unassigned Devices can mount and read NTFS.

 

Only issue I can think of is if the volume wasn't completely closed properly the last time it was mounted in the Windows system.

[makem]

1 hour ago, JonathanM said:

Unassigned Devices can mount and read NTFS.

 

Only issue I can think of is if the volume wasn't completely closed properly the last time it was mounted in the Windows system.

I have checked in Windows and it was closed fully. I noticed that it was not visible in Unassigned Devices there either.

Does it need to be mounted in /mnt/disks and if so, how?

 

Can the Unassigned Devices plugin deal with internal nvme drives?

Edited September 22, 2024 by makem
query if UD can see nvme

[JorgeB]

20 minutes ago, makem said:

Can the Unassigned Devices plugin deal with internal nvme drives?

Yes, please post the diagnostics.

 

 

[makem]

Diagnostics were posted earlier but repeated below.

nas-diagnostics-20240922-2347.zip

[JorgeB]

Only one NVMe device is being detected by Linux, the one assigned as cache, I assume it's not that one? Check to see if it's detected din the BIOS and or try a different m.2 slot.

[makem]

It is not the cache and it is one of a pair of nvme's which are in use and working correctly for 2 or 3 years. I cannot use another slot as they are all taken.

 

I will take a look at the BIOS.

[makem]

BIOS shows the nvme's and tests are passed.

 

Perhaps the gparted images will help?

Edited September 22, 2024 by makem
added edited lsblk output

[JorgeB]

10 hours ago, makem said:

Perhaps the gparted images will help?

Not really, since that device is not being detected in Unraid.

[makem]

I am, wondering, as the diagnostics 'only reported one nvme'. Has it been assumed that the nvme I am concerned with is inside the NAS?

 

I am concerned about a PC which controls the NAS and which uses the NAS to store data as do another two PCs and mobile phones.

 

This Pc is not able to store data on the NAS from one of it's nvme's.

Edited September 23, 2024 by makem

[JorgeB]

I'm not sure I follow, is the 2TB device not installed in the Unraid server?

[makem]

1 hour ago, JorgeB said:

I'm not sure I follow, is the 2TB device not installed in the Unraid server?

No, it is in the machine which is running Ubuntu 24.04 as mentioned in my first post. Sorry if I have misslead the thread

Edited September 23, 2024 by makem

[JorgeB]

Not sure if Ubuntu can mount NFTS, if it can, mount the filesystem and share it over SMB or NFS, you can then connect to it with the UD plugin, but this is not an Unraid issue, so cannot really help with that, the easiest way, would be to add the NVMe device to the Unraid server and then mount it with UD.

 

 

[makem]

53 minutes ago, JorgeB said:

Not sure if Ubuntu can mount NFTS, if it can, mount the filesystem and share it over SMB or NFS, you can then connect to it with the UD plugin, but this is not an Unraid issue, so cannot really help with that, the easiest way, would be to add the NVMe device to the Unraid server and then mount it with UD.

 

 

Yes Ubuntu can mount NTFS as shown in the screenshots above.

 

I thought it was a nextcloud/unraid issue because nextcloud can see the drive but reports a permission problem although the drive is public.