Solo2 Hard Disk Initialization problem Help...

[saayinla]

Hi All,

I am having problem setting up the Hard disk in my New Solo2 Box. Its been very easy to setup on the Vu+ Duo as I ve done this like 10 times at least.

But the Solo2 is behaving badly. The Hard drive was taken from a Portable USB drive I hard and it didnt work so I took it out and formatted it on a PC again to no avail. I cant see it in Telnet. See screenshot attached and its not in fstab as well.. not very clued up on Unix though but trying a little bit.


https://lh3.googleusercontent.com/-gg61ho0cLls/UQPEw62ILAI/AAAAAAAALEs/-S96Z0RGxiE/s528/screenshot%2520%25281%2529.jpg

https://lh6.googleusercontent.com/-5R-6poVbF3Q/UQPExOSWU8I/AAAAAAAALEw/KuAtQl6JeOU/s526/screenshot.jpg

https://lh6.googleusercontent.com/-aqw-ZhvtARQ/UQPExowwEhI/AAAAAAAALE8/9gsOcnZwWmM/s946/screenshot%2520%25282%2529.jpg


Also is the Output of my Telnet Session.. I tried to format the drive




login as: root
root@192.168.1.88's password:
root@vusolo2:~# df -h
Filesystem Size Used Available Use% Mounted on
ubi0:rootfs 196.6M 52.1M 144.5M 27% /
devtmpfs 279.1M 4.0K 279.1M 0% /dev
tmpfs 64.0K 0 64.0K 0% /media
tmpfs 279.2M 84.0K 279.1M 0% /var/volatile

root@vusolo2:~# more /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:~# login as: root
Filesystem Size Used Available Use% Mounted on
ubi0:rootfs 196.6M 52.1M 144.5M 27% /
devtmpfs 279.1M 4.0K 279.1M 0% /dev
tmpfs 64.0K 0 64.0K 0% /media
tmpfs 279.2M 84.0K 279.1M 0% /var/volatile
root@vusolo2:~# fstab
-sh: fstab: not found
Password:
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:~#

root@vusolo2:~#
root@vusolo2:~# mkfs.ext3 /dev/sda1
mke2fs 1.42.6 (21-Sep-2012)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
30531584 inodes, 122095872 blocks
6104793 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
3727 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

Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done





Please help.

Thanks in advance.

[reaper101]

if you are using blackhole image use the usb format wizard press blue button twice to get to it
start the wizard then plug in the usb drive and follow instructions

the usb drive should be mounted as media/usb

[lincsat]

As it's a HDD not a USB, then there is the initialize HDD option in the menu. Initialize, then reboot box, then mount.

[saayinla]

if you are using blackhole image use the usb format wizard press blue button twice to get to it
start the wizard then plug in the usb drive and follow instructions

the usb drive should be mounted as media/usb

Sorry forgot to mention its VIX image not blackhole.


As it's a HDD not a USB, then there is the initialize HDD option in the menu. Initialize, then reboot box, then mount.

I tried that earlier but I didnt wait for it to complete as it was taking Forever.. I ll give it another try. Thanks for the headsup.

[lincsat]

I'm not used to Vix, only Blackhole.

The only other thing I can suggest is with the HDD in a PC, from disk management - delete the volume on the HDD. Then put it back in the Vu+ and it should see it as a virgin HDD.

[simon 2003]

this is a longshot but worked for me on a dreambox 800 but have you tried to edit the fstab file,this is found in ect/ ,when you right click and press edit at the bottom where it refers to your HDD it has a hash in front of it,this kind off means "no" in linux so delete hash and save and should initialise straight away ,

[RustySpoons]

If it came out of a portable drive there is probably a hidden partition for some "backup" or "Cloud" software.

Put it in your windows PC, from the command prompt type diskpart, type list disk, then locate the disk number, so in my case I would type, select disk 2, then type list partitions, then type select partition 1, then type delete partition. If there are more partitions repeat the process.

Then put the disk in your solo2 box and it should be available to initialise.