× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

ReadyNAS 424 - Installing support for NTFS - ntfs-3g

EHCanadian
Star

ReadyNAS 424 - Installing support for NTFS - ntfs-3g

So I'm trying to get this ReadyNAS 424 running ReadyNAS v6.10.2 that has

a outdated os of debian jessie that has been set to archive mode by the

maintainers (debian). I am looking to have ntfs/windows file system support

on the readynas os. So after enabling ssh, setting up some repos and the

hassle of tracking down dependincies, I still can not get he system to

reconize a existing (raid 0, 4 disks, windows ntfs gpt)

 

ntfs-3g is installed so is gdisk 

 

I've tried ramming Debian 9.11 down its throat. Didn't work. factory

reset without the disks being in. I'm using a M2 drive for the primary

drive for this system as I screw around trying to get this darn thing

to detect and support ntfs.

 

So the game plan was to have my existing DAS raid 0 with ntfs gpt

be backed up to this readynas device. But for failure reasons I need

the readynas to mount a ntfs raid 0 gpt so I can replace the DAS

raid with the readynas raid incase of disk failure. I don't care for the

readynas interface so I can terminal and use webmin for what I need.

 

But cleary NetGear has done something with the readynas os and I

can't figure it out. https://wiki.debian.org/NTFS

 

mkdir /windows

mdadm --build /dev/md2000 --level=0 --raid-devices=4 /dev/sda /dev/sdb /dev/sdc /dev/sdd

mount -t ntfs /dev/md2000 /windows
Error: mount: unknown filesystem type 'ntfs'

mount -t ntfs-3g /dev/md2000 /windows
Error: mount: unknown filesystem type 'ntfs-3g'

 

root@ReadyNAS424:~# mkfs.ntfs -f /dev/md2000
Cluster size has been automatically set to 4096 bytes.
Creating NTFS volume structures.
mkntfs completed successfully. Have a nice day.

root@ReadyNAS424:~# fdisk -l

Disk /dev/sda: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: F39DE616-28BE-4386-8A2F-80665F24CD27


Disk /dev/sdb: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 78BCBE22-702A-4A1F-B96E-D28505B74AF6


Disk /dev/sdc: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 8E99BE17-7BFA-4A92-81DB-08E3ABBE622E


Disk /dev/sdd: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 2EA45BD2-AF20-4A5A-8AA4-DF3D38FEEE3A


Disk /dev/sde: 111.8 GiB, 120040980480 bytes, 234455040 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 24B6B301-8899-4AC8-BAFA-CEDBD2E5AEDB

Device Start End Sectors Size Type
/dev/sde1 64 8388671 8388608 4G Linux RAID
/dev/sde2 8388672 9437247 1048576 512M Linux RAID
/dev/sde3 9437248 234454991 225017744 107.3G Linux RAID

Disk /dev/md0: 4 GiB, 4290772992 bytes, 8380416 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/md127: 107.2 GiB, 115141967872 bytes, 224886656 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/md2000: 14.6 TiB, 16003148021760 bytes, 31256148480 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 262144 bytes
Disklabel type: dos
Disk identifier: 0x2052474d

Device Boot Start End Sectors Size Id Type
/dev/md2000p1 ? 6579571 1924427647 1917848077 914.5G 70 DiskSecure Multi-Boot
/dev/md2000p2 ? 1953251627 3771827541 1818575915 867.2G 43 unknown
/dev/md2000p3 ? 225735265 225735274 10 5K 72 unknown
/dev/md2000p4 2642411520 2642463409 51890 25.3M 0 Empty

Partition 2 does not start on physical sector boundary.

Partition 3 does not start on physical sector boundary.

Partition 4 does not start on physical sector boundary.


Partition table entries are not in disk order.

 

At this point I walk away and go grab a coffee. Did some googleing. It shouldn't be this hard to get a ntfs with gpt mounted.

 

Anyone got any ideas ? These disks are for the backups so they can be tested on.

 

 

Model: RN424|ReadyNAS 424 – High-performance Business Data Storage - 4-Bay
Message 1 of 4
StephenB
Guru

Re: ReadyNAS 424 - Installing support for NTFS - ntfs-3g

I don't have any direct help, but I will say that the stock ReadyNAS already has support for NTFS disks (though the readynasd application itself only supports NTFS for usb disks).

 

Not sure if you can go back to the unmodified ReadyNAS at this point, but it might be worth testing this with the stock firmware using an NTFS formatted USB drive first, just to take mdadm out of the equation.

Message 2 of 4
EHCanadian
Star

Re: ReadyNAS 424 - Installing support for NTFS - ntfs-3g

They have stripped the NTFS support for it out of debian documented ways and any debian/linux forum you may come acrosss.

While it "may" have support for usb drives that does me little use.

 

I was sucessfull in getting NTFS with GPT on Debian 9 and 10. I just had to replace all of netgear binaries.

*It is doable. Just you will break the web interface or run into dependency loops that can take hours to hunt down as to upgrade from 8 to 9

you will have to force packages with dpkg.. NetGears binaries are hard coded and depentant on one another. apt isn't your friend at

this stage and you will being using dpkg alot.*

 

So I was sucessfull after a few days. It was a complete hassle that they did it this way.

Hopefully in the future they reconsider the slim down approach. I miss my 314. It has a HDMI port and life was simpler to run my distro of

choise. Or give back the hdmi/video output. I don't mind paying a few dollors more for a unit with hdmi/vga/dvi without a os would be

even better. Always allow memory to be upgradeable with two SODIMM slots. Make the readynas os its own product.

 

Other notes.

1, Use a M2 Drive or another drive port if the logic board/motherboard has it and not in the 3.5 bays if you want to tinker.

 (This way the raid bays are one raid type and file system format)

2, Always remove the 3.5" disks from the unit if you factory reset.

 (It destories the existing partitions and installs itself in a RAID 5 across all the disks.)

3. A DAS and a mini computer is a better idea if you want to run vanilla or your own distro.

4. Disable flex raid before inserting your drives if you opt to use another smaller drive for the os.

 (it will destroy your existing raid and raid 5 your 3.5" disks)

 

My next adventure is seeing if I can get that PCI-E 4x port to support a low power graphics card to see if I can even install with a x4 to x16

adaptor/ribbin and clean install that way. If not I'm tossing the whole thing out as it was a warrenty exchange anyhow.

 

Not interested in learning UART

Message 3 of 4
EHCanadian
Star

Re: ReadyNAS 424 - Installing support for NTFS - ntfs-3g

When I insert a pci-e 16x card the power supply turns off.

- Also doesn't power up when the card is in the slot and you plugin in the power.

When I insert a 4x to 16x riser/adaptor, the power supply turns off.

- Also doesn't power up when the card is in the slot and you plugin in the power.

 

I grabbed a 4x server grade small height factor dvi card and tried the slot.

 - Also doesn't power up when the card is in the slot and you plugin in the power.

 

So ether the pci-e 4x slot isn't actually a pci-e 4x port and they may have used the slot

to run the raid card only. I also tried to run some headless distros. No go.

 

Also tried removing the daughter board and no go. Won't even boot at that point with the

M.2 drive in the slot. Sure would have been nice to see what the darn thing is doing.

 

Ah well. I tried everything but the uart port option. They really didn't want you to be able

to do anything but run their readynas os on this thing. (ReadyNAS 424)

Message 4 of 4
Top Contributors
Discussion stats
  • 3 replies
  • 1096 views
  • 0 kudos
  • 2 in conversation
Announcements