Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

atv unable to mount /OSBoot #98

Closed
GoogleCodeExporter opened this issue Mar 13, 2015 · 25 comments
Closed

atv unable to mount /OSBoot #98

GoogleCodeExporter opened this issue Mar 13, 2015 · 25 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. successfully created stick using atvusb
2. booted off stick. see attached pictures of output errors

What is the expected output? What do you see instead?
expected for it to work. it didn't.

What version of the product are you using? On what operating system?
using atvusb-creator 1.0.b7. using Atv 2.0 (cant get it to update. it
downloads but fails to apply.) on a freshly "factory restored" system.

Please provide any additional information below.
not much else to explain. created the stick successfully. booted off stick
successfully. got mount errors from patchstick.sh. See attached.

Original issue reported on code.google.com by phpnotasp on 25 Oct 2008 at 3:59

Attachments:

@GoogleCodeExporter
Copy link
Author

under osx, on the flash drive, change the name of patchstick.sh to 
a_patchstick.sh. This disables the auto-
patchstick functions.

boot the atv using the flash stick, telnetd will startup,  telnet in 
(root/root) then

"ls -l /dev/sd*"

post output here.

Original comment by sdavi...@gmail.com on 25 Oct 2008 at 4:11

@GoogleCodeExporter
Copy link
Author

i have the same issue:

What steps will reproduce the problem?
Same as OP.

What is the expected output? What do you see instead?
Same as OP.

What version of the product are you using? On what operating system?
atvusb-creator 1.0.b7
Atv 2.2
OS X 10.5.5 PPC
"ls -l /dev/sd*" output:
/dev/sda
/dev/sda1
/dev/sda2
/dev/sda3
/dev/sda4
/dev/sdb
/dev/sdb1
/dev/sdb2

Please provide any additional information below.
Same as OP.

Original comment by khenr...@yahoo.com on 3 Nov 2008 at 10:30

@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

under penbuntu

fsck.hfsplus -f /dev/sdb2
mount -t hfsplus -o rw,force /dev/sdb2 /mnt/rootfs


bash /mnt/rootfs/a_patchstick.sh


Original comment by sdavi...@gmail.com on 3 Nov 2008 at 10:56

@GoogleCodeExporter
Copy link
Author

thank you sdavilla for the quick reply.  I still get the same error.

in telnet, I run each line, the output is below:
# fsck.hfsplus -f /dev/sdb2                     
** /dev/sdb2
** Checking HFS Plus volume.
** Checking Extents Overflow file.
** Checking Catalog file.
** Checking Catalog hierarchy.
** Checking Extended Attributes file.
** Checking volume bitmap.
** Checking volume information.
** The volume PATCHSTICK appears to be OK.
# mount -t hfsplus -o rw,force /dev/sdb2 /mnt/rootfs
# bash /mnt/rootfs/a_patchstick.sh

nothing happens for the last two lines above.  Sorry, I have to say that I am 
new to the mac as well.

btw, i tried it again and just let it sit after running bash 
/mnt/rootfs/a_patchstick.sh, my tv screen blacked out 
and the light on the AppleTV is flashing yellow.  Will wait a bit longer before 
power cycling the AppleTV.

Thanks again for your help.

Original comment by khenr...@yahoo.com on 4 Nov 2008 at 12:02

@GoogleCodeExporter
Copy link
Author



boot to penbuntu

fsck.hfsplus -f /dev/sdb2
mount -t hfsplus -o rw,force /dev/sdb2 /mnt/rootfs

mkdir /OSBoot
fsck.hfsplus -f /dev/sda3
mount -t hfsplus -o rw,force /dev/sda3 /OSBoot

fsck.hfsplus -f /dev/sda4
mount -t hfsplus -o rw,force /dev/sda4 /OSBoot/mnt


Original comment by sdavi...@gmail.com on 4 Nov 2008 at 12:36

@GoogleCodeExporter
Copy link
Author

Getting: Invalid argument

penbuntu login: root
Password: 
# fsck.hfsplus -f /dev/sdb2
** /dev/sdb2
** Checking HFS Plus volume.
** Checking Extents Overflow file.
** Checking Catalog file.
** Checking Catalog hierarchy.
** Checking Extended Attributes file.
** Checking volume bitmap.
** Checking volume information.
** The volume PATCHSTICK appears to be OK.
# mount -t hfsplus -o rw,force /dev/sdb2 /mnt/rootfs
# mkdir /OSBoot
# fsck.hfsplus -f /dev/sda3
** /dev/sda3
# mount -t hfsplus -o rw,force /dev/sda3 /OSBoot
mount: mounting /dev/sda3 on /OSBoot failed: Invalid argument


Original comment by khenr...@yahoo.com on 4 Nov 2008 at 1:08

@GoogleCodeExporter
Copy link
Author

interesting result, let now find out what format Linux thinks /dev/sda3 is.

in penbuntu

blkid

and post the results

Original comment by sdavi...@gmail.com on 4 Nov 2008 at 1:33

@GoogleCodeExporter
Copy link
Author

penbuntu login: root
Password: 
# blkid
/dev/sdb1: TYPE="hfsplus" 
/dev/sdb2: TYPE="hfsplus" 
/dev/sda1: TYPE="hfsplus" 
/dev/sda2: TYPE="hfsplus" 
/dev/sda3: LABEL="EFI" UUID="3F3C-1AF6" TYPE="vfat" 
/dev/sda4: TYPE="hfsplus" 
# 


Original comment by khenr...@yahoo.com on 4 Nov 2008 at 1:49

@GoogleCodeExporter
Copy link
Author

This is not a standard AppleTV set of partitions.

normally it is organized as 

/dev/sda1 -> EFI
/dev/sda2 -> Recovery (hfsplus)
/dev/sda3 -> OSBoot (hfsplus)
/dev/sda4 -> Media/Customer (hfsplus)

Tell me about the history with this AppleTV. What has been done to it in the 
past?



Original comment by sdavi...@gmail.com on 4 Nov 2008 at 2:12

@GoogleCodeExporter
Copy link
Author

@phpnotasp -> if you also do the above, do you get the same results in 
partition organization.

Original comment by sdavi...@gmail.com on 4 Nov 2008 at 2:16

@GoogleCodeExporter
Copy link
Author

purchased used and had problem getting update from 1.0 to latest 2.2.  would 
not respond to update software.

read on some forums to remove hard drive, place in usb external drive, connect 
to mac, erase OS Boot and Media 
partition, restore latest 2.2 dmg file to OS Boot partition and got it to run 
with the latest Apple TV version.

hope this is fixable :)

Original comment by khenr...@yahoo.com on 4 Nov 2008 at 2:21

@GoogleCodeExporter
Copy link
Author

"purchased used", ha, the seller needs a cluestick. That's why it would not 
update. 

Fixable but need to make sure to grap a copy of recovery contents first. You 
will be able to do this all from 
penbuntu.

see http://code.google.com/p/atv-bootloader/wiki/ATVBackup

Since your partition order is messed up, you will need to probe by mounting 
each partition. Then you can 
figure out which one is which.

The critical thing is to find "recovery" and back it up, don't do a dd image, 
follow the above instructions and 
copy the contents onto the flash drive. It's actually not critical as the above 
link has info on restoring from 
scratch. Then nuke the internal disk and use parted to create the proper 
partition order and sizes. The only 
partition that needs to be populated is recovery. Given a good recovery, the 
factory restore will re-populate 
everything else.


Good luck.





Original comment by sdavi...@gmail.com on 4 Nov 2008 at 2:39

@GoogleCodeExporter
Copy link
Author

Original comment by sdavi...@gmail.com on 4 Nov 2008 at 2:39

  • Changed state: Done
  • Added labels: Type-Other
  • Removed labels: Type-Defect

@GoogleCodeExporter
Copy link
Author

I get precisely the same error as described in this thread:
"mounting /dev/sda3 on /OSBoot failed"

and I tried the rename to "a_patchstick.sh"  and telnetd (version 1.9.1) does 
indeed
seem to start itself up, but at 127.0.0.1

Newbie warning: But when you say "telnet in and do...." I'm not sure what you 
mean:
there's obviously no keyboard with the ATV. And if I cable in with my laptop, 
what
should I do?

I tried, bring up a Terminal window and typing in telnet -- but what address? 
the ATV
gives itself 127.0.0.1

do you mean I should attach the ATV to my Airport Extreme base station?

Original comment by jcqua...@gmail.com on 19 Apr 2009 at 8:23

@GoogleCodeExporter
Copy link
Author

I figured it can't hurt to just attach the ATV by cable to the base station 
rather
than relying on wireless, and yes I can get a IP address that way. When I 
telnet in
via root/root and do 

ls -l /dev/sd*

I see:

/dev/sda
/dev/sda1
/dev/sda2

which isn't quite what sdavilla suggested should be there. So I tried blkid
which reports:
/dev/sda1: TYPE="hfsplus"
/dev/sda2: TYPE="hfsplus"

Also please don't get the impression I know what any of these linux commands 
mean --
I just guess well when reading the current thread :)  I'm a recent convert from 
Windows.

I'm thinking the next question will be the history of this AppleTV.  I had an
original 40Gb drive, had it since 2007. I recently bought a 320Mb upgraded
replacement harddisk with "all the AppleTV updates on it". I installed it with 
no
problems, enjoyed all the usual regular AppleTV features. Did an update to the 
latest
AppleTV software, no problems at all. Even controlled it via my iPhone. That's 
when I
decided to use the ATV solution so I could use ssh and XBMC

Original comment by jcqua...@gmail.com on 19 Apr 2009 at 9:52

@GoogleCodeExporter
Copy link
Author

ls -l /dev/sd*

should show all four internal disk partitions and the two usb flash drive 
partitions.

looks like EFI and Recovery are missing. EFI not so much a big deal, recovery 
means you will never be able to 
do a factory restore. The patchstick is not designed to handle such a goofy way 
to partition an internal appletv 
disk.

OSBoot is usually sda3 and Media is sda4.



Original comment by sdavi...@gmail.com on 21 Apr 2009 at 12:21

@GoogleCodeExporter
Copy link
Author

surely one of /dev/sda or /dev/sda1 or /dev/sda2 is OSBoot and the other
...?something else?  Is there no command that would tell?


Original comment by jcqua...@gmail.com on 21 Apr 2009 at 4:43

@GoogleCodeExporter
Copy link
Author

you have to manually mount and check which is which. But if you are unfamiliar 
with linux, this will take some 
learning. But no patchstick will work automatically. you could change the 
patchstick.sh script but again, with no 
linux experence, this will be difficult.



Original comment by sdavi...@gmail.com on 21 Apr 2009 at 5:50

@GoogleCodeExporter
Copy link
Author

could you point out what one would look for after mounting each to determine 
which is
OSBoot and which is Restore?

or can the entire hardrive be erased and replaced with some virgin state?

Original comment by jcqua...@gmail.com on 21 Apr 2009 at 5:25

@GoogleCodeExporter
Copy link
Author

see http://code.google.com/p/atv-bootloader/wiki/ATVBackup -> Opps I did not 
make a backup

Original comment by sdavi...@gmail.com on 21 Apr 2009 at 5:38

@GoogleCodeExporter
Copy link
Author

When I 
ls -l /dev/sd*

I see:

/dev/sda
/dev/sda1
/dev/sda2

I think these items are all related to my USB drive and not the built in ATV 
drive. Does that mean my ATV drive 
is dead?

Original comment by rimcl...@gmail.com on 18 Sep 2009 at 2:39

@GoogleCodeExporter
Copy link
Author

@rimclean, It's dead Jim.

Original comment by sdavi...@gmail.com on 18 Sep 2009 at 4:04

@GoogleCodeExporter
Copy link
Author

same error for me too. did you guys able to fix it

Original comment by arun.geo...@gmail.com on 15 Jun 2014 at 7:10

@GoogleCodeExporter
Copy link
Author

By the way following is what I am tying to do. I am creating an patch stick 
from mac and trying to upgrade my atv1 to Gotham. If I remember correctly I 
installed xbmc v12 rom crystalbuntu site.

Original comment by arun.geo...@gmail.com on 15 Jun 2014 at 8:16

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant