Jump to content


Photo

Strange mount problem

DM8000 mount

  • Please log in to reply
7 replies to this topic

#1 stdemonac

  • Senior Member
  • 52 posts

0
Neutral

Posted 21 January 2021 - 22:33

Dear all,

 

I try to install a brand new HDD in my DM8000 but I just can't mount it.

 

The current image is openpli-7.3-release-dm8000-20210119 (flashed from openpli-8.0-release-dm8000-20210111).

 

First, some useful information about the HDD:

root@dm8000:~# smartctl -i /dev/sda
smartctl 5.42 2011-10-20 r3458 [mips-linux-3.2-dm8000] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:     ST4000DM004-2CV104
Serial Number:    WFN3DVPM
LU WWN Device Id: 5 000c50 0cf46a884
Firmware Version: 0001
User Capacity:    4,000,787,030,016 bytes [4.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ACS-3 (unknown minor revision code: 0x006d)
Local Time is:    Thu Jan 21 20:44:52 2021 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
root@dm8000:~# blkid
/dev/sda1: UUID="896dfc9b-9145-4471-a7da-e04a3f5197d1" TYPE="ext4"
/dev/sdc1: UUID="a82aa934-989a-4d8d-8490-dc74d3d20a17" TYPE="ext4"
root@dm8000:~# tune2fs -l /dev/sda1 | grep -e UUID -e features
Filesystem UUID:          896dfc9b-9145-4471-a7da-e04a3f5197d1
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype extent 64bit flex_bg sparse_super large_file huge_file dir_nlink extra_isize metadata_csum

It seems to be clean (even if some strange unknown devices are present):

root@dm8000:~# parted --list
Model: ATA ST4000DM004-2CV1 (scsi)
Disk /dev/sda: 4001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name     Flags
 1      1049kB  4001GB  4001GB  ext4         primary


Model: Generic USB CF Reader (scsi)
Disk /dev/sdc: 4012MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number  Start  End     Size    Type     File system  Flags
 1      512B   4012MB  4012MB  primary  ext4


Error: /dev/mtdblock0: unrecognised disk label
Model: Unknown (unknown)
Disk /dev/mtdblock0: 268MB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:

Error: /dev/mtdblock1: unrecognised disk label
Model: Unknown (unknown)
Disk /dev/mtdblock1: 1049kB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:

Error: /dev/mtdblock2: unrecognised disk label
Model: Unknown (unknown)
Disk /dev/mtdblock2: 7340kB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:

Error: /dev/mtdblock3: unrecognised disk label
Model: Unknown (unknown)
Disk /dev/mtdblock3: 260MB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:
root@dm8000:~# cat /proc/partitions
major minor  #blocks  name
  31        0     262144 mtdblock0
  31        1       1024 mtdblock1
  31        2       7168 mtdblock2
  31        3     253952 mtdblock3
   8        0 3907018584 sda
   8        1 3907016704 sda1
   8       32    3917592 sdc
   8       33    3917591 sdc1
root@dm8000:~# e2fsck -f -v /dev/sda1
e2fsck 1.43.4 (31-Jan-2017)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

          12 inodes used (0.00%, out of 476944)
           0 non-contiguous files (0.0%)
           0 non-contiguous directories (0.0%)
             # of inodes with ind/dind/tind blocks: 0/0/0
             Extent depth histogram: 3/1
      384381 blocks used (0.04%, out of 976754176)
           0 bad blocks
           1 large file

           0 regular files
           3 directories
           0 character device files
           0 block device files
           0 fifos
           0 links
           0 symbolic links (0 fast symbolic links)
           0 sockets
------------
           3 files

My /etc/fstab is:

root@dm8000:~# more /etc/fstab
UUID=896dfc9b-9145-4471-a7da-e04a3f5197d1    /media/hdd         auto     defaults              0  0
UUID=a82aa934-989a-4d8d-8490-dc74d3d20a17    /media/cf          auto     defaults              0  0
rootfs               /                    auto       defaults              1  1
proc                 /proc                proc       defaults              0  0
devpts               /dev/pts             devpts     mode=0620,gid=5       0  0
usbdevfs             /proc/bus/usb        usbdevfs   noauto                0  0
tmpfs                /var/volatile        tmpfs      defaults              0  0

Mount points are created:

root@dm8000:~# ls -l /media/
drwxr-xr-x    8 root     root          4096 Jan 21 19:45 cf
drwxr-xr-x    2 root     root            40 Jan 21 20:16 hdd

But the mount command fails :

root@dm8000:~# mount /dev/sda1 /media/hdd
NTFS signature is missing.
Failed to mount '/dev/sda1': Invalid argument
The device '/dev/sda1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
FUSE exfat 1.2.3
ERROR: exFAT file system is not found.
mount: mounting /dev/sda1 on /media/hdd failed: Invalid argument

Some other log:

root@dm8000:~# ACTION=add MDEV=sda1 sh -x /etc/mdev/mdev-mount.sh
+ log -------[ add sda1 ] -------------
+ return
+ [ -z add ]
+ cat /proc/cmdline
+ sed -e s/^.*root=\/dev\/// -e s/ .*$//
+ BOOTDEV=ubi.mtd=root
+ log > BOOTDEV = ubi.mtd=root
+ return
+ [ sda1 == ubi.mtd=root ]
+ DEVBASE=sda1
+ log > DEVBASE = sda1
+ return
+ [[ ubi.mtd=root == sda1* ]]
+ [ ! -d /sys/block/sda1 ]
+ DEVBASE=sda
+ log > DEVBASE = sda
+ return
+ [ -f /dev/nomount.sda ]
+ [ sda == sda1 ]
+ get_blkid
+ blkid /dev/sda1
+ cut -d : -f 2+
grep sda1
+ eval UUID="896dfc9b-9145-4471-a7da-e04a3f5197d1" TYPE="ext4"
+ UUID=896dfc9b-9145-4471-a7da-e04a3f5197d1 TYPE=ext4
+ log > device TYPE = ext4
+ return
+ log > device UUID = 896dfc9b-9145-4471-a7da-e04a3f5197d1
+ return
+ log > device LABEL =
+ return
+ [ -z ext4 ]
+ [ ext4 == swap ]
+ [ -f /sys/block/sda/device/model ]
+ cat /sys/block/sda/device/model
+ MODEL=ST4000DM004-2CV1
+ log > MODEL = ST4000DM004-2CV1
+ return
+ mount /dev/sda1
+ log ! device could not be mounted
+ return
+ fstab_mountpoint
+ local mountpoint
+ grep+ awk {print $2}
 ^/dev/sda1\s /etc/fstab
+ mountpoint=
+ [ -z  ]
+ grep ^LABEL=\s /etc/fstab
+ awk {print $2}
+ mountpoint=
+ [ -z  ]
+ grep ^UUID=896dfc9b-9145-4471-a7da-e04a3f5197d1\s+  /etc/fstabawk {print $2}

+ mountpoint=/media/hdd
+ echo /media/hdd
+ MOUNTPOINT=/media/hdd
+ [ ! -z /media/hdd ]
+ samba_share /media/hdd ST4000DM004-2CV1
+ [ ! -f /etc/init.d/samba.sh ]
+ local path=/media/hdd
+ basename /media/hdd
+ local mountpoint=hdd
+ local model=ST4000DM004-2CV1
+ local share
+ [ hdd == hdd ]
+ mountpoint=Harddisk
+ log > add SAMBA share for Harddisk
+ return
+ [ add == add ]
+ find /etc/samba -name *.conf -exec grep path\s*=\s*/media/hdd {} ;
+ share=  path = /media/hdd
+ [ -z   path = /media/hdd ]
+ log ! share for /media/hdd already exists
+ return
+ return
+ log ! exit, device was already mounted outside mdev
+ return
+ exit 0
root@dm8000:~# cat /proc/mounts
rootfs / rootfs rw 0 0
ubi0:rootfs / ubifs rw,relatime 0 0
devtmpfs /dev devtmpfs rw,relatime,size=74540k,nr_inodes=18635,mode=755 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /media tmpfs rw,relatime,size=64k 0 0
fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0
tmpfs /var/volatile tmpfs rw,relatime 0 0
/dev/sdc1 /media/cf ext4 rw,noatime,barrier=1,data=ordered 0 0
devpts /dev/pts devpts rw,relatime,gid=5,mode=620 0 0
nfsd /proc/fs/nfsd nfsd rw,relatime 0 0

I attach the dmesg file.

Any advice ?

 

 

 

Attached Files


DM8000 - 2 DVB-S2 tuners - 1 DVB-C tuner - OpenPLi 7.3


Re: Strange mount problem #2 Dimitrij

  • PLi® Core member
  • 7,577 posts

+247
Excellent

Posted 22 January 2021 - 06:01

Please answer

sfdisk -l

 


Duo 4K/Lunix3-4K/Solo 4K


Re: Strange mount problem #3 stdemonac

  • Senior Member
  • 52 posts

0
Neutral

Posted 22 January 2021 - 10:30

Thanks for looking. Here you are :

root@dm8000:~# sfdisk -l
Disk /dev/mtdblock2: 7 MiB, 7340032 bytes, 14336 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/mtdblock3: 248 MiB, 260046848 bytes, 507904 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/sda: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 593BB782-65C4-440A-9B8F-544EB0B32746

Device     Start        End    Sectors  Size Type
/dev/sda1   2048 7814035455 7814033408  3.7T Linux filesystem


Disk /dev/sdc: 3.8 GiB, 4011614208 bytes, 7835184 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: dos
Disk identifier: 0x00000000

Device     Boot Start     End Sectors  Size Id Type
/dev/sdc1           1 7835183 7835183  3.8G 83 Linux


DM8000 - 2 DVB-S2 tuners - 1 DVB-C tuner - OpenPLi 7.3


Re: Strange mount problem #4 Dimitrij

  • PLi® Core member
  • 7,577 posts

+247
Excellent

Posted 22 January 2021 - 10:56

Disklabel type: gpt

Maybe the problem is here?


Duo 4K/Lunix3-4K/Solo 4K


Re: Strange mount problem #5 WanWizard

  • PLi® Core member
  • 57,692 posts

+1,234
Excellent

Posted 22 January 2021 - 15:40

Could also the 4K sectors, the DM8000 has an antique kernel.

GPT is enabled in the defconfig, so that shouldn't be it. I assume parted would also not work if not enabled in the kernel.

 

edit: disk is using 512 sector emulation, so that's not it either. Besides that, advanced format is supported in kernel 2.6+.


Edited by WanWizard, 22 January 2021 - 15:42.

Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2+fallback), Octagon SF8008 (S2+T2), Zgemma H9.2H (T2+fallback)

Many answers to your question can be found in our new and improved wiki.

Because to health reasons, I will not be active online very often anymore.


Re: Strange mount problem #6 betacentauri

  • PLi® Core member
  • 6,911 posts

+298
Excellent

Posted 22 January 2021 - 18:59

Have you formatted the HDD in the box?
What happens when you reformat it via command line?
Xtrend ET-9200, ET-8000, ET-10000, OpenPliPC on Ubuntu 12.04

Re: Strange mount problem #7 stdemonac

  • Senior Member
  • 52 posts

0
Neutral

Posted 22 January 2021 - 20:49

 

SOLVED ! :)

 

Have you formatted the HDD in the box?

Well, I just finished initialized it from the menu Parameters > System > Expert > Hard Drive > Initialize. And ... it worked !

At first, I tried the same process but from the image openpli-8.0-release-dm8000-20210111. As that didn't work, I formatted it

from my desktop (Kubuntu 20.10) with the KDE Partition Manager, inserted it in my DM8000 (re-flashed with

openpli-7.3-release-dm8000-20210119 because I read this comment), and tried a Verify Filesystem but I got an error at 99% (on mounting the device).
I tried again from a shell with the problem listed above. I didn't think re-format it again :(.

 

Apart from the UUID, the parameters shown from the different commands (tunefs, parted, sfdisk) above are exactly the same.

 

Thanks all for your help !


Edited by stdemonac, 22 January 2021 - 20:52.

DM8000 - 2 DVB-S2 tuners - 1 DVB-C tuner - OpenPLi 7.3


Re: Strange mount problem #8 WanWizard

  • PLi® Core member
  • 57,692 posts

+1,234
Excellent

Posted 22 January 2021 - 22:07

The problem with verifying the filesystem is that it needs lots of memory, especially on big disks. More memory than the box has, which is why you get the error...


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2+fallback), Octagon SF8008 (S2+T2), Zgemma H9.2H (T2+fallback)

Many answers to your question can be found in our new and improved wiki.

Because to health reasons, I will not be active online very often anymore.






Also tagged with one or more of these keywords: DM8000, mount

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users