10 replies to this topic

[klorinczi]

I have VU+DUO 4K SE PVR with Openpli v8.3.

I used a 2TB HDD, but I got it filled.

I copied the 2TB EXT4 partition to 3TB HDD, then resized partition to 3TB size.

If I check the resized EXT4 partition with fsck.ext4, it shows a clean filesystem.

But when I put the drive to the external hdd enclosure of VU+DUO 4K SE PVR, it doesn't mount, does not recognize it.

The disk is recognized, the sda1 partition and EXT4 filesystem is not.

ls /dev/sda*
shows only /dev/sda, but not /dev/sda1.

Are 3TB GPT disks supported in OpenPLI v8.3?


What can cause not to mount this 3TB HDD with GPT partition and EXT4 filesystem?

Edited by klorinczi, 15 October 2023 - 16:18.

[WanWizard]

Yes, not a problem, there are people using 10TB or more disks.

 

What is the output of

sfdisk -l /dev/sda

and/or

parted /dev/sda -l

?

 

[klorinczi]

Yes, not a problem, there are people using 10TB or more disks.

 

What is the output of

sfdisk -l /dev/sda

and/or

parted /dev/sda -l

?

 

 

I get the following results:

 

sfdisk -l /dev/sda
Disk /dev/sda: 2.75 TiB, 3000592982016 bytes, 732566646 sectors
Disk model: ASMT1153E
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x96cf96cf


Device     Boot Start        End    Sectors Size Id Type
/dev/sda1           1 4294967295 4294967295  16T ee GPT




parted /dev/sda -l
Error: /dev/sda: unrecognised disk label
Model: asmedia ASMT1153E (scsi)
Disk /dev/sda: 3001GB
Sector size (logical/physical): 4096B/4096B
Partition Table: unknown
Disk Flags:


Error: /dev/mmcblk0rpmb: unrecognised disk label
Warning: Error fsyncing/closing /dev/mmcblk0rpmb: Input/output error
Retry/Ignore? i
Model: Generic SD/MMC Storage Card (sd/mmc)
Disk /dev/mmcblk0rpmb: 524kB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:


Error: /dev/mmcblk0boot0: unrecognised disk label
Model: Generic SD/MMC Storage Card (sd/mmc)
Disk /dev/mmcblk0boot0: 4194kB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:


Error: /dev/mmcblk0boot1: unrecognised disk label
Model: Generic SD/MMC Storage Card (sd/mmc)
Disk /dev/mmcblk0boot1: 4194kB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:


Model: MMC 4FTE4R (sd/mmc)
Disk /dev/mmcblk0: 3909MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:


Number  Start   End     Size    File system  Name     Flags
 1      721kB   786kB   65.5kB               nvram
 2      786kB   852kB   65.5kB               macadr
 3      852kB   918kB   65.5kB               devtree
 4      918kB   983kB   65.5kB               bp30
 5      983kB   1049kB  65.5kB               bp31
 6      1049kB  17.8MB  16.8MB               kernel
 7      17.8MB  34.6MB  16.8MB               initrd
 8      34.6MB  36.7MB  2097kB               splash
 9      36.7MB  3908MB  3871MB  ext4         rootfs

Edited by klorinczi, 15 October 2023 - 16:50.

[WanWizard]

Partition Table: unknown

looks worrying.

 

What does this output:

partprobe /dev/sda -s

 

[klorinczi]

partprobe /dev/sda -s
/dev/sda: msdos partitions

[klorinczi]

Just checked this partition and filesystem with a Gparted LIVE booted from USB, and check found no problem, filesystem is clean.

[WanWizard]

Also, partition type "ee" means "this is a legact MBR partition", so this might as well be the cause.

 

You can change it to a standard linux partition using

sfdisk --part-type /dev/sda 1 83

 

[klorinczi]

Now I get:

fsck.ext4 /dev/sda1 -f
e2fsck 1.45.3 (14-Jul-2019)
ext2fs_open2: Bad magic number in super-block
fsck.ext4: Superblock invalid, trying backup blocks...
fsck.ext4: Bad magic number in super-block while trying to open /dev/sda1

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>


e2fsck -b 32768 /dev/sda1
e2fsck 1.45.3 (14-Jul-2019)
e2fsck: Bad magic number in super-block while trying to open /dev/sda1

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

[WanWizard]

You can change it back using

sfdisk --part-type /dev/sda 1 ee

eitherway, the partitioning of the disk is all off, most likely due to the fact you copied and resized the raw disk partion (which will not work as the old partition was < 2TB and MBR, which is not compatible with larger partitions.

 

If I were you, I restart from scratch. Initialize the new disk in the box via the menu. This creates a correct partition, which is also tuned for large file recordings. And then connect the old disk somewhere, and copy the data across (for example using rsync).

[klorinczi]

I work on windows so rsync will not work.

Copying 3TB took for long time, so I'd like to fix the partition.

 

The data is on the place on ext4 filesytem, the ext4 is clean, just the partition has to be with the correct values, which is accepted by OpenPLI.

[WanWizard]

Good luck.

 

I don't know of any means of changing a partioning system of a disk without impactting the data.

 

I'd download a linux based rescue disk you can flash on USB, and boot your PC with that. It will give you native access to the old disk partition, to the new disk (if connected to the PC too), rsync, and critically, also the correct disk tools.

 

Something like https://www.supergru...k.org/rescatux/ or https://www.system-rescue.org/ (which I use).