Filesystem Error: fsck

[Rob van der Does]

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.

 

[judge]

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]

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.

 

[ptoni]

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

 

[judge]

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.

 

[ptoni]

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/

 

[judge]

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.

 

[DISCODV]

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.

 

[ptoni]

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]

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.

 

[ptoni]

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?

 

[judge]

Have you filled your flash so?
maybe try a reflash now that your HDD has initalised.

 

[ptoni]

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?

 

[ptoni]

reflash

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

 

[Larry-G]

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.

 

[DISCODV]

Solved my issues by reflashing with a fresh update, hardrive working fine now

 

[ptoni]

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]

Look at the recordingssettings: is that really set to the correct location?
Also compare that location in Mountmanager.

 

[ptoni]

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]

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.