Another DNS-323 and some difficulties

141 views
Skip to first unread message

Rolf Pedersen

unread,
Mar 1, 2020, 11:27:07 AM3/1/20
to al...@googlegroups.com
I've acquired what looks to be a good used 323 NAS box and flashed it with no disks loaded.
The box is currently running Alt-F 1.0 with kernel 4.4.86, and is flashed with "Alt-F-1.0, initrd" and kernel "Alt-F-1.0, kernel 4.4.86".

I'm downsizing my desktop and moving large amounts (hordes) of seldom-used files to this NAS, (theoretically).  So, I dropped in a 4TB and 8TB containing much of these files.





Partitions sda1,2,3 and sdb1 are reiserfs and don't get mounted.

[root@DNS-323A]# fdisk -l
fdisk: device has more than 2^32 sectors, can't use all of them
Found valid GPT with protective MBR; using GPT

Disk /dev/sda: 4294967295 sectors, 4095M
Logical sector size: 512
Disk identifier (GUID): 50421e26-11b8-4ae7-9937-c24d0607243e
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 7814037134

   Device  Start (sector)    End (sector)  Size (sectors)   Code  Name
/dev/sda1            2048      3610087423      3610085376   8300 
/dev/sda2      5860530176      6002923519       142393344   8300 
/dev/sda3      6002923520      6643689471       640765952   8300 
/dev/sda4      6643689472      7391203327       747513856   0700 
/dev/sda5      7391203328      7400962047         9758720   0700 
/dev/sda6      7400962048      7586908159       185946112   0700 
/dev/sda7      7586910208      7606441457        19531250   8300  
/dev/sda8      7606441984      7814037134       207595151   0700  
Segmentation fault
[root@DNS-323A]# fdisk -l /dev/sdb
fdisk: device has more than 2^32 sectors, can't use all of them
Found valid GPT with protective MBR; using GPT

Disk /dev/sdb: 4294967295 sectors, 4095M
Logical sector size: 512
Disk identifier (GUID): 0af1c4ec-e17c-46dd-8819-cb75da76b835
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 15628053134

   Device  Start (sector)    End (sector)  Size (sectors)   Code  Name
/dev/sdb1            2048      8220358655      8220356608   8300 
[root@DNS-323A]#

I figured I needed to install Alt-F packages to get full access and clear the e2fsck problem with sda7 and tried with what was available, only MS filesystems:



Long story short, no packages are displayed (after reboots, even), "UpdatePackageList" flashes the screen, briefly, without showing a list or error, and I see nothing in logs.

I've been running Alt-F on my first DNS-323 and, after some time, a DNS-320 for some years.  I've never created/used a user other than root and am not aware of any problems caused by that.  In this case, I tried adding a user, which threw the "can't change permissions" error for the MS filesystem, as it did for the Alt-F folder, understandably.  That made no difference about the packages list.  Also, these disks have no swap.  I could take one or both out, resize the first partition, and put swap at the beginning of the disk, IIUC that is where it needs to be.

Thanks,
Rolf


João Cardoso

unread,
Mar 2, 2020, 2:38:03 PM3/2/20
to Alt-F





Hi Rolf,

Your post cover many different subjects, so it is difficult to concentrate on the real issue, so a few brief notes:

-reiserfs is not supported under Alt-F, sorry. It was my fs of choice during years.

-fsck does not supports 64 bit features, which is now common. I have a e2fsck-1.42.13 pkg available, which supports 64 bit features accordingly to its documentation.
I'm reluctant  to make it available, as it has special installation requirements and it might cause troubles: Alt-F has to be installed on a USB pen or on a not otherwise used disk partition, otherwise fsck will "vanish" when the partition is unmounted to be checked. The experienced user will understand that, but might cause issues for normal users, which just install Alt-F packages in their main fs.

-Alt-F has to be installed on a ext2/3/4 filesystem, are you using vfat? "Interestingly" enough the destination fs type is checked when you try to copy the current Alt-F to a new fs (using Packages->Alt-F, CopyTo), but it is not detected at install time -- a bug!

-Creating Users is not really necessary, but it is "good practice" and useful to identify which is the more probable fs to be used by users. You can skip the first login wizard by just logout after creating the box password.

-swap will only be needed if fsck needs to run, so you can skip that for now. Do a fsck and a clean unmount on a linux box to avoid running Alt-F fsck and the the swap needed.
I'm not sure if fsck will be called in this case, but go to Disk->filesystem unmount the RO marked fs, and edit the mount option to read "default" instead of "ro" and select "Set mnt options" under "FS operations", then mount again...

What is you more worrying issue?

Rolf Pedersen

unread,
Mar 7, 2020, 9:47:46 PM3/7/20
to al...@googlegroups.com


On 03/02/2020 11:38 AM, João Cardoso wrote:





Hi Rolf,
Hi João,

Your post cover many different subjects, so it is difficult to concentrate on the real issue, so a few brief notes:

-reiserfs is not supported under Alt-F, sorry. It was my fs of choice during years.
Yes, I still use it and it is the format of all the Linux storage partitions I am migrating to the new 323.  It's been some time since I set up Alt-F on a NAS and I did not read through the supported filesystem or other howto before jumping in. :P  BTW, I tried with a desktop machine to convert the ~2TB reiserfs partition to ext4 with fstransform, https://github.com/cosmos72/fstransform but it failed for any number of reasons.  I had gone the other way in the past, converted ext3/4 to reiserfs and was impressed. 

-fsck does not supports 64 bit features, which is now common. I have a e2fsck-1.42.13 pkg available, which supports 64 bit features accordingly to its documentation.
I'm reluctant  to make it available, as it has special installation requirements and it might cause troubles: Alt-F has to be installed on a USB pen or on a not otherwise used disk partition, otherwise fsck will "vanish" when the partition is unmounted to be checked. The experienced user will understand that, but might cause issues for normal users, which just install Alt-F packages in their main fs.
Right.  Those partitions were made on the desktop box with a newer e2fsck.  I have since created an ext3 partition and copied the 1.8TB of files there.  That is working.


-Alt-F has to be installed on a ext2/3/4 filesystem, are you using vfat? "Interestingly" enough the destination fs type is checked when you try to copy the current Alt-F to a new fs (using Packages->Alt-F, CopyTo), but it is not detected at install time -- a bug!
Following your notes, I managed to delete the Alt-F folder on vfat and put it on the new ext3 partition.


-Creating Users is not really necessary, but it is "good practice" and useful to identify which is the more probable fs to be used by users. You can skip the first login wizard by just logout after creating the box password.
I have bumbled my way through and am making progress using the new 323 according to my plan to separate the large amount of slightly used storage off the desktop machine.


-swap will only be needed if fsck needs to run, so you can skip that for now. Do a fsck and a clean unmount on a linux box to avoid running Alt-F fsck and the the swap needed.
I'm not sure if fsck will be called in this case, but go to Disk->filesystem unmount the RO marked fs, and edit the mount option to read "default" instead of "ro" and select "Set mnt options" under "FS operations", then mount again...
On both the 4TB and 8TB disk I have shrunk the first partition (with the novice-friendly gparted on a desktop machine) and put a swap partition at the beginning.  Both are being used.


What is you more worrying issue?
I'm making progress, thank you.  I'm now able to access and write to the new ext3 partition from the desktop.  There is an error, 'No fsck command for ntfs-3g' for two ntfs partitions that I can't solve, however.  I've got ntfs-3g and ntfs-3g-ntfsprogs installed, see below.


--
You received this message because you are subscribed to the Google Groups "Alt-F" group.
To unsubscribe from this group and stop receiving emails from it, send an email to alt-f+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/alt-f/7a250331-8ceb-4c98-a486-b213c5235408%40googlegroups.com.

Joao Cardoso

unread,
Mar 8, 2020, 11:01:56 PM3/8/20
to Alt-F


On Sunday, March 8, 2020 at 2:47:46 AM UTC, Rolf Pedersen wrote:


On 03/02/2020 11:38 AM, João Cardoso wrote:





Hi Rolf,
Hi João,

Your post cover many different subjects, so it is difficult to concentrate on the real issue, so a few brief notes:

-reiserfs is not supported under Alt-F, sorry. It was my fs of choice during years.
Yes, I still use it and it is the format of all the Linux storage partitions I am migrating to the new 323.  It's been some time since I set up Alt-F on a NAS and I did not read through the supported filesystem or other howto before jumping in. :P  BTW, I tried with a desktop machine to convert the ~2TB reiserfs partition to ext4 with fstransform, https://github.com/cosmos72/fstransform but it failed for any number of reasons.  I had gone the other way in the past, converted ext3/4 to reiserfs and was impressed. 

-fsck does not supports 64 bit features, which is now common. I have a e2fsck-1.42.13 pkg available, which supports 64 bit features accordingly to its documentation.
I'm reluctant  to make it available, as it has special installation requirements and it might cause troubles: Alt-F has to be installed on a USB pen or on a not otherwise used disk partition, otherwise fsck will "vanish" when the partition is unmounted to be checked. The experienced user will understand that, but might cause issues for normal users, which just install Alt-F packages in their main fs.
Right.  Those partitions were made on the desktop box with a newer e2fsck.  I have since created an ext3 partition and copied the 1.8TB of files there.  That is working.

You can make non-64 bits feature ext4 filesystems. By default, when creating ext4 fs /etc/mke2fs.conf is consulted, and it specify
ext4 = {
                features = has_journal,extent,huge_file,flex_bg,uninit_bg,64bit,dir_nlink,...
 
Probably, specifying "mkfs ... -O^64bit... " (caret means no-64bit) will remove that default option.

You can also convert ext3 to ext4 using the webUI. Lengthy, as it requires a fsck, the conversion, then a new fsck...
-Alt-F has to be installed on a ext2/3/4 filesystem, are you using vfat? "Interestingly" enough the destination fs type is checked when you try to copy the current Alt-F to a new fs (using Packages->Alt-F, CopyTo), but it is not detected at install time -- a bug!
Following your notes, I managed to delete the Alt-F folder on vfat and put it on the new ext3 partition.

-Creating Users is not really necessary, but it is "good practice" and useful to identify which is the more probable fs to be used by users. You can skip the first login wizard by just logout after creating the box password.
I have bumbled my way through and am making progress using the new 323 according to my plan to separate the large amount of slightly used storage off the desktop machine.

-swap will only be needed if fsck needs to run, so you can skip that for now. Do a fsck and a clean unmount on a linux box to avoid running Alt-F fsck and the the swap needed.
I'm not sure if fsck will be called in this case, but go to Disk->filesystem unmount the RO marked fs, and edit the mount option to read "default" instead of "ro" and select "Set mnt options" under "FS operations", then mount again...
On both the 4TB and 8TB disk I have shrunk the first partition (with the novice-friendly gparted on a desktop machine) and put a swap partition at the beginning.  Both are being used.

What is you more worrying issue?
I'm making progress, thank you.  I'm now able to access and write to the new ext3 partition from the desktop.  There is an error, 'No fsck command for ntfs-3g' for two ntfs partitions that I can't solve, however.  I've got ntfs-3g and ntfs-3g-ntfsprogs installed, see below.

Those warnings means that the NTFS fs (sda4/sda6) are discovered before the Alt-F folder (sdb2) being active, so the ntfs-3g-progs package with the ntfs fsck aware program is also not yet available.
I'm afraid that there is no guaranteed working around, other than relocating the Alt-F folder to a ext2/3/4 partition before the ntfs ones, i.e., in sda2 or sda3 (as I'm assuming sda1 is swap). And even so it is not guaranteed that sda2/sda3 is processed before sda4/sda6, e.g., they might need a fsck themselves or some other reason due to the asynchronous system nature.
That's why I don't make a new e2fsck pkg with 64-bit feature available, it is not guaranteed to work when most needed. Only flash-memory pre-installed pkgs are early/always available (and on boxes with a bigger flash-memory (non-DNS-323/321) at least ntfs-3g-progs is flash-memory installed)

 


To unsubscribe from this group and stop receiving emails from it, send an email to alt-f+unsubscribe@googlegroups.com.

Rolf Pedersen

unread,
Mar 15, 2020, 2:53:35 PM3/15/20
to al...@googlegroups.com
I think I'm ok, now.  If I clear the messages after boot, the hd LEDs turn from pinkish to blue and everything is mounted RW.
If I want, I can "Stop all services" and "Check" the ntfs partition under " Disk > Filesytem, then start all services and all functions as needed.
Some day, I might try to move the Alt-F folder from sdb2 to sda2 and see how it goes but
for now, two DNS-323 and one DNS-320 are running Alt-F 1.0 and serving terabytes of storage to the LAN.
Thank you for your help and the ever more impressive Alt-F!
Rolf


To unsubscribe from this group and stop receiving emails from it, send an email to alt-f+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/alt-f/b5151651-44c2-4997-b9fe-87a06dc71e63%40googlegroups.com.

Reply all
Reply to author
Forward
0 new messages