View Full Version : [VU+ Solo2] HDD no longer mounted
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
You could try installing fdisk and seeing if your HD is listed
opkg install util-linux-fdisk
then
fdisk -l
which should return something similar to:
Disk /dev/sda: 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:
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.....
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
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
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
try to use blue button and mountmanager
try to use blue button and mountmanager
I went into mountmanager, and tried "use as hdd" and "mount" both fail.
Am I doing this wrong ? Any other ideas?
Here's what I currently get
root@vusolo2:/dev# 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
root@vusolo2:/dev# fsck /dev/sda1
fsck from util-linux 2.23.2
e2fsck 1.42.9 (28-Dec-2013)
/dev/sda1: recovering journal
Error reading block 33565858 (Attempt to read block from filesystem resulted in short read). Ignore error<y>? yes
Force rewrite<y>? no
fsck.ext4: Filesystem too large to use legacy bitmaps while trying to re-open /dev/sda1
/dev/sda1: ********** WARNING: Filesystem still has errors **********
I have successfully mounted the drive using command line. GUI didn't work. Now I get this:
root@vusolo2:/dev# df -h
Filesystem Size Used Available Use% Mounted on
ubi0:rootfs 194.8M 75.2M 119.5M 39% /
devtmpfs 279.4M 8.0K 279.4M 0% /dev
tmpfs 64.0K 0 64.0K 0% /media
tmpfs 279.6M 168.0K 279.4M 0% /var/volatile
/dev/sda1 465.6G 271.7G 192.9G 58% /media/hdd
I can now see the tv programmes that I recorded.
I am running a fsck now.
Thanks for everyone's help.
OK, some progress.....
<snip>
The HDD should be 1TB.
In my sheer panic to revoer the HDD in the Solo2 I forgot that the 1TB is in my laptop and the disc in the Solo2 is correctly identified as a 500GB.
Thanks again for all the help
I recently upgraded to Hades 11
Just went into recorded movies to find my whole 1TB hard drive is wiped. Did not initialize it and can't figure out how it happened. Hard drive was close to full but have lost all recordings and backups. Only folders now showing are time shift, movie, var and crossepg.
Anybody here come across anything similar?
I recently upgraded to Hades 11
Just went into recorded movies to find my whole 1TB hard drive is wiped. Did not initialize it and can't figure out how it happened. Hard drive was close to full but have lost all recordings and backups. Only folders now showing are time shift, movie, var and crossepg.
Anybody here come across anything similar?
HDD not mounted correctly.
Check blue button -> ViX > Mount Manager, take a screenshot & add to this post if you need help with the resulting mountpoints.
Thanks, but hdd is mounted fine. I can record on it and see new recording in movie folder. It is the only file there as rest have disappeared.
just updated my solo to hades 11 and both my usb have unmounted and when i try to mount them just get the screen of death thanks
just updated my solo to hades 11 and both my usb have unmounted and when i try to mount them just get the screen of death thanks
start a new thread support thread with all relevant information.
I recently upgraded to Hades 11
Just went into recorded movies to find my whole 1TB hard drive is wiped. Did not initialize it and can't figure out how it happened. Hard drive was close to full but have lost all recordings and backups. Only folders now showing are time shift, movie, var and crossepg.
Anybody here come across anything similar?
It just happened again overnight! HDD is mounted but all recordings I made since are gone. Think I will have to move back to earlier version.
Andy_Hazza
05-06-15, 14:11
You must be doing something wrong. I have 4 boxes, all with HDDs and all using ViX Hades 011 and no such issues!
Wish that I could figure out what I am doing wrong. Recordings were there last night and not there today. I don't remember setting anything to update overnight and did not think you could set box to auto delete everything on hdd. Seems odd that it has happened twice over the course of a few days.
Andy_Hazza
05-06-15, 20:40
You not using tsPanel are you?
Sent from my iPhone using Tapatalk
No not using ts panel. Checked again this morning and yesterday's recordings are gone and just left with a recording from today. Really weird, could it be a problem with the hard drive?
abu baniaz
06-06-15, 18:02
Can you telnet the following command and post back result?
df -h
This is what I get
Filesystem Size Used Available Use% Mounted on
ubi0:rootfs 194.8M 80.9M 113.9M 42% /
devtmpfs 279.4M 8.0K 279.4M 0% /dev
tmpfs 64.0K 0 64.0K 0% /media
/dev/sda1 931.3G 540.8M 929.8G 0% /media/hdd
/dev/sdb1 7.1G 16.3M 7.0G 0% /media/usb
tmpfs 279.
Recordings from this evening have disappeared and it is supposed to be recording now and /media/hdd is empty.
Just to update, I did try another image and same thing happened. Have done a fresh install of latest Openvix and so far recordings are staying put. Only changes I have made since are some settings on black box app and password on telnet. So far so good.
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.