HDD/Partition initialization problems

[jaker]

Hi
I've encountered a problem with Network Space, the one with only one HDD. After performing a clean install from laptop/Console, it does not seem to be able to initialize disk correctly. I added 2TB hard drive into this one and it seems to get recognized correctly, only formatting isn't working.

System information shows Available storage as 0GB.

info.png

Disk setup/Manage disks and volumes does not show anything on Format Type, Total Size or Free Size columns.

info2.png

I tried to start over from scratch twice, but this problem still exists.

Initialize disks and volumes gives following errors

Code: Select all

NAS server in Setup Mode
(re-)Start the setup task :   Format data partition
Started on:   03 August 2020, 19:06:18

Ended at:   03 August 2020, 19:24:41

Setup task format.sh is now running
Found disk: sda(S2H7JD1ZA20706)
Format partition sda8 with file system ext4:
=>mke2fs 1.43.4 (31-Jan-2017)
Creating filesystem with 487653137 4k blocks and 121913344 inodes
Filesystem UUID: f995fc35-759e-4d87-8de6-d000f5a5d5f1
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848
Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done
set label on the data volume successful (Vol-A)
=>Fail (set ext4 file system on sda8 failed)


or

Code: Select all

NAS server in Setup Mode
(re-)Start the setup task :   Reset internal disk(s)
Started on:   03 August 2020, 19:46:33

Ended at:   03 August 2020, 20:04:51

Setup task reset.sh is now running
Found disk: sda(S2H7JD1ZA20706)
Format partition sda8 with file system ext4:
=>mke2fs 1.43.4 (31-Jan-2017)
Creating filesystem with 487653137 4k blocks and 121913344 inodes
Filesystem UUID: d796a679-625a-4b19-8d55-ff71b75f4afb
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848
Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done
=>Fail (set ext4 file system on sda8 failed)


By opening SSH connection I was able to use mke2fs commands as mentioned in another post. These seem to be succesful, but it didn't make any change to webUI contents. It still does not show anything on Format Type, Total Size or Free Size columns.

Code: Select all

root@fvdwsl-base:/ # mke2fs -m 1 -j /dev/sda8
mke2fs 1.43.4 (31-Jan-2017)
/dev/sda8 contains `Linux rev 1.0 ext3 filesystem data, UUID=71d3c4c0-4b60-488a-ac60-abab45e549b8, volume name "Vol-A" (large files)' data
Proceed anyway? (y,N) y
Creating filesystem with 487653137 4k blocks and 121913344 inodes
Filesystem UUID: 4223e373-3823-41d3-9e26-111593e7b103
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
        102400000, 214990848

Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done

root@fvdwsl-base:/ # reboot


and

Code: Select all

root@fvdwsl-base:/ # mke2fs -t ext4 /dev/sda8
mke2fs 1.43.4 (31-Jan-2017)
/dev/sda8 contains `Linux rev 1.0 ext4 filesystem data, UUID=d796a679-625a-4b19-8d55-ff71b75f4afb (extents) (large files) (huge files)' data
Proceed anyway? (y,N) y
Creating filesystem with 487653137 4k blocks and 121913344 inodes
Filesystem UUID: 8119de2d-72b3-4f02-8343-b2b09bf288a9
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
        102400000, 214990848

Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done

root@fvdwsl-base:/ #


My Linux skills aren't that good that I could handle this by myself. Has someone encountered anything similar?

[Jocko]

Hi

I added 2TB hard drive into this one and it seems to get recognized correctly

So post this output:

Code: Select all

cat /proc/partitions
fdisk -l /dev/sda
file -bs /dev/sda8

According with your first output, it seems up to the label step all is ok

Code: Select all

set label on the data volume successful (Vol-A)

as the returned message on this step is not

Code: Select all

=>Fail (set ext4 file system on sda8 failed)

that means this step is also successful and then the issue is on the next step : check the real fs type on the partition before ending the setup job.

in this case that means blkid command would not return the expected output (ext4).

So repeat the format task and after failing can you run the following command

Code: Select all

/usr/sbin/blkid -o value -s TYPE /dev/sda8

[jaker]

Code: Select all

cat /proc/partitions
major minor  #blocks  name

   1        0       4096 ram0
   1        1       4096 ram1
   1        2       4096 ram2
   1        3       4096 ram3
   1        4       4096 ram4
   1        5       4096 ram5
   1        6       4096 ram6
   1        7       4096 ram7
   1        8       4096 ram8
   1        9       4096 ram9
   1       10       4096 ram10
   1       11       4096 ram11
   1       12       4096 ram12
   1       13       4096 ram13
   1       14       4096 ram14
   1       15       4096 ram15
  31        0        500 mtdblock0
  31        1          4 mtdblock1
   8        0 1953514584 sda
   8        1     524288 sda1
   8        2     524288 sda2
   8        3     524288 sda3
   8        4       8192 sda4
   8        5     786432 sda5
   8        6       8192 sda6
   8        7     524288 sda7
   8        8 1950612551 sda8
root@fvdwsl-base:/ #


Code: Select all

fdisk -l /dev/sda

Disk /dev/sda: 2000.3 GB, 2000398934016 bytes
256 heads, 63 sectors/track, 242251 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1               1      242252  1953514583+ ee EFI GPT
root@fvdwsl-base:/ #


Code: Select all

file -bs /dev/sda8
Linux rev 1.0 ext4 filesystem data, UUID=8119de2d-72b3-4f02-8343-b2b09bf288a9 (extents) (large files) (huge files)
root@fvdwsl-base:/ #


I'll start the formatting and reply when it is finished.

format_from_GUI.png

Edit: Format related prints:

Code: Select all

NAS server in Setup Mode

(re-)Start the setup task :   Format data partition
Started on:   04 August 2020, 16:10:48
Ended at:   04 August 2020, 16:29:06

Setup task format.sh is now running
Found disk: sda(S2H7JD1ZA20706)
Format partition sda8 with file system ext4:
=>mke2fs 1.43.4 (31-Jan-2017)
Creating filesystem with 487653137 4k blocks and 121913344 inodes
Filesystem UUID: 011368da-0fa7-4c14-b112-8c0c7a88fdaf
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848
Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done
set label on the data volume successful (Vol-A)
=>Fail (set ext4 file system on sda8 failed)

[jaker]

This didn't return anything.

Code: Select all

/usr/sbin/blkid -o value -s TYPE /dev/sda8
root@fvdwsl-base:/ #


[jaker]

And reason for not returning anything might be here. blkid command does not list SDA8 at all.

Code: Select all

root@fvdwsl-base:/ # /usr/sbin/blkid
/dev/sda1: UUID="7787a480-26cb-45a7-97f1-9bb09014b115" TYPE="ext3" PARTLABEL="Linux filesystem" PARTUUID="00000000-0000-0000-0000-000000000000"
/dev/sda2: PARTLABEL="Linux filesystem" PARTUUID="00000000-0000-0000-0000-000000000000"
/dev/sda3: UUID="f37d5416-5711-4dbe-a0b9-f9901b824154" TYPE="swap" PARTLABEL="Linux swap" PARTUUID="00000000-0000-0000-0000-000000000000"
/dev/sda4: PARTLABEL="Linux filesystem" PARTUUID="00000000-0000-0000-0000-000000000000"
/dev/sda5: UUID="185670ca-a72a-4b19-b057-49f422536585" TYPE="ext3" PARTLABEL="Linux filesystem" PARTUUID="00000000-0000-0000-0000-000000000000"
/dev/sda6: PARTLABEL="Linux filesystem" PARTUUID="00000000-0000-0000-0000-000000000000"
/dev/sda7: UUID="2dcbcd7b-bde4-4915-97cb-7b9dd89a4739" TYPE="ext3" PARTLABEL="Linux filesystem" PARTUUID="00000000-0000-0000-0000-000000000000"
root@fvdwsl-base:/ # /usr/sbin/blkid -o value
7787a480-26cb-45a7-97f1-9bb09014b115
ext3
Linux filesystem
00000000-0000-0000-0000-000000000000
Linux filesystem
00000000-0000-0000-0000-000000000000
f37d5416-5711-4dbe-a0b9-f9901b824154
swap
Linux swap
00000000-0000-0000-0000-000000000000
Linux filesystem
00000000-0000-0000-0000-000000000000
185670ca-a72a-4b19-b057-49f422536585
ext3
Linux filesystem
00000000-0000-0000-0000-000000000000
Linux filesystem
00000000-0000-0000-0000-000000000000
2dcbcd7b-bde4-4915-97cb-7b9dd89a4739
ext3
Linux filesystem
00000000-0000-0000-0000-000000000000
root@fvdwsl-base:/ # /usr/sbin/blkid -o value -s TYPE
ext3
swap
ext3
ext3
root@fvdwsl-base:/ #


[Jocko]

So the issue is only on blkid command... But why ???

I think the best way is to upgrade again the firmware to have a clean environment : go to the upgrade menu and force it even if it claims you have the latest version.

So after upgrading, try the command blkid and see if it returns an output with sda8. If yes reset again the volume

---edit---
our firmware does not cache blkid information and then on running blkid scans the content of /dev

Code: Select all

lstat64("/dev", {st_mode=S_IFDIR|0755, st_size=12288, ...}) = 0

. can you check before upgrading if sda8 device node is present

Code: Select all

ls -l /dev/sda*

[jaker]

Code: Select all

root@fvdwsl-base:/ #  ls -l /dev/sda*
brw-rw----  1 root root 8, 0 2008-01-03 20:06 /dev/sda
brw-rw----  1 root root 8, 1 2008-01-03 20:06 /dev/sda1
brw-rw----  1 root root 8, 2 2008-01-03 20:06 /dev/sda2
brw-rw----  1 root root 8, 3 2020-08-05 15:51 /dev/sda3
brw-rw----  1 root root 8, 4 2008-01-03 20:06 /dev/sda4
brw-rw----  1 root root 8, 5 2008-01-03 20:06 /dev/sda5
brw-rw----  1 root root 8, 6 2008-01-03 20:06 /dev/sda6
brw-rw----  1 root root 8, 7 2008-01-03 20:06 /dev/sda7
brw-rw----  1 root root 8, 8 2020-08-04 16:29 /dev/sda8
brw-rw-rw-  1 root root 8, 9 2013-08-09 19:22 /dev/sda9
root@fvdwsl-base:/ #


Hmm. I wasn't sure if you wanted me to run the first command, but I did it anyway. It had some problem

Code: Select all

root@fvdwsl-base:/ # lstat64("/dev", {st_mode=S_IFDIR|0755, st_size=12288, ...})
 = 0
-sh: syntax error: unexpected word (expecting ")")
root@fvdwsl-base:/ #


I'll start the update now.

Edit:
After first install I did perform the update to 18.2. but with second attempt I didn't do the update. So the device has now 18.1. and I'm updating to 18.2

[jaker]

After performing the update from 18.1 to 18.2 I opened the SSH connection and gave following command.

Code: Select all

root@fvdwsl-base:/ # /usr/sbin/blkid -o value -s TYPE /dev/sda8
root@fvdwsl-base:/ #


It didn't give anything.

I entered also following commands which gave same results as before. It does not mention SDA8.

Code: Select all

root@fvdwsl-base:/ # /usr/sbin/blkid -o value -s TYPE /dev/sda8
root@fvdwsl-base:/ # /usr/sbin/blkid
/dev/sda1: UUID="45f338fc-3b44-4d2d-8eea-cf636f69b5d4" TYPE="ext3" PARTLABEL="Linux filesystem" PARTUUID="00000000-0000-0000-0000-000000000000"
/dev/sda2: PARTLABEL="Linux filesystem" PARTUUID="00000000-0000-0000-0000-000000000000"
/dev/sda3: UUID="ed71634f-384d-444c-81c4-9c247ab0ae8d" TYPE="swap" PARTLABEL="Linux swap" PARTUUID="00000000-0000-0000-0000-000000000000"
/dev/sda4: PARTLABEL="Linux filesystem" PARTUUID="00000000-0000-0000-0000-000000000000"
/dev/sda5: UUID="185670ca-a72a-4b19-b057-49f422536585" TYPE="ext3" PARTLABEL="Linux filesystem" PARTUUID="00000000-0000-0000-0000-000000000000"
/dev/sda6: PARTLABEL="Linux filesystem" PARTUUID="00000000-0000-0000-0000-000000000000"
/dev/sda7: UUID="2dcbcd7b-bde4-4915-97cb-7b9dd89a4739" TYPE="ext3" PARTLABEL="Linux filesystem" PARTUUID="00000000-0000-0000-0000-000000000000"
root@fvdwsl-base:/ # /usr/sbin/blkid -o value
45f338fc-3b44-4d2d-8eea-cf636f69b5d4
ext3
Linux filesystem
00000000-0000-0000-0000-000000000000
Linux filesystem
00000000-0000-0000-0000-000000000000
ed71634f-384d-444c-81c4-9c247ab0ae8d
swap
Linux swap
00000000-0000-0000-0000-000000000000
Linux filesystem
00000000-0000-0000-0000-000000000000
185670ca-a72a-4b19-b057-49f422536585
ext3
Linux filesystem
00000000-0000-0000-0000-000000000000
Linux filesystem
00000000-0000-0000-0000-000000000000
2dcbcd7b-bde4-4915-97cb-7b9dd89a4739
ext3
Linux filesystem
00000000-0000-0000-0000-000000000000
root@fvdwsl-base:/ # /usr/sbin/blkid -o value -s TYPE
ext3
swap
ext3
ext3
root@fvdwsl-base:/ #


However it seems to exist also after update

Code: Select all

root@fvdwsl-base:/ # ls -l /dev/sda*
brw-rw----  1 root root 8, 0 2008-01-03 20:06 /dev/sda
brw-rw----  1 root root 8, 1 2008-01-03 20:06 /dev/sda1
brw-rw----  1 root root 8, 2 2008-01-03 20:06 /dev/sda2
brw-rw----  1 root root 8, 3 2020-08-05 17:07 /dev/sda3
brw-rw----  1 root root 8, 4 2008-01-03 20:06 /dev/sda4
brw-rw----  1 root root 8, 5 2008-01-03 20:06 /dev/sda5
brw-rw----  1 root root 8, 6 2008-01-03 20:06 /dev/sda6
brw-rw----  1 root root 8, 7 2008-01-03 20:06 /dev/sda7
brw-rw----  1 root root 8, 8 2014-05-30 09:19 /dev/sda8
brw-rw-rw-  1 root root 8, 9 2013-08-09 19:22 /dev/sda9
root@fvdwsl-base:/ #


Let me know if I could provide some more information about this problem.

[fvdw]

Code: Select all

df -h
mount
/usr/sbin/blkid -v
busybox blkid /dev/sda8
gdisk -l /dev/sda

What does these commands give as output?

Ps. The fact that all partition id's are 0 is also not normal, in fact blkid command should normally not list this..

However it seems to exist also after update..

The command ls /dev/sd* will only show if the file /dev/sda8 exist or not, it is a device node. It is not proff that the partition exists
It cannot be used to connect to the partition in case the partition doesn't exist.
The command cat /proc/partitions will reveal if sda8 exists or not. Must be something with blkid command you use. Did you install another version ??

[jaker]

Hi

Here you go

Code: Select all

root@fvdwsl-base:/ # df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1       488M  147M  337M  31% /
/dev/sda5       740M  1.3M  732M   1% /rw_fs
tmpfs           4.9M   96K  4.8M   2% /rw_fs/tmp/usr/var
/dev/root       488M  147M  337M  31% /lacie-boot
root@fvdwsl-base:/ # mount
/dev/sda1 on / type ext3 (rw,relatime,data=ordered)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
none on /dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000)
/dev/sda5 on /rw_fs type ext3 (rw,noatime,data=ordered)
tmpfs on /rw_fs/tmp/usr/var type tmpfs (rw,relatime,size=5000k)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
/dev/sda7 on /lacie-boot type ext3 (rw,relatime,data=ordered)
root@fvdwsl-base:/ # /usr/sbin/blkid -v
blkid from util-linux 2.30  (libblkid 2.30.0, 02-Jun-2017)
root@fvdwsl-base:/ # busybox blkid /dev/sda8
/dev/sda8: LABEL="Vol-A" UUID="011368da-0fa7-4c14-b112-8c0c7a88fdaf"
root@fvdwsl-base:/ # gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.5

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 3907029168 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 00000000-0000-0000-0000-000000000000
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 2048-sector boundaries
Total free space is 4062 sectors (2.0 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            4096         1052671   512.0 MiB   8300  Linux filesystem
   2         1052672         2101247   512.0 MiB   8300  Linux filesystem
   3         2101248         3149823   512.0 MiB   8200  Linux swap
   4         3149824         3166207   8.0 MiB     8300  Linux filesystem
   5         3166208         4739071   768.0 MiB   8300  Linux filesystem
   6         4739072         4755455   8.0 MiB     8300  Linux filesystem
   7         4755456         5804031   512.0 MiB   8300  Linux filesystem
   8         5804032      3907029134   1.8 TiB     8300  Linux filesystem
root@fvdwsl-base:/ #


Code: Select all

root@fvdwsl-base:/ # cat /proc/partitions
major minor  #blocks  name

   1        0       4096 ram0
   1        1       4096 ram1
   1        2       4096 ram2
   1        3       4096 ram3
   1        4       4096 ram4
   1        5       4096 ram5
   1        6       4096 ram6
   1        7       4096 ram7
   1        8       4096 ram8
   1        9       4096 ram9
   1       10       4096 ram10
   1       11       4096 ram11
   1       12       4096 ram12
   1       13       4096 ram13
   1       14       4096 ram14
   1       15       4096 ram15
  31        0        500 mtdblock0
  31        1          4 mtdblock1
   8        0 1953514584 sda
   8        1     524288 sda1
   8        2     524288 sda2
   8        3     524288 sda3
   8        4       8192 sda4
   8        5     786432 sda5
   8        6       8192 sda6
   8        7     524288 sda7
   8        8 1950612551 sda8
root@fvdwsl-base:/ #