View Full Version : Filesystem Error: fsck
I noticed something was up when I realised all my movies on the HDD had vanished, so I ran the filesystem check from vix menu and I get the error
Error:
/dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
anyone know what can I do to resolve this?
Thanks
telnet in to the box, and run fsck manually...
You should also unmount the filesystem
telnet to the box then run
umount /media/hdd
fsck /dev/sda1
all sorted now thanks guys
Right well power got cut off today and now I've noticed this has happened again, But this time I am unable to umount the hdd and I get the following:
http://i39.tinypic.com/15dp0ue.png
any suggestions to what could be up?
try running "df -h" and "mount", and post the results
so it would be like this ?
root@vuduo:~# df -h mount
so it would be like this ?
root@vuduo:~# df -h mount
nope separate commands
root@vuduo:~# df -h
root@vuduo:~# mount
Is it an external USB harddrive or an USB flash memory ?
it's internal harddrive m8, Here are results :
Welcome to ViX for vuduo
ViX v2.3
vuduo login: root
Password:
root@vuduo:~# df -h
Filesystem Size Used Available Use% Mounted on
ubi0:rootfs 102.1M 82.9M 19.2M 81% /
tmpfs 64.0K 4.0K 60.0K 6% /dev
tmpfs 67.5M 660.0K 66.9M 1% /var/volatile
root@vuduo:~# mount
rootfs on / type rootfs (rw)
ubi0:rootfs on / type ubifs (rw,sync,relatime)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,size=64k,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
usbfs on /proc/bus/usb type usbfs (rw,relatime)
tmpfs on /var/volatile type tmpfs (rw,relatime)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
root@vuduo:~#
Can you give us the output of 'fdisk -l /dev/sd?' and output of 'dmesg' ?
it's internal harddrive m8, Here are results :
Welcome to ViX for vuduo
ViX v2.3
vuduo login: root
Password:
root@vuduo:~# df -h
Filesystem Size Used Available Use% Mounted on
ubi0:rootfs 102.1M 82.9M 19.2M 81% /
tmpfs 64.0K 4.0K 60.0K 6% /dev
tmpfs 67.5M 660.0K 66.9M 1% /var/volatile
root@vuduo:~# mount
rootfs on / type rootfs (rw)
ubi0:rootfs on / type ubifs (rw,sync,relatime)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,size=64k,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
usbfs on /proc/bus/usb type usbfs (rw,relatime)
tmpfs on /var/volatile type tmpfs (rw,relatime)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
root@vuduo:~#
That's showing that your hdd is not mounted currently... Hence, the reason you are unable to unmount it...
Can you give us the output of 'fdisk -l /dev/sd?' and output of 'dmesg' ?
If using the vix image, fdisk is not used. Instead, issue the command "sfdisk -l /dev/sd?". This should give something similar to the following:
Disk /dev/sda: 30524 cylinders, 64 heads, 32 sectors/track
Units = cylinders of 1048576 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sda1 0+ 30523 30524- 31256560 83 Linux
/dev/sda2 0 - 0 0 0 Empty
/dev/sda3 0 - 0 0 0 Empty
/dev/sda4 0 - 0 0 0 Empty
root@vuduo:~# fdisk -l /dev/sd?
-sh: fdisk: not found
root@vuduo:~#
[AUD]: setting mute : 0
[VID]: VIDEO_STOP 1 1
[AUD]: AUDIO_STOP 1
[AUD]: AUDIO_CONTINUE 1 0 audio pid_hndl : 0x0
[AUD]: AUDIO_CONTINUE:bcm7335->audio_pid_hndl is null 0 0
[AUD]: AUDIO_SET_BYPASS_MODE 0
[AUD]: AC3 proc_get_ac3 0 audio_passthrough_spdif : 0
[AUD]: AUDIO_PAUSE 1
[AUD]: AUDIO_PLAY 1 decoder start : 0
[VID]: VIDEO_SET_STREAMTYPE 1
[VID]: VIDEO_FREEZE 1 0
[VID]: VIDEO_PLAY 1 5 2
[VID]: VIDEO_SLOWMOTION 0 1
[VID]: VIDEO_FAST_FORWARD 0 1
[VID]: VIDEO_CONTINUE 1 1
[AUD]: AUDIO_CONTINUE 1 1 audio pid_hndl : 0xc0ad1edc
[AUD]: setting mute : 0
[VID]: VIDEO_STOP 1 1
[AUD]: AUDIO_STOP 1
[AUD]: AUDIO_CONTINUE 1 0 audio pid_hndl : 0x0
[AUD]: AUDIO_CONTINUE:bcm7335->audio_pid_hndl is null 0 0
FE tune
[AUD]: AUDIO_SET_BYPASS_MODE 0
[AUD]: AC3 proc_get_ac3 0 audio_passthrough_spdif : 0
[AUD]: AUDIO_PAUSE 1
[AUD]: AUDIO_PLAY 1 decoder start : 0
[VID]: VIDEO_SET_STREAMTYPE 1
[VID]: VIDEO_FREEZE 1 0
[VID]: VIDEO_PLAY 1 5 2
[VID]: VIDEO_SLOWMOTION 0 1
[VID]: VIDEO_FAST_FORWARD 0 1
[VID]: VIDEO_CONTINUE 1 1
[AUD]: AUDIO_CONTINUE 1 1 audio pid_hndl : 0xc0ad1d2c
[AUD]: setting mute : 0
[VID]: VIDEO_STOP 1 1
[AUD]: AUDIO_STOP 1
[AUD]: AUDIO_CONTINUE 1 0 audio pid_hndl : 0x0
[AUD]: AUDIO_CONTINUE:bcm7335->audio_pid_hndl is null 0 0
[AUD]: AUDIO_SET_BYPASS_MODE 0
[AUD]: AC3 proc_get_ac3 0 audio_passthrough_spdif : 0
[AUD]: AUDIO_PAUSE 1
[AUD]: AUDIO_PLAY 1 decoder start : 0
[VID]: VIDEO_SET_STREAMTYPE 1
[VID]: VIDEO_FREEZE 1 0
[VID]: VIDEO_PLAY 1 5 2
[VID]: VIDEO_SLOWMOTION 0 1
[VID]: VIDEO_FAST_FORWARD 0 1
[VID]: VIDEO_CONTINUE 1 1
[AUD]: AUDIO_CONTINUE 1 1 audio pid_hndl : 0xc0ad1dec
[AUD]: setting mute : 0
[VID]: VIDEO_STOP 1 1
[AUD]: AUDIO_STOP 1
[AUD]: AUDIO_CONTINUE 1 0 audio pid_hndl : 0x0
[AUD]: AUDIO_CONTINUE:bcm7335->audio_pid_hndl is null 0 0
[AUD]: AUDIO_SET_BYPASS_MODE 0
[AUD]: AC3 proc_get_ac3 0 audio_passthrough_spdif : 0
[AUD]: AUDIO_PAUSE 1
[AUD]: AUDIO_PLAY 1 decoder start : 0
[VID]: VIDEO_SET_STREAMTYPE 1
[VID]: VIDEO_FREEZE 1 0
[VID]: VIDEO_PLAY 1 5 2
[VID]: VIDEO_SLOWMOTION 0 1
[VID]: VIDEO_FAST_FORWARD 0 1
[VID]: VIDEO_CONTINUE 1 1
[AUD]: AUDIO_CONTINUE 1 1 audio pid_hndl : 0xc0ad1edc
[AUD]: setting mute : 0
[VID]: VIDEO_STOP 1 1
[AUD]: AUDIO_STOP 1
[AUD]: AUDIO_CONTINUE 1 0 audio pid_hndl : 0x0
[AUD]: AUDIO_CONTINUE:bcm7335->audio_pid_hndl is null 0 0
FE tune
[AUD]: AUDIO_SET_BYPASS_MODE 0
[AUD]: AC3 proc_get_ac3 0 audio_passthrough_spdif : 0
[AUD]: AUDIO_PAUSE 1
[AUD]: AUDIO_PLAY 1 decoder start : 0
[VID]: VIDEO_SET_STREAMTYPE 1
[VID]: VIDEO_FREEZE 1 0
[VID]: VIDEO_PLAY 1 5 2
[VID]: VIDEO_SLOWMOTION 0 1
[VID]: VIDEO_FAST_FORWARD 0 1
[VID]: VIDEO_CONTINUE 1 1
[AUD]: AUDIO_CONTINUE 1 1 audio pid_hndl : 0xc0ad1d8c
[AUD]: setting mute : 0
[VID]: VIDEO_STOP 1 1
[AUD]: AUDIO_STOP 1
[AUD]: AUDIO_CONTINUE 1 0 audio pid_hndl : 0x0
[AUD]: AUDIO_CONTINUE:bcm7335->audio_pid_hndl is null 0 0
[AUD]: AUDIO_SET_BYPASS_MODE 0
[AUD]: AC3 proc_get_ac3 0 audio_passthrough_spdif : 0
[AUD]: AUDIO_PAUSE 1
[AUD]: AUDIO_PLAY 1 decoder start : 0
[VID]: VIDEO_SET_STREAMTYPE 1
[VID]: VIDEO_FREEZE 1 0
[VID]: VIDEO_PLAY 1 5 2
[VID]: VIDEO_SLOWMOTION 0 1
[VID]: VIDEO_FAST_FORWARD 0 1
[VID]: VIDEO_CONTINUE 1 1
[AUD]: AUDIO_CONTINUE 1 1 audio pid_hndl : 0xc0ad1e1c
[AUD]: setting mute : 0
[VID]: VIDEO_STOP 1 1
[AUD]: AUDIO_STOP 1
[AUD]: AUDIO_CONTINUE 1 0 audio pid_hndl : 0x0
[AUD]: AUDIO_CONTINUE:bcm7335->audio_pid_hndl is null 0 0
FE tune
[AUD]: AUDIO_SET_BYPASS_MODE 0
[AUD]: AC3 proc_get_ac3 0 audio_passthrough_spdif : 0
[AUD]: AUDIO_PAUSE 1
[AUD]: AUDIO_PLAY 1 decoder start : 0
[VID]: VIDEO_SET_STREAMTYPE 1
[VID]: VIDEO_FREEZE 1 0
[VID]: VIDEO_PLAY 1 5 2
[VID]: VIDEO_SLOWMOTION 0 1
[VID]: VIDEO_FAST_FORWARD 0 1
[VID]: VIDEO_CONTINUE 1 1
[AUD]: AUDIO_CONTINUE 1 1 audio pid_hndl : 0xc0ad1dbc
[AUD]: setting mute : 0
!!!pes_cb idx<0
[VID]: VIDEO_STOP 1 1
[AUD]: AUDIO_STOP 1
[AUD]: AUDIO_CONTINUE 1 0 audio pid_hndl : 0x0
[AUD]: AUDIO_CONTINUE:bcm7335->audio_pid_hndl is null 0 0
================= FAN is OFF ==============================
[AUD]: AUDIO_SET_MUTE 0
[AUD]: AUDIO_SET_BYPASS_MODE 0
[AUD]: AC3 proc_get_ac3 0 audio_passthrough_spdif : 0
[AUD]: AUDIO_PAUSE 1
[AUD]: AUDIO_PLAY 1 decoder start : 0
[VID]: VIDEO_SET_STREAMTYPE 1
[VID]: VIDEO_FREEZE 1 0
[VID]: VIDEO_PLAY 1 5 2
[VID]: VIDEO_SLOWMOTION 0 1
[VID]: VIDEO_FAST_FORWARD 0 1
[VID]: VIDEO_CONTINUE 1 1
[AUD]: AUDIO_CONTINUE 1 1 audio pid_hndl : 0xc0ad1d5c
[AUD]: setting mute : 0
bcm7335: hotplug_callback():
Hotplug - status.connected 0
bcm7335: hotplug_callback():
Hotplug - Disconnecting HDMI from display
out of order segment: rcv_next 5910B1FE seq 5910B206 - 5910B245
ofo requeuing : rcv_next 5910B206 seq 5910B206 - 5910B245
out of order segment: rcv_next 5970960E seq 59709616 - 5970966A
ofo requeuing : rcv_next 59709616 seq 59709616 - 5970966A
out of order segment: rcv_next 58E4BE6B seq 58E4BE73 - 58E4BEE3
ofo requeuing : rcv_next 58E4BE73 seq 58E4BE73 - 58E4BEE3
out of order segment: rcv_next 58E4C219 seq 58E4C221 - 58E4C275
ofo requeuing : rcv_next 58E4C221 seq 58E4C221 - 58E4C275
bcm7335: hotplug_callback():
Hotplug - status.connected 1
bcm7335: hotplug_callback():
Hotplug - connecting HDMI to display 0xe
bcm7335: hotplug_callback():
Hotplug - status.connected 0
bcm7335: hotplug_callback():
Hotplug - Disconnecting HDMI from display
bcm7335: hotplug_callback():
Hotplug - status.connected 1
bcm7335: hotplug_callback():
Hotplug - connecting HDMI to display 0xe
bcm7335: hotplug_callback():
Hotplug - status.connected 0
bcm7335: hotplug_callback():
Hotplug - Disconnecting HDMI from display
[VID]: VIDEO_STOP 1 1
[AUD]: AUDIO_STOP 1
[AUD]: AUDIO_CONTINUE 1 0 audio pid_hndl : 0x0
[AUD]: AUDIO_CONTINUE:bcm7335->audio_pid_hndl is null 0 0
FE tune
dvb_demux_feed_del: feed not in list (type=0 state=0 pid=ffff)
[AUD]: AUDIO_SET_BYPASS_MODE 1
[AUD]: proc_get_ac3 0 audio_passthrough_spdif : 0
[AUD]: AUDIO_PAUSE 1
[AUD]: AUDIO_PLAY 1 decoder start : 0
[AUD]: AUDIO_CONTINUE 1 1 audio pid_hndl : 0xc0ad1d2c
[AUD]: setting mute : 0
[VID]: VIDEO_SELECT_SOURCE 1
[VID]: VIDEO_SET_STREAMTYPE 0
[VID]: VIDEO_PLAY 0 2 0
[VID]: VIDEO_CONTINUE 0 1
[VID]: VIDEO_CLEAR_BUFFER 0 1 0
[VID]: VIDEO_STOP 0 1
[VID]: VIDEO_SELECT_SOURCE 0
[AUD]: AUDIO_STOP 1
[AUD]: AUDIO_CONTINUE 1 0 audio pid_hndl : 0x0
[AUD]: AUDIO_CONTINUE:bcm7335->audio_pid_hndl is null 0 0
FE tune
[AUD]: AUDIO_SET_BYPASS_MODE 0
[AUD]: AC3 proc_get_ac3 0 audio_passthrough_spdif : 0
[AUD]: AUDIO_PAUSE 1
[AUD]: AUDIO_PLAY 1 decoder start : 0
[VID]: VIDEO_SET_STREAMTYPE 1
[VID]: VIDEO_FREEZE 1 0
[VID]: VIDEO_PLAY 1 5 2
[VID]: VIDEO_SLOWMOTION 0 1
[VID]: VIDEO_FAST_FORWARD 0 1
[VID]: VIDEO_CONTINUE 1 1
[AUD]: AUDIO_CONTINUE 1 1 audio pid_hndl : 0xc0ad1d2c
[AUD]: setting mute : 0
[VID]: VIDEO_STOP 1 1
[AUD]: AUDIO_STOP 1
[AUD]: AUDIO_CONTINUE 1 0 audio pid_hndl : 0x0
[AUD]: AUDIO_CONTINUE:bcm7335->audio_pid_hndl is null 0 0
================= FAN is OFF ==============================
[AUD]: AUDIO_SET_MUTE 0
[AUD]: AUDIO_SET_BYPASS_MODE 0
[AUD]: AC3 proc_get_ac3 0 audio_passthrough_spdif : 0
[AUD]: AUDIO_PAUSE 1
[AUD]: AUDIO_PLAY 1 decoder start : 0
[VID]: VIDEO_SET_STREAMTYPE 1
[VID]: VIDEO_FREEZE 1 0
[VID]: VIDEO_PLAY 1 5 2
[VID]: VIDEO_SLOWMOTION 0 1
[VID]: VIDEO_FAST_FORWARD 0 1
[VID]: VIDEO_CONTINUE 1 1
[AUD]: AUDIO_CONTINUE 1 1 audio pid_hndl : 0xc0ad1cfc
[AUD]: setting mute : 0
bcm7335: hotplug_callback():
Hotplug - status.connected 1
bcm7335: hotplug_callback():
Hotplug - connecting HDMI to display 0xf
bcm7335: hotplug_callback():
Hotplug - status.connected 0
bcm7335: hotplug_callback():
Hotplug - Disconnecting HDMI from display
bcm7335: hotplug_callback():
Hotplug - status.connected 1
bcm7335: hotplug_callback():
Hotplug - connecting HDMI to display 0xe
[VID]: VIDEO_STOP 1 1
[AUD]: AUDIO_STOP 1
[AUD]: AUDIO_CONTINUE 1 0 audio pid_hndl : 0x0
[AUD]: AUDIO_CONTINUE:bcm7335->audio_pid_hndl is null 0 0
FE tune
dvb_demux_feed_del: feed not in list (type=0 state=0 pid=ffff)
[AUD]: AUDIO_SET_BYPASS_MODE 1
[AUD]: proc_get_ac3 0 audio_passthrough_spdif : 0
[AUD]: AUDIO_PAUSE 1
[AUD]: AUDIO_PLAY 1 decoder start : 0
[VID]: VIDEO_SET_STREAMTYPE 0
[VID]: VIDEO_FREEZE 1 0
[VID]: VIDEO_PLAY 1 2 2
[VID]: VIDEO_SLOWMOTION 0 1
[VID]: VIDEO_FAST_FORWARD 0 1
[VID]: VIDEO_CONTINUE 1 1
[AUD]: AUDIO_CONTINUE 1 1 audio pid_hndl : 0xc0ad1cfc
[AUD]: setting mute : 0
dvb_demux_feed_del: feed not in list (type=0 state=0 pid=ffff)
[VID]: VIDEO_SLOWMOTION 0 1
[VID]: VIDEO_FAST_FORWARD 0 1
[VID]: VIDEO_CONTINUE 1 1
[AUD]: AUDIO_CONTINUE 1 1 audio pid_hndl : 0xc0ad1cfc
[AUD]: setting mute : 0
[VID]: VIDEO_STOP 1 1
[AUD]: AUDIO_STOP 1
[AUD]: AUDIO_CONTINUE 1 0 audio pid_hndl : 0x0
[AUD]: AUDIO_CONTINUE:bcm7335->audio_pid_hndl is null 0 0
================= FAN is OFF ==============================
[AUD]: AUDIO_SET_MUTE 0
dvb_demux_feed_del: feed not in list (type=0 state=0 pid=ffff)
[AUD]: AUDIO_SET_BYPASS_MODE 1
[AUD]: proc_get_ac3 0 audio_passthrough_spdif : 0
[AUD]: AUDIO_PAUSE 1
[AUD]: AUDIO_PLAY 1 decoder start : 0
[VID]: VIDEO_SET_STREAMTYPE 0
[VID]: VIDEO_FREEZE 1 0
[VID]: VIDEO_PLAY 1 2 2
[VID]: VIDEO_SLOWMOTION 0 1
[VID]: VIDEO_FAST_FORWARD 0 1
[VID]: VIDEO_CONTINUE 1 1
[AUD]: AUDIO_CONTINUE 1 1 audio pid_hndl : 0xc0ad1cfc
[AUD]: setting mute : 0
dvb_demux_feed_del: feed not in list (type=0 state=0 pid=ffff)
[VID]: VIDEO_SLOWMOTION 0 1
[VID]: VIDEO_FAST_FORWARD 0 1
[VID]: VIDEO_CONTINUE 1 1
[AUD]: AUDIO_CONTINUE 1 1 audio pid_hndl : 0xc0ad1cfc
[AUD]: setting mute : 0
bcm7335: hotplug_callback():
Hotplug - status.connected 0
bcm7335: hotplug_callback():
Hotplug - Disconnecting HDMI from display
bcm7335: hotplug_callback():
Hotplug - status.connected 1
bcm7335: hotplug_callback():
Hotplug - connecting HDMI to display 0xe
bcm7335: hotplug_callback():
Hotplug - status.connected 0
bcm7335: hotplug_callback():
Hotplug - Disconnecting HDMI from display
bcm7335: hotplug_callback():
Hotplug - status.connected 1
bcm7335: hotplug_callback():
Hotplug - connecting HDMI to display 0xe
out of order segment: rcv_next 3EC7037B seq 3EC703B3 - 3EC703BB
ofo requeuing : rcv_next 3EC703B3 seq 3EC703B3 - 3EC703BB
out of order segment: rcv_next 3EC73573 seq 3EC7357B - 3EC73631
ofo requeuing : rcv_next 3EC7357B seq 3EC7357B - 3EC73631
out of order segment: rcv_next 3EC752E0 seq 3EC7531F - 3EC75350
ofo requeuing : rcv_next 3EC7531F seq 3EC7531F - 3EC75350
root@vuduo:~#
If using the vix image, fdisk is not used. Instead, issue the command "sfdisk -l /dev/sd?".
Thanx pooface, totally forgot that i added fdisk manually...
If using the vix image, fdisk is not used. Instead, issue the command "sfdisk -l /dev/sd?". This should give something similar to the following:
Disk /dev/sda: 30524 cylinders, 64 heads, 32 sectors/track
Units = cylinders of 1048576 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sda1 0+ 30523 30524- 31256560 83 Linux
/dev/sda2 0 - 0 0 0 Empty
/dev/sda3 0 - 0 0 0 Empty
/dev/sda4 0 - 0 0 0 Empty
thanks pooface here is the results of that
root@vuduo:~# sfdisk -l /dev/sd?
Disk /dev/sda: 121601 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sda1 0+ 121600 121601- 976760028+ 83 Linux
/dev/sda2 0 - 0 0 0 Empty
/dev/sda3 0 - 0 0 0 Empty
/dev/sda4 0 - 0 0 0 Empty
root@vuduo:~#
t
root@vuduo:~# sfdisk -l /dev/sd?
Disk /dev/sda: 121601 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sda1 0+ 121600 121601- 976760028+ 83 Linux
/dev/sda2 0 - 0 0 0 Empty
/dev/sda3 0 - 0 0 0 Empty
/dev/sda4 0 - 0 0 0 Empty
root@vuduo:~#
This means the disk is there, if the filesystem is a bit more damaged the kernel often refuses to mount it (even if only as read only). You can easily check that by trying to mount it manually.
mount -t auto /dev/sda1 /media/hdd
If that fails post the message. If it doesnt you have mounted it manually, then unmount it with umount /media/hdd or umount /dev/sda1 . Then run fsck -y /dev/sda1 to try to repair it, the -y will run fsck and answear yes to all questions - if you are paranoid skip -y and answear all questions that appears manually. If VIX still doesnt mount the disk after reboot, and it is clean (that is, its not damaged). You can add an entry/line in /etc/fstab to skip vix's diskmounting logic, i dont know how supported that is ( i do it because i want some extra speed options that vix doesnt add otherwise).
The line should look something as follows:
/dev/sda1 /media/hdd auto rw,noatime,nodiratime,errors=remount-ro 0 0
The noatime and nodiratime is a safe performance enhancement - you can skip thoose if you want.
If the disk still doesnt mount on boot, send the output of dmesg directly after you booted the machine, it should contain the info why the disk wasnt mounted.
ok I ran that and here is the result.
root@vuduo:~# mount -t auto /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?
mount: mounting /dev/sda1 on /media/hdd failed: Invalid argument
root@vuduo:~#
Either your disk is really messed up or you are running NTFS on a partition marked as being a Linux volume. Do you know what filesystem it ought to contain ? Dont want to give an advice that will mess up your files ...:confused:
I'm not sure , I remember formatting the hard drive when got it not sure which system though it was quite a while back then just initialized it and has been working fine up until this.
Did you format it with your box or a computer ? Anyway we can see if the disk has reported errors (if it is a hardware failure) by installing smartmontools:
opkg install smartmontools
smartctl -a /dev/sda
Post the output of 'smartctl -a /dev/sda'
And you might aswell try to mount the file system with 'mount -t ext3 /dev/sda1 /media/hdd' or if that fails 'mount -t ext4 /dev/sda1 /media/hdd'
I'm not sure , I remember formatting the hard drive when got it not sure which system though it was quite a while back then just initialized it and has been working fine up until this.
I'd say easiest thing to is to re-initialize connected to the receiver (you will loose all data). Menu > Setup > System > Harddisk.
Did you format it with your box or a computer ? Anyway we can see if the disk has reported errors (if it is a hardware failure) by installing smartmontools:
opkg install smartmontools
smartctl -a /dev/sda
Post the output of 'smartctl -a /dev/sda'
And you might aswell try to mount the file system with 'mount -t ext3 /dev/sda1 /media/hdd' or if that fails 'mount -t ext4 /dev/sda1 /media/hdd'
Below is output of smartctl -a /dev/sda , Afterwords I tried to mount with both options you gave me and both failed
root@vuduo:~# smartctl -a /dev/sda
smartctl 5.39.1 2010-01-28 r3054 [mipsel-oe-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Device Model: SAMSUNG HD103SJ
Serial Number: S246JD2ZB04668
Firmware Version: 1AJ10001
User Capacity: 1,000,203,804,160 bytes
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 6
Local Time is: Fri Mar 2 11:15:37 2012 GMT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (9000) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off supp
ort.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 150) minutes.
SCT capabilities: (0x003f) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_
FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always -
11
2 Throughput_Performance 0x0026 252 252 000 Old_age Always -
0
3 Spin_Up_Time 0x0023 072 072 025 Pre-fail Always -
8774
4 Start_Stop_Count 0x0032 098 098 000 Old_age Always -
2249
5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always -
0
7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always -
0
8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline -
0
9 Power_On_Hours 0x0032 100 100 000 Old_age Always -
5599
10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always -
0
11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always -
0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always -
215
191 G-Sense_Error_Rate 0x0022 252 252 000 Old_age Always -
0
192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always -
0
194 Temperature_Celsius 0x0002 064 064 000 Old_age Always -
25 (Lifetime Min/Max 16/52)
195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always -
0
196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always -
0
197 Current_Pending_Sector 0x0032 252 252 000 Old_age Always -
0
198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline -
0
199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always -
0
200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always -
0
223 Load_Retry_Count 0x0032 252 252 000 Old_age Always -
0
225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always -
2308
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
Note: selective self-test log revision number (0) not 1 implies that no selectiv
e self-test has ever been run
SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been ru
n
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Completed [00% left] (0-65535)
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
root@vuduo:~#
Well smartctl output looks good, the physical disk seems to be fine, you can free up the space used by that tool by uninstalling it (opkg remove smartmontools)
I would go for a reformat as Sicillian suggested, you will loose all data on the disk though. If it indeed is a NTFS filesystem on the disk, and you want to go through the trouble - connect it to a machine running windows and see if the builtin filecheck can repair it. If it can, save your precious data somewhere else and let the sat box reformat the disk as Sicillian suggested.
My duo keeps crashing with HDD error.
I have 1tb Western Digital HDD which was working fine for last 3 days (when I set up my brand new box). The problem arose when I go into HDD direcotry to select playback the box crashes. Now all recordings are missing and EPG data wiped out. The following error message is showing: "Non existent Device. fsck.ext3. No such file on directory while trying to open dev/sda1"
I am still newbie and learning. Please, please inform how to fix this.
Thanks
Rob van der Does
20-10-12, 07:41
1- If the box crashes, there is a crashreport. Please upload that.
2- Go to Menu -->setup --> ViX --> MountManager: what does it tell you about the HDD? A screenshot could help.
3- Go to the HDD via an FTP-client and see if the folder '/movie' exists. If not create it.
4- How did you initialise the HDD? You should have done that via Menu --> setup --> HDD --> initialise
1- If the box crashes, there is a crashreport. Please upload that.
2- Go to Menu -->setup --> ViX --> MountManager: what does it tell you about the HDD? A screenshot could help.
3- Go to the HDD via an FTP-client and see if the folder '/movie' exists. If not create it.
4- How did you initialise the HDD? You should have done that via Menu --> setup --> HDD --> initialise
The MountManager shows the following:
Hard Disc: WDC 10ZRX-00A; Size: 931GB; Device: dev/sda1; Mount:/media/hdd; Type:ext4 R/W
I have checked vai FTP and the folder movies does exists; it is under media/hdd/movies.
The HDD was intialised in the original image, 3 days ago, and worked fine until yesterday. The crash log from yesterday contained message "write error on recording. disk full" and "Cannont allocate memory"
I have since done a complete shut down and reboot and then the lost information appears incuding epg. However, when I select playback of recordings it crashes and restarts itself and then the EPG or recorded list does not appear.
I have not created recording paths. Do Ineed to create these and if so how do you do this. I flashed mu box using openvix-3.0.339, i did not use bootloader. Should I have used bootloader?
Aprreaciate your advice.
Rob van der Does
20-10-12, 11:08
The MountManager shows the following:
Hard Disc: WDC 10ZRX-00A; Size: 931GB; Device: dev/sda1; Mount:/media/hdd; Type:ext4 R/W
I have checked vai FTP and the folder movies does exists; it is under media/hdd/movies.
The HDD was intialised in the original image, 3 days ago, and worked fine until yesterday. The crash log from yesterday contained message "write error on recording. disk full" and "Cannont allocate memory"
I have since done a complete shut down and reboot and then the lost information appears incuding epg. However, when I select playback of recordings it crashes and restarts itself and then the EPG or recorded list does not appear.
I have not created recording paths. Do Ineed to create these and if so how do you do this. I flashed mu box using openvix-3.0.339, i did not use bootloader. Should I have used bootloader?
Aprreaciate your advice.
1- If your system boots/worked OK, there's no need to flash a bootloader;
2- Although not the cause of your problem, initialising an HDD using OI has the huge disadvantage that Ext3 is being used. The fact that mountmanager states it to be Ext4 is wrong: it displays all Ext formats as Ext4. Please use a modern image (such as ViX) to initialise the HDD
3- Normally recordings settings do not have to be manipulated when an internal HDD is in use. But please have a look at it to see if it is set correct.
4- Can you post the outcome of the telnet commands 'df -h' and 'blkid'?
Will intialise the drive in Vix. However, before I do this I tried to update to Vix 3.0 378 (vai menu>setup>online update) but message said nothing to update. How do I update to latest 378 version of Vix
The outcome of the telnet commands 'df -h' and 'blkid' , is as follows:
Welcome to OpenViX for vuduo
openvix 3.0 vuduo
vuduo login: root
root@vuduo:~# blkid
/dev/sda1: UUID="e0949b23-c866-41fc-a8f2-4ea32162ba83" SEC_TYPE="ext2" TYPE="ext
3"
root@vuduo:~# df -h
Filesystem Size Used Available Use% Mounted on
ubi0:rootfs 102.1M 51.9M 50.3M 51% /
devtmpfs 67.5M 4.0K 67.4M 0% /dev
tmpfs 64.0K 0 64.0K 0% /media
/dev/sda1 931.2G 13.8G 917.4G 1% /media/hdd
tmpfs 67.6M 1.2M 66.4M 2% /var/volatile
root@vuduo:~#
Please let me know what I need to do to sort this problem with the HDD and how to update Vix image to latest 378.
Many Thanks
Rob van der Does
20-10-12, 15:00
OK, the good news is that your output seems to be fine.
The bad news is that I now have no clue what can be wrong.
Update to 380 should be possible online.
For the HDD Ext4 is the best format, but this will not solve your problem. Or maybe it happens to do so......??
OK, the good news is that your output seems to be fine.
The bad news is that I now have no clue what can be wrong.
Update to 380 should be possible online.
For the HDD Ext4 is the best format, but this will not solve your problem. Or maybe it happens to do so......??
Thanks. How do I update to 380. When I select online software update (vai menu>setup>online update) message keeps coming saying nothing to update. Is there a manual file for 380 which I can use to upload vai USB or is there an easier way.
Also, I am searching for AutoBouquets 28.2 plug in feed to download, but can't seem to find it. Please let me know where this is located.
check the version you have on the box already in menu> information> about. then try again. also to install the autobouquets plugin from the feeds it's in menu> plugins> green to download > then look in the various sub sections there for it. or install the version manually from the forum but be aware that both versions are different and not compatible with each other, use one or the other not both.
check the version you have on the box already in menu> information> about. then try again. also to install the autobouquets plugin from the feeds it's in menu> plugins> green to download > then look in the various sub sections there for it. or install the version manually from the forum but be aware that both versions are different and not compatible with each other, use one or the other not both.
Looked in the sub sections but still can't seem to find autobouquets. Can you tell me which sub section.
Looked in the sub sections but still can't seem to find autobouquets. Can you tell me which sub section.
I'm at work at the moment and dont have access to a receiver to check. if you can list the various headings in the plugin feeds i can tell you that way.
I'm at work at the moment and dont have access to a receiver to check. if you can list the various headings in the plugin feeds i can tell you that way.
The sub sections are: drivers, dvb, extensions, picons, security, settings, skins, system plug ins, and Vix. I have searched but can't seem to find. Please let me know which sub section it should be in..
Rob van der Does
20-10-12, 16:40
AB is in extensions. If you don't see it in there, it's probably already installed.
I am still having problems withh Hard drive which is causing the box to crash when I try to access the HDD or hard disk menu. The last message showed it was not intialised i tried to intialise but it does not work. After the last crash the mount manger is showing the hdd unmounted when i try to mount using the colour button it fails to mount. When the drive was mounted the crash logs contained message "write error on recording. disk full" and "cannont allocate memory"
How can I fix the Hard Drive and mount it back to get it to work. The HDD is a new western digital 1tb installled three days ago and it was intialised in the original image without any problems. Help Please
Rob van der Does
20-10-12, 19:29
The last message showed it was not intialised i tried to intialise but it does not work
What exactly does 'it does not work' mean?
You have to initialise the HDD. After starting the initialisation process you must allow the box some time; a message will pop up saying that the job is done.
What exactly does 'it does not work' mean?
You have to initialise the HDD. After starting the initialisation process you must allow the box some time; a message will pop up saying that the job is done.
The error message I get when trying to intialise the drive is, as follows:
"Error: writing inode tables: 0/7453..... Plus many other codes...................done.
Creating journal (32768blocks): mkfs ext 4. Attempt to write block to filesystem resulted in short write while trying to create journal"
I have waited long time when starting intialisation process but only error box is coming. How can I fix this?
The error message I get when trying to intialise the drive is, as follows:
"Error: writing inode tables: 0/7453..... Plus many other codes...................done.
Creating journal (32768blocks): mkfs ext 4. Attempt to write block to filesystem resulted in short write while trying to create journal"
I have waited long time when starting intialisation process but only error box is coming. How can I fix this?
Have you any other box you can format the drive on?
Have you any other box you can format the drive on?
Unfortunetly, I only have the one box.
If I were to remove the drive and replace with another new 1tb hard drive and then try to intialise in the Vix image (I have updated to V3.0, 382) do you think that would work?
Rob van der Does
20-10-12, 20:44
If I were to remove the drive and replace with another new 1tb hard drive and then try to intialise in the Vix image (I have updated to V3.0, 382) do you think that would work?
Well, if you have the drive, it's worth a try.
Unfortunetly, I only have the one box.
If I were to remove the drive and replace with another new 1tb hard drive and then try to intialise in the Vix image (I have updated to V3.0, 382) do you think that would work?
I've never had any issues formatting any drives using multiple VIX images, so i'd say yes.
However you should try the get the current one working.
Have you tried
mkfs.ext4 /dev/XXX in telnet?
replace XXX with the correct device.
Rob van der Does
20-10-12, 20:57
I've never had any issues formatting any drives using multiple VIX images, so i'd say yes.
However you should try the get the current one working.
Have you tried
mkfs.ext4 /dev/XXX in telnet?
replace XXX with the correct device.
Would be nice if that works, but even if it does, the HDD should b initialised again via the GUI in order to be formatted with the correct parameters.
Would be nice if that works, but even if it does, the HDD should b initialised again via the GUI in order to be formatted with the correct parameters.
The telnet command provides the following message:
root@vuduo:~# mkfs.ext4 /dev/wdc 10erx-00
mke2fs 1.42.1 (17-Feb-2012)
mkfs.ext4: invalid blocks '10erx-00' on device '/dev/wdc'
root@vuduo:~#
What does this mean and is it easy to fix.
In another forum I saw this:
""------ I installed a 500gb hard disk and this gave me a problem. It didn’t show up in the devices list and so ofcourse I couldn’t mount it.
Using a telnet session I investigated.
I typed :-
fdisk -l
This listed the hard disk and reported it had no partition table. Hence the reason the VU+ doesn’t see the drive.
Next I made a partition and formatted it.
I typed :-
fdisk /dev/sda
then I typed :-
w
(write new partition table and exit)
Lastly I typed :-
mkfs.ext3 /dev/sda
Once this was completed I restarted the box and now it showed in the devices list. I selected /media/hdd as it’s mount point.
Job done""
Do you think this would work to format my drive or would I do damage.
Thanks
are you copy & pasting commands from other forums?
If I use:
mkfs.ext4 /dev/wdc 10erx-00
I also get
mkfs.ext4: invalid blocks '10erx-00' on device '/dev/wdc'
as that device doesn't exist in my set-up.
Use df in telnet to see what the HDD is recognised as, & try that device.
are you copy & pasting commands from other forums?
If I use:
mkfs.ext4 /dev/wdc 10erx-00
I also get
mkfs.ext4: invalid blocks '10erx-00' on device '/dev/wdc'
as that device doesn't exist in my set-up.
Use df in telnet to see what the HDD is recognised as, & try that device.
No. Not copying from other forums.
df in telnet gives me this:
Welcome to OpenViX for vuduo
openvix 3.0 vuduo
vuduo login: root
root@vuduo:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
ubi0:rootfs 104592 58832 45760 56% /
devtmpfs 69072 4 69068 0% /dev
tmpfs 64 0 64 0% /media
/dev/sdb1 7812864 75504 7737360 1% /media/hdd
tmpfs 69188 1084 68104 2% /var/volatile
root@vuduo:~#
The device I have is shown as "ATA(WDC 10ERX-00)-internal" under intialisation menu on the b0x.
Any ides what I would enter after: mkfs.ext4 /dev/
I'd try
mkfs.ext4 /dev/sdb1
rather than
mkfs.ext4 /dev/wdc 10erx-00
in telnet so, if that works, then reformat using the image, but try it first & let us know the result.
Im having the same issue as others on this thread, did an online update in the morning and hdd is reporting errors. Been working fine until now, box can see hdd.
Tried initialising it and converting it to EXT4 but get an error message straight away.
Im on latest VIX image.
I'd try
mkfs.ext4 /dev/sdb1
rather than
mkfs.ext4 /dev/wdc 10erx-00
in telnet so, if that works, then reformat using the image, but try it first & let us know the result.
Following telnet command,"" mkfs.ext4 /dev/sdb1"" The results were, as follows:
root@vuduo:~# mkfs.ext4 /dev/sdb1
mke2fs 1.42.1 (17-Feb-2012)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
61054976 inodes, 244190645 blocks
12209532 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
7453 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
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 (32768 blocks): done
Writing superblocks and filesystem accounting information: done
root@vuduo:~#
I then tried to intialise hard drive but message said "" no displayable files on this medium found"". Any suggestions on how should I proceed and what do do next
Rob van der Does
21-10-12, 10:26
I then tried to intialise hard drive but message said "" no displayable files on this medium found"". Any suggestions on how should I proceed and what do do next
So that seems OK then: once the HDD has been initialised it's a new and empty disk.
So that seems OK then: once the HDD has been initialised it's a new and empty disk.
When I try to record message comes up saying disk full. The hdd directory page bottem right corner shows free space 931gb.
Does not let me record and it crashes when trying to access the HDD directory.
Making some progress but still there seems to be a problem. Any ideas?
Have you filled your flash so?
maybe try a reflash now that your HDD has initalised.
Have you filled your flash so?
maybe try a reflash now that your HDD has initalised.
Will try. Still newbie and learning. How do I reflash and what files do i use?
Will try. Still newbie and learning. How do I reflash and what files do i use?
To reflash do I use bootloader file (duo_cfe_3_0_usb) and then install the latest vix image (or do I back up and then restoe from Vix Backup and Image Manager). Please inform best way to reflash.
Thanks
you only need to flash the bootloader once, so if your receiver is already running a kernel 3.1.1 based image such as ViX 2.4 or ViX 3.0 you will be fine and dont need to load the bootloader again.
before you re-flash first make a set of backups from the ViX backup and image managers and keep these safe.
Then format a USB stick to FAT32.
download the image from here http://www.world-of-satellite.com/enigma2/openvix/
extract the .zip archive to your desktop then copy the vuplus folder and it's entire contents to the USB stick, place the stick in one of the USB ports and power off / on the receiver via the rear power switch ( allow approx 1 minute between powering off then back on again ). When you power back on you should see text across the screen of the receiver telling you whats happening. at this point DO NOT power off the receiver again until it tells you to do so, otherwise you can cause serious damage to it.
Solved my issues by reflashing with a fresh update, hardrive working fine now
Have you filled your flash so?
maybe try a reflash now that your HDD has initalised.
Done reflash but hard drive still not working. Same errors as before reflash i.e when I try to record, message comes up saying disk full. The hdd directory page bottem right corner shows free space 931gb. I did restore settings from back up manager after reflash.
Any suggestions what to do?
Rob van der Does
21-10-12, 16:20
Look at the recordingssettings: is that really set to the correct location?
Also compare that location in Mountmanager.
Look at the recordingssettings: is that really set to the correct location?
Also compare that location in Mountmanager.
checked record settings. The message say"s: ""The directory/hdd/movie is not writeable. Make sure you select writeable directory.""
Rob van der Does
21-10-12, 16:54
checked record settings. The message say"s: ""The directory/hdd/movie is not writeable. Make sure you select writeable directory.""
Yes, we knew that already because of your previous errors. But go in there, and check what the location is exactly.
'Something' has been mounted as hdd/movie, that isn't actually your HDD. Also tell us what mountmanager says about the HDD.
Yes, we knew that already because of your previous errors. But go in there, and check what the location is exactly.
'Something' has been mounted as hdd/movie, that isn't actually your HDD. Also tell us what mountmanager says about the HDD.
Under Recording settings menu, The Defualt Move location is showing as Hdd/movie. When I select this it shows Parent Directory Folder an Trash folder only (but I cannot select either of these folders. There is also bookmark HDD/movie. How do I confirm that the HDD/move location is the hard drive?
The Mount Manager shows: Hard Disck ATA WDC10 ERX, Size: 976.61gb; Mount: /media/hdd: Device/devsda1; Type: Ext 4 r/w.
It also shows my USB (which I use for back up), Mount: /media/usb: Device/devsdb1; Type: Vfat r/w.
What should I do next?
Rob van der Does
21-10-12, 21:14
Please: in recordingssettings click on the entry showing the path. That opens an other screen. In there push 'CH+' and navigate to the correct location (probably media/hdd/movie) and click on blue. Now a new bookmark has been established.
Click on 'CH-' and now click on the just made bookmark, then save. You now return to the previous screen: exit via 'save'.
If you FTP/telnet into the box, are the correct locations there & mounted?
Please: in recordingssettings click on the entry showing the path. That opens an other screen. In there push 'CH+' and navigate to the correct location (probably media/hdd/movie) and click on blue. Now a new bookmark has been established.
Click on 'CH-' and now click on the just made bookmark, then save. You now return to the previous screen: exit via 'save'.
Thanks. Followed these instructions but still no joy.
HDD/movie bookmark already existed (at the top of screen Default Movie location is shown: hdd/movie) this only gives option to remove bookmark.
I also created new bookmark media/hdd (at the top of screen Default Movie location for this bookmark is shown: media/hdd) but this did not work either.
When I try to record after 20 secons a message appears disk full. Then when you try to delete the 20 second recording in the trash can the box crashes. Anything else I can do? Thanks
If you FTP/telnet into the box, are the correct locations there & mounted?
Using FTP, I can see the Media and HDD folders. In Media you have HDD folder which contains logs, lost & found, timershift and movie.
When you click HDD folder (whch is located on the first page where all other folders are) it opens folders under Media.
What telnet command do I use to check if hard drive is mounted?
Rob van der Does
22-10-12, 15:12
What is the output of the telnet commands
blkid
and
df -h
What is the output of the telnet commands
blkid
and
df -h
The output of telnet commands, is as follows:
root@vuduo:~# blkid
/dev/ubi0_0: UUID="9891dc83-9c79-431a-948a-d51090e64a6f" TYPE="ubifs"
/dev/sda1: LABEL="PETERPAL" UUID="8056-A382" TYPE="vfat"
/dev/sdb1: UUID="55246bf5-b706-4703-8a60-1e851f3e142b" TYPE="ext4"
root@vuduo:~#
root@vuduo:~# df -h
Filesystem Size Used Available Use% Mounted on
ubi0:rootfs 102.1M 61.8M 40.3M 61% /
devtmpfs 67.5M 4.0K 67.4M 0% /dev
tmpfs 64.0K 0 64.0K 0% /media
/dev/sda1 7.5G 171.8M 7.3G 2% /media/usb
/dev/sdb1 931.4G 207.1M 931.2G 0% /media/hdd
tmpfs 67.6M 1.0M 66.5M 2% /var/volatile
root@vuduo:~#
I have a usb inserted and 1tb hard drive. What do these commands mean and what can i do next?
Rob van der Does
22-10-12, 17:35
Those commands show some details about your mounts.
Please do the following:
1- Disconnect your USB-device;
2- Go to mountmanager and change the mount of the HDD (presently mounted as 'sdb1') to 'sda1'
3- Follow the orders by the box (reboot);
4- After the reboot, go to the mountmanager to check the HDD to be indeed mounted as 'sda1';
if that's fine
5- go to the recordings settings, and make sure that the correct path has been set. Make a recording to check all is well.
if that's fine
6- insert the USB-device again, and use mountmanager to set it as 'usb'. Reboot if asked by the box.
After the reboot: check again if all is fine.
And please post again the output of
blkid and
df -h
See you later!
Those commands show some details about your mounts.
Please do the following:
1- Disconnect your USB-device;
2- Go to mountmanager and change the mount of the HDD (presently mounted as 'sdb1') to 'sda1'
3- Follow the orders by the box (reboot);
4- After the reboot, go to the mountmanager to check the HDD to be indeed mounted as 'sda1';
if that's fine
5- go to the recordings settings, and make sure that the correct path has been set. Make a recording to check all is well.
if that's fine
6- insert the USB-device again, and use mountmanager to set it as 'usb'. Reboot if asked by the box.
After the reboot: check again if all is fine.
And please post again the output of
blkid and
df -h
See you later!
Again Did not work. Message this time is no HDD found or HDD not initailised. Followed instructions as above. Mount Manager and recording settings seem to be correct. They show:
Mount Manager shows: Device: /dev/sda1, Mount:media/sda1, Type Ext 4 r/W
Recording settings shows location: hdd/movie then when you click it shows path to media/sda1 whcich is also set up as bookmark.
The output of telnet is:
/dev/ubi0_0: UUID="9891dc83-9c79-431a-948a-d51090e64a6f" TYPE="ubifs"
/dev/sda1: UUID="55246bf5-b706-4703-8a60-1e851f3e142b" TYPE="ext4"
root@vuduo:~#
root@vuduo:~#
root@vuduo:~# df -h
Filesystem Size Used Available Use% Mounted on
ubi0:rootfs 102.1M 63.3M 38.8M 62% /
devtmpfs 67.5M 4.0K 67.4M 0% /dev
tmpfs 64.0K 0 64.0K 0% /media
/dev/sda1 931.4G 209.4M 931.2G 0% /media/sda1
tmpfs 67.6M 1.0M 66.6M 1% /var/volatile
root@vuduo:~#
What next????????
Rob van der Does
22-10-12, 21:44
Sorry: I'm out of ideas. Let's hope one of my colleagues jumps in.
/dev/sda1 931.4G 209.4M 931.2G 0% /media/sda1
Is showing your HDD as mounted, can you go to Menu -> Setup -> VIX -> Mount Manager, press green button & change the mount point to /media/hdd, save & reboot.
/dev/sda1 931.4G 209.4M 931.2G 0% /media/sda1
Is showing your HDD as mounted, can you go to Menu -> Setup -> VIX -> Mount Manager, press green button & change the mount point to /media/hdd, save & reboot.
Tried this but still not recording. When you put recording On, Message appears after 20 seconds saying: ""Write Error, Disk Full"".
Do you think there are compatibilty issue with Western Digital hard drive, WDC10ERX?
What else can I try?
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.