my tv was hacked via manual hotel mode hack and i usually use a usb key with two partitions one formatted fat32 for samygo files and one formatted to xfs for Recording. So in dtv/usb/ i usually have sda sda1 and sdb.
Sdb is a virtual usb where i mount a Windows network share.
I decide to use one old ide hard disk instead of usb so i buy one external box and make the old hard disk portable.
I formatted it with 2 partitions one for samygo and one for Recording, the hard disk pass the test and everything seems work well. But i can't mount the network share... The virtual usb is created every time i boot the tv but the network mount is never mounted. i see that the two partitions are recognized as sda5 and sda6 maybe is that the problem? But the hack still works i have ftp samba Telnet on my tv at the boot time and all patch are loaded
Any hints?
Device recognized as sda5 and sda6 how to modify?
Re: Device recognized as sda5 and sda6 how to modify?
So 43 views and any suggestions?
- beatfreak
- SamyGO Project Donor
- Posts: 597
- Joined: Tue Aug 23, 2011 9:03 am
- Location: Hamburg
- Contact:
Re: Device recognized as sda5 and sda6 how to modify?
on standard partition tables you can create 4 primary partitions and (idk, more) extended partitions, so the primary partitions are always sdx1-sdx4 and the extended start from 5
your'e welcome
your'e welcome

//UE40C6500 @ T-VALDEUC 3011 // rooted manual HotelMode style // PVR to NFS via 18MB on-the-fly sparse XFS // >> decommissioned due to tuner death
//UE46F8090 @ T-FXPDEUC 1136 // rooted by new Widget // root starting with empty usb drive
FYI: you can close your ssh session with SamyGO with
If you can't fix it using dvct tape, you are not using enough dvct tape.
//UE46F8090 @ T-FXPDEUC 1136 // rooted by new Widget // root starting with empty usb drive
FYI: you can close your ssh session with SamyGO with
Code: Select all
~.
Re: Device recognized as sda5 and sda6 how to modify?
Thanks beatfreak i solved the problem with reformat entire hard disk with gparted. But the problem still persist the network share aren't mounted. So i have to try to find where is the problem i think is due to init script that try to mount the network share before the network is ready.
- beatfreak
- SamyGO Project Donor
- Posts: 597
- Joined: Tue Aug 23, 2011 9:03 am
- Location: Hamburg
- Contact:
Re: Device recognized as sda5 and sda6 how to modify?
maybe, if you are using remis71 nfsmount.init there is a wait value, if you set this to ~45 it should definately work then you can try to decrease it slowly
//UE40C6500 @ T-VALDEUC 3011 // rooted manual HotelMode style // PVR to NFS via 18MB on-the-fly sparse XFS // >> decommissioned due to tuner death
//UE46F8090 @ T-FXPDEUC 1136 // rooted by new Widget // root starting with empty usb drive
FYI: you can close your ssh session with SamyGO with
If you can't fix it using dvct tape, you are not using enough dvct tape.
//UE46F8090 @ T-FXPDEUC 1136 // rooted by new Widget // root starting with empty usb drive
FYI: you can close your ssh session with SamyGO with
Code: Select all
~.