I received a wd external usb hard drive (my book 8Tb) and I connected it to omv6. The disk has been easily recognized. It comes however in ntfs format. Omv6 Internal drive has two partitions, a small one for system (sda) and a second, large one for data (sdb). Both are in ext4. Now, the official omv6 guide says that it could be possible to use the ntfs hard drive as it is, but there are technical limitations. It does not say which ones since they are beyond the scope of the introduction. Let me point out the case: it is about a digital archive of texts. No need of a raid, since the archive has been copied in many pc. Also, we dispose at the moment of 3 omv6 server and 3 wd My book. The idea would be use sdb (internal drive) as a storage point for incoming texts waiting for ocr, format conversion and so on. It should function as a sort of antechamber of sdc (external drive), where a separated folder would be created for the archive. The archive folder on a ntfs external drive could be easily transported and red by windows. What would be the technical limitations in this case? I would be grateful if I could receive any help or suggestion for a storage configuration that suits the case.
Hi, thanks a lot for your explanations. I guess, the only way to know if there will be limitations with file and folder permissions is to try and see if the result is acceptable. I will make a test. Since the disk is ready, I have to mount it, create a shared folder, give permissions to "write list = @users" and see if I can access and download the file, correct?
Otherwise, In case of problems, I will format the hard disk in ext4. If I remember well, omv6 has a wipe and format function, but I wonder if it would be faster to prepare the disk with a free partition tool that supports ext4.
It may work initially, but after a while problems may arise if those files are managed from windows and some permissions are changed unintentionally. This would end up crashing with the Linux permissions system. This is why it is not recommended to work with NTFS file systems.
The fact that NTFS is allowed is solely for the purpose of being able to plug in a drive and do a backup, maybe something else. But if the intention is to share folders from that disk, the recommendation is to use a native Linux file system. EXT4, BTRFS, ...
Ok Thanks a lot. Just a final question: do I have to build a storage pool? If possible, I would keep things separated. Existing folder A "Incoming Texts", new, large drive: folder B: "Archive". Is it ok so? I would not like to share the data between the disks, since disk A is not as reliable as disk B, which is brand new.
I currently find myself in a desperate situation. I'm trying to boot from the pendrive on my computer installed with Ubuntu 22.10, it is not recognizing my pendrive formatted with the NTFS file system, which consequently makes it impossible to boot and format my computer.
I've always formatted my notebook with NTFS and it worked perfectly, but with this latest version of Ubuntu 22.10 I'm not having success. Currently my computer only recognizes the FAT32 file system (I can usually format it in this format), but the problem is that I am trying to install Windows 11 and a certain ISO file is 4.8 GB, i.e. , the file is broken with a file size limitation of 4GB (the OS installation window will open but will not install because of this).
I honestly don't know what's going on, I've tried other file system formats, but Ubuntu is only releasing FAT32 and I can't install the operating system due to the file size limitation. Before someone tells me that the Pendrive is not configured correctly, Incorrect boot order in BIOS/UEFI, Corrupted boot image, Defective or damaged Pendrive, etc., I have already checked all of this, does anyone know of a solution?
Several but not all computers can boot from an NTFS partition in UEFI mode. In other words, the Windows installer, that you created I think similar to this method on a USB drive, should work in several computers, but it seems your computer needs a FAT32 partition for that purpose.
The classic tool to create a Windows installer, winusb, was forked to woeusb, and it has been modified several times to keep up with modifications of both Windows and Linux. I think this link describing the github version of woeusb is up to date (but have not checked in Sept 2023).
Assuming you can actually format some drive/partition with NTFS on your Ubuntu machine or some other machine, you can extract and copy the content (i.e. files, directories inside) of the Windows ISO to the drive and boot it with grub. It does not matter whether the drive is the same drive where grub is installed on.
On (modern) Windows, you can mount the ISO by simply double clicking it. You should then see it attached as some sort of virtual drive where you can select all, copy and paste the content from the ISO to the NTFS-formatted drive.
Again, this requires your distro ships either a kernel with NTFS driver or ntfs-3g, the userspace/FUSE driver, in their package repo. For the latter should be able to install it with your package manager, if it is not installed yet.
If the drive is a USB drive, it might be automatically mounted by your desktop environment (DE) via udisks2. If that's the case, you probably need to find out where it is mounted, instead of mounting it again with mount. (Often it would be somewhere under /media or /run/media. And you might not even need to know where exactly the path is if you can see it in your file manager and are going to perform the file copying with it.)
Certainly you can perform the file copying with GUI file manager in the "Windows manner" instead. (But well, GUI file copying has been surprisingly problematic for a long time, like stalling / cannot finish for no reasons even long after the expected flushing time. Maybe things have become better. Maybe not. I have no idea since CLI works perfectly fine for me.)
49EA0D032930D9B5 in the example is the volume serial number of the NTFS filesystem (where the content of the ISO have been copy to). It is treated as the filesystem UUID (note: NOT PARTUUID) in Linux so you should be able to find it out with lsblk -f or blkid easily.
You might find some similar example which ask you to have a bunch of insmod. In my experience with the grub shiped in Arch Linux, none is necessary. But you can probably have it for part_msdos, part_gpt and ntfs anyway just in case.
(Note that this works only if your have efi grub. If you have bios grub that has been booted through CSM, this won't work. I think you'll get an error from grub in that case. It probably won't just give you a black screen or reset. I don't know for sure though.)
P.S. Since I personally haven't been generating grub.cfg for a long time, I don't have an exact idea where you should put the menu entry so that grub-mkconfig / update-grub will add it to grub.cfg (and hence your grub boot menu). It's probably some file under /etc/grub.d or so. Do your own research. Also, since you probably need it for a while only, you may even just put it to the end of your grub.cfg (under /boot/grub).
Los pendrive USB son herramientas muy tiles para llevar documentos o datos con nosotros de un sitio a otro, entre otros muchos menesteres, y son varios los formatos que podemos darle a nuestros pendrive USB en Windows, pero, sabes cul de ellos es el mejor? Te explicamos cmo puedes formatear un pendrive USB, y qu tipo de formato es el mejor.
A la hora de elegir el formato para un pen drive, tenemos varias opciones diferentes; el mtodo de formateo es el mismo que utilizaramos para cualquier otra unidad, sea disco duro o unidad de estado slido, y por lo tanto las opciones que el sistema operativo nos ofrece para realizarlo son las mismas. En cualquier caso, cada tipo de formato tiene sus ventajas, pero tambin sus desventajas, as que vamos a ver cul es la ms adecuada cuando hablamos de un pen drive USB.
Un formato de archivos es una forma en la que estos se organizan los datos en la unidad de almacenamiento para que as el sistema operativo sepa como leerlos y escribirlos. Generalmente, son estos tres tipos de formato los que podrs utilizar bajo Windows para un pendrive USB. Vamos a ver en qu consiste cada uno de ellos:
Por lo tanto, solo deberemos formatear nuestros pendrives en FAT32 cuando queramos que sean compatibles con el mximo nmero de dispositivos posibles, pero asegurndonos de que no tendrn archivos de ms de 4 GB (ms que nada porque no podremos meterlos dentro).
Aunque parezca mentira, sigue siendo el ms usado por lo que hemos comentado de la compatibilidad, ya que a da de hoy sigue siendo complicado encontrar un archivo que pese ms de 4 GB, por lo que muchos fabricantes siguen usando FAT32 para garantizar la compatibilidad por encima de otras ventajas que tienen los formatos de archivos que vamos a ver a continuacin.
Si bien es cierto que es un sistema de archivos propietario de Microsoft, eso no significa que, desde otros sistemas operativos, como macOS o Linux no se pueda acceder a su contenido. Se puede acceder sin problemas, pero nicamente en modo lectura.
Si queremos escribir datos ser necesario utilizar una aplicacin especfica para hacerlo en macOS. En Linux, como incorpora drivers genriccos, no es necesario, pero, al no ser oficiales, el funcionamiento no siempre ser el mejor de todos.
d3342ee215