Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £99! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £149! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

[VU+ Solo2] HDD no longer mounted

lfc84

Member
Joined
Feb 18, 2011
Messages
72
Reaction score
0
Points
6
I am running Hades for a few weeks and prior to that Apollo and Openvix3.0.8

Hades crashed a few days ago and I think at that time the HDD sata unmounted. I have only just noticed.

Since then I have done a software update using the menu.

/etc/fstab includes the folliwing:

root@vusolo2:~# cat /etc/fstab
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
usbfs /proc/bus/usb usbfs defaults 0 0
UUID=9EDF-B289 /media/hdd auto defaults 0 0


i tried the following

/dev/sda1 /media/hdd auto defaults 0 0
#UUID=9EDF-B289 /media/hdd auto defaults 0 0

rebooted, but no joy !

the menu doesnt allow me to mount the hdd. backups and tv recordings were on the hdd.

Can anyone help please? how can i access the hdd ?

this is the hdd

amazon.co.uk/367/dp/B007NVGWV0/ref=cm_cr_pr_product_top
 
Last edited:
You could try installing fdisk and seeing if your HD is listed

Code:
opkg install util-linux-fdisk

then

Code:
fdisk -l

which should return something similar to:

Code:
Disk [COLOR="#FF0000"]/dev/sda[/COLOR]: 1000.2 GB, 1000204886016 bytes, 1953525168 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
Disk label type: gpt
 
Here's what I get:

Code:
root@vusolo2:~# fdisk -l

Disk /dev/mtdblock0: 235 MB, 235929600 bytes, 460800 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/mtdblock1: 235 MB, 235929600 bytes, 460800 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/mtdblock2: 7 MB, 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: 1 MB, 1048576 bytes, 2048 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
 
no hard disk then... if its internal check the cables. If it's external plug it into a pc and see if it responds.
 
It's internal. I will remove it and try it in my laptop.
 
It's internal. I will remove it and try it in my laptop.

I'd just check/re-seat the cables first and try again... wouldn't be the first or last time that's happened to me with PCs...
 
I'd just check/re-seat the cables first and try again... wouldn't be the first or last time that's happened to me with PCs...


OK, some progress.....

Code:
root@vusolo2:~# fdisk -l
WARNING: fdisk GPT support is currently new, and therefore in an experimental phase. Use at your own discretion.

Disk /dev/sda: 500.1 GB, 500107862016 bytes, 976773168 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 label type: gpt


#         Start          End    Size  Type            Name
 1         2048    976773119  465.8G  Microsoft basic primary

Disk /dev/mtdblock0: 235 MB, 235929600 bytes, 460800 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/mtdblock1: 235 MB, 235929600 bytes, 460800 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/mtdblock2: 7 MB, 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: 1 MB, 1048576 bytes, 2048 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


The HDD should be 1TB.

What do i do next to try and avoid formatting the disc
 
Last edited:
I would uncouple the HDD and do a full reflash off the box.Try to get it working again and then couple HDD again.In NO CASE do a FORMAT even if requested.
 
I would uncouple the HDD and do a full reflash off the box.Try to get it working again and then couple HDD again.In NO CASE do a FORMAT even if requested.

A reflash of the image, will still need me to Initialise the disk. This will start a format. So hoping for other solutions
 
A reflash of the image, will still need me to Initialise the disk. This will start a format. So hoping for other solutions

A reflash of the image DOES NOT require you to initialize the disc unless you choose to do so.
 
Ah, I stand corrected. I'll reflash and report back
 
if you doubt use openvix image.That one NEVER initialises the HDD. I sometimes change the HDD in my box for another and never had to initialize.Just mount with vix mount manager.
 
OK, I'm just about to reflash with openvix-Hades.010.release-vusolo2_usb.zip
 
As Larry-G has said, a full flash will not cause an initialize of the disk.

In fact, I generally always do a full flash (with no restore of settings) and it always automatically mounts my internal HDD without me doing anything at all.
 
I found a backup that I had archived to my laptop named "openvix-vusolo2-Hades.007-20150511_184258.zip". It's from the start of May before the problems began.

I have reflashed with the backup image with the HDD connected but the box hung on boot up just showing the purple "Vu+ Your Smart Linux Tv Player" boot logo. After about 5 minutes I gave up and then I then reflashed with the Hades007 backup image with the HDD disconnected. This also hung at the same point.

I am going to try a new install of the Hade010 image now.
 
I have now flashed with a new install of Hades010 (downloaded the release image from the Openvix server). I have the HDD disconnected during the reflash.

Please advise me what to do next. Thanks appreciate the help.
 
I would have kept internal HDD connected and flashed fresh 010 as that's what I do all the time. It mounts itself so no need to do anything usually with your HDD.
 
I would have kept internal HDD connected and flashed fresh 010 as that's what I do all the time. It mounts itself so no need to do anything usually with your HDD.

I have flashed Hades010 release with the HDD connected. What would you recommend now? Thanks


Code:
root@vusolo2:~# df -h
Filesystem                Size      Used Available Use% Mounted on
ubi0:rootfs             194.8M     73.1M    121.6M  38% /
devtmpfs                279.4M      8.0K    279.4M   0% /dev
tmpfs                    64.0K         0     64.0K   0% /media
/dev/sdb1                 3.8G     88.1M      3.7G   2% /media/hdd
tmpfs                   279.6M    120.0K    279.4M   0% /var/volatile
root@vusolo2:~#
root@vusolo2:~#
root@vusolo2:~# cat /etc/fstab
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
usbfs                /proc/bus/usb        usbfs      defaults              0  0
root@vusolo2:~#

/dev/sb1 is the USB drive.

The HDD doesn't seem to have auto mounted
 
Last edited:
try to use blue button and mountmanager
 

OpenViX Feeds Status

Back
Top