TiVo Community Forum banner
481 - 494 of 494 Posts

·
Premium Member
Joined
·
49 Posts
It looks like the default boot is with the -tivo kernel. You would need to choose the third option for the kernel choices to boot standard kernel.

I have not tested the tools with the -tivo kernels and am wondering if that is the issue.

Will PM you to start fixing this.


Sent from my iPad using Tapatalk
I know the first option is highlight but that is not what I chose, I chose the third option (every time). That was just a screen shot showing all the options...not the one I chose.
 

·
der Neuerer
Joined
·
3,407 Posts
Discussion Starter · #482 ·
I know the first option is highlight but that is not what I chose, I chose the third option (every time). That was just a screen shot showing all the options...not the one I chose.
Interesting. Will have to do some testing to see why it failed like it did.


Sent from my iPad using Tapatalk
 

·
Registered
Joined
·
9 Posts
I am having the exact same issue as JoJetSki. I copied the drive, then added the partition then I get the same error running the fix command. I tried both the tivo partition option and the normal option during boot with the same results.
 

·
der Neuerer
Joined
·
3,407 Posts
Discussion Starter · #484 ·
I am having the exact same issue as JoJetSki. I copied the drive, then added the partition then I get the same error running the fix command. I tried both the tivo partition option and the normal option during boot with the same results.
I found a small error in the code on the github site. The code is corrected and waiting on it to be incorporated into the main branch. If you wish I can help you correct your current image so it will work. Just would wait until the code is incorporated into the main branch before expanding any further.

Sent from my SM-G998U using Tapatalk
 

·
der Neuerer
Joined
·
3,407 Posts
Discussion Starter · #485 ·
The main branch has been updated with the fixes.

Sent from my SM-G998U using Tapatalk
 

·
Registered
Joined
·
9 Posts
Thank you, this solved my problem. I downloaded the newest iso from github and used the tivo partitions option because that seems to be what the github page recommends, and everything seems to work.
 

·
der Neuerer
Joined
·
3,407 Posts
Discussion Starter · #487 · (Edited)
Thank you, this solved my problem. I downloaded the newest iso from github and used the tivo partitions option because that seems to be what the github page recommends, and everything seems to work.
Can you post the mfsinfo -d output
Just want to make sure it is correct.
Sent from my SM-G998U using Tapatalk
 

·
Premium Member
Joined
·
49 Posts
I found a small error in the code on the github site. The code is corrected and waiting on it to be incorporated into the main branch. If you wish I can help you correct your current image so it will work. Just would wait until the code is incorporated into the main branch before expanding any further.

Sent from my SM-G998U using Tapatalk
The new image solved my problem and I was able to add the extra partitions and now I have an 8 TB roamio. Went from 10% free space to 70% free space. Thanks to JMBach who helped me out and then found the small issue with the current ISO so Equinoxe could post a new iso. Thanks to all for your hard work.
 
  • Like
Reactions: jmbach

·
Registered
Joined
·
9 Posts
Can you post the mfsinfo -d output
Just want to make sure it is correct.
Sent from my SM-G998U using Tapatalk
Can you give a quick explanation of what you are looking for in all this info?

Computer Personal computer Font Display device Electronic device


Code:
[email protected]:"$ sudo nfsinfo -d
/dev/sda
MFS Volune Header (64-bit)
state=0 magic-ebbafeed
deulist-/dev/sda10 /dev/sda11 /dev/sda12 /dev/sda13 /dev/sda2 /dev/sda3 zonemap_ptr=1121 total_secs-7805122560 next_fsid=4038774
MFS volume set for /dev/sda
The MFS volune Partition
set Sectors
contains 6 partitions
Size
/dev/sda10
1638400
800 MiB 423289 MiB
/dev/sda11 866895872
/dev/sda12 1638400
800 MiB
/dev/sda13 1074438144
524628 MiB
/dev/sda2 4278191104
2088960 MiB 772617 MiB
/dev/sda3 1582320640 Total MFS sectors: 7805122560
Total MFS volume size: 3811095 MiB
Total Inodes: 524288
Zone Maps
Zone 0: type=0 logstamp-25253459 checksum-3439775393 first-1122 last-525409
sector=1121 sbackup-1638398 length=1
size=524288 min-524288 free-524288 zero-0 num=1 next_sector-525410 next_sbackup-1638364 next_length-34
next size=866877440 next_min=20480 Zone 1: type=2 logstamp-25259159 checksum-234301934 first-1638400 last-868515839
sector-525410 sbackup-1638364 length-34 size=866877440 min-20480 free-22200320 zero-0 num=17
next_sector-525444 next_sbackup-1638234 next_length=130
next size-1112656 next_min=8
Zone 2: type=1 logstamp-25259159 checksum-997068015 first-525574 last=1638229
sector-525444 sbackup-1638234 length=130 size=1112656 min-8 free-1054592 zero-0 num=19
next_sector-868534272 next_sbackup-870172671 next_length=1
next size=524288 next_min=524288
Zone 3: type=0 logstamp-25253459 checksum-1826620146 sector-868534272 sbackup-870172671 length=1
first-868534273 last=869058560
size=524288 min-524288 free-524288 zero-0 num=1
next_sector-869058561 next_sbackup-870172637 next_length=34 next_size=1074421760 next_min=20480
Zone 4: type=2 logstamp-25259159 checksun- 22781 first-870172672 last=1944594431
sector-869058561 sbackup-870172637 length=34
size=1074421760 min=20480 free-36843520 zero-0 num=17 next_sector-869058595 next_sbackup-870172507 next_length=130
next_size=1113776_next_min=8 Zone 5: type=1 logstamp-2 p=25258515 checksum-3839544230 first-869058725 last=870172500
sector=869058595 sbackup-870172507 length=130 size=1113776 min-8 free-1109168 zero-0 num=19
next_sector=1944610817 next_sbackup-1944611709 next_length=130
next_size=4278190080 next_min-20480
Zone 6: type=2_logstamp-25259159 checksum=1259296489 first-1944611840 last-6222801919 sector 1944610817 sbackup-1944611709 length=130 size=4278190080 min-20
min=20480 free-4184678400 zero-0 num-19
next_sector-6222 r-6222801921 next_sbackup-6222802877 next length=66 next size-1582305280 next_min=20480
Zone 7: type=2 logstamp=25259159 checksum=1504095959 first-6222802914 last-7805108223
sector-6222801921 sbackup-6222802877 length=66 size=1582305280 min-20480 free-1512960000 zero-0 num-18
next sector=0 next_sbackup-0 next_length=0 next size=0 next_min-0
partition table for /dev/sda
[#称]:
Name 1st Sector
Sectors
Next
[01]: 63 [021]: MFS application/media region 1953525168 4278191104 6231716272
Apple
64
[031: MFS application/media region 6231716272 1582320896 7814037168 [04]:
Root 1 1074438720
8 1074438728
[05]:
Bootstrap 2 1074438728
8 1074438736
[06]:
Kernel 2 1074438736
8 1074438744
[07]: [08]:
Root 2 1074438744
8 1074438752
Linux suap 1074438752 1048576 1075487328
[09]:
/var 1075487328 1572864 1077060192
[10]: MFS application region 1083351648 1638400 1084990048
[11]:
MFS media region 1086628448 866896720 1953525168
[12]: MFS application region 2 1084990048 1638400 1086628448
[13]:
MFS media region 2
64 1074438640 1074438704
[14]:
SQLite 1077060192 6291456 1083351648
Estimated hours in a standalone TiVo: 4770 This MFS volume may be expanded 3 more times
[email protected]:"$
 

·
der Neuerer
Joined
·
3,407 Posts
Discussion Starter · #490 ·
Mainly congruency between the MFS sizes and partitions displayed on top and the partition size and structure displayed on the bottom

If you did something like add info to the MFS header without the appropriate partition structure and size, the TiVo will boot okay but may error out when it tried to record in that region.

Sent from my SM-G998U using Tapatalk
 

·
Premium Member
Joined
·
49 Posts
Mainly congruency between the MFS sizes and partitions displayed on top and the partition size and structure displayed on the bottom

If you did something like add info to the MFS header without the appropriate partition structure and size, the TiVo will boot okay but may error out when it tried to record in that region.

Sent from my SM-G998U using Tapatalk
I did an mfsadd and it said there was no more space to add so I stopped with my drive expansion. I did not run the mfsaddfix, I am assuming because it said there was no more space to add I will be fine.
 

·
der Neuerer
Joined
·
3,407 Posts
Discussion Starter · #492 ·
I did an mfsadd and it said there was no more space to add so I stopped with my drive expansion. I did not run the mfsaddfix, I am assuming because it said there was no more space to add I will be fine.
If mfsadd did not add anything then no mfsaddfix needs to be ran.

How many mfsadd/mfsaddfix did you run on the drive?

With an 8 TB drive you should have ran two of the mfsadd/mfsaddfix cycles to fully expand it after running the mfscopy command.


Sent from my SM-G998U using Tapatalk
 

·
Premium Member
Joined
·
49 Posts
If mfsadd did not add anything then no mfsaddfix needs to be ran.

How many mfsadd/mfsaddfix did you run on the drive?

With an 8 TB drive you should have ran two of the mfsadd/mfsaddfix cycles to fully expand it after running the mfscopy command.


Sent from my SM-G998U using Tapatalk
Yes. I ran two and the third attempt is when I got the message "no space to add".
 

·
der Neuerer
Joined
·
3,407 Posts
Discussion Starter · #494 ·
Yes. I ran two and the third attempt is when I got the message "no space to add".
That males sense. Every cycle add 2 TiB.

Sent from my SM-G998U using Tapatalk
 
481 - 494 of 494 Posts
Top