mount file system using offset.
Hi, First of all please accept my apologies for posting to this list on this particular topic, but it was the closest match I could find. I pulled the harddisk out of my ps3, because I have forgotten the root password on the linux partition. After spending some time googling I see that the harddisk is encrypted and there are no linux utilities that can read/write it. However I did find that the testdisk program finds the linux partitions on the disk (see below.). It seems I should be able to mount the partitions on my linux pc box somehow since I now know their location on the disk. Does anyone know how one might go about that? Thanks! Fred TestDisk 6.12, Data Recovery Utility, May 2011 Christophe GRENIER gren...@cgsecurity.org http://www.cgsecurity.org Disk /dev/sdc - 80 GB / 74 GiB - CHS 9729 255 63 The harddisk (80 GB / 74 GiB) seems too small! ( 13 TB / 11 TiB) Check the harddisk size: HD jumpers settings, BIOS detection... The following partition can't be recovered: Partition StartEndSize in sectors Linux SWAP 2 9675 127 42 1593896 192 5 25450514424 TestDisk 6.12, Data Recovery Utility, May 2011 Christophe GRENIER gren...@cgsecurity.org http://www.cgsecurity.org Disk /dev/sdc - 80 GB / 74 GiB - CHS 9729 255 63 Partition StartEndSize in sectors P ext3 1566 128 42 1579 127 35 208776 [/boot] P ext3 1579 127 42 9675 127 41 130062240 [/] ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: mount file system using offset.
On Sun, Sep 18, 2011 at 21:21, F. Heitkamp heitk...@ameritech.net wrote:
First of all please accept my apologies for posting to this list on this
particular topic, but it was the closest match I could find.
I pulled the harddisk out of my ps3, because I have forgotten the root
password on the linux partition.
After spending some time googling I see that the harddisk is encrypted and
there are no linux utilities that can read/write it.
However I did find that the testdisk program finds the linux partitions on
the disk (see below.).
It seems I should be able to mount the partitions on my linux pc box somehow
since I now know their location on the disk.
Does anyone know how one might go about that?
Now you know the offset of the Linux partition on the disk (i.e. the
part of the
disk that was visible to Linux), you can use dm-linear to map this part onto a
new block device.
After that you can use kpartx to create block devices representing the
individual
partitions on the above new block device.
TestDisk 6.12, Data Recovery Utility, May 2011
Christophe GRENIER gren...@cgsecurity.org
http://www.cgsecurity.org
Disk /dev/sdc - 80 GB / 74 GiB - CHS 9729 255 63
The harddisk (80 GB / 74 GiB) seems too small! ( 13 TB / 11 TiB)
Check the harddisk size: HD jumpers settings, BIOS detection...
The following partition can't be recovered:
Partition Start End Size in sectors
Linux SWAP 2 9675 127 42 1593896 192 5 25450514424
TestDisk 6.12, Data Recovery Utility, May 2011
Christophe GRENIER gren...@cgsecurity.org
http://www.cgsecurity.org
Disk /dev/sdc - 80 GB / 74 GiB - CHS 9729 255 63
Partition Start End Size in sectors
P ext3 1566 128 42 1579 127 35 208776 [/boot]
P ext3 1579 127 42 9675 127 41 130062240 [/]
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say programmer or something like that.
-- Linus Torvalds
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: mount file system using offset.
On Sun, Sep 18, 2011 at 03:21:45PM -0400, F. Heitkamp wrote: Hi, First of all please accept my apologies for posting to this list on this particular topic, but it was the closest match I could find. I pulled the harddisk out of my ps3, because I have forgotten the root password on the linux partition. Why doesn't init=/bin/sh work on the ps3? ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
RE: [PATCH] RapidIO: documentation update
Micha Nelissen wrote: Alexandre Bounine wrote: After the host has completed enumeration of the entire network it releases devices by clearing device ID locks (calls rio_clear_locks()). For each endpoint -in the system, it sets the Master Enable bit in the Port General Control CSR +in the system, it sets the Discovered bit in the Port General Control CSR to indicate that enumeration is completed and agents are allowed to execute passive discovery of the network. The host needs to set both. Without Master Enable an agent is not supposed to initiate transactions on the bus, that's the meaning of that bit. This is correct and host set both bits: Master_Enable and Discovered. The documentation change above is related to event that triggers discovery process. In this context the change shown above is sufficient. Please see the original code patch submitted by Liu Gang. Alex. ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH 2/2] [PowerPC Book3E] Introduce new ptrace debug feature flag
On Tue, Aug 30, 2011 at 09:27:41PM -0300, Thiago Jung Bauermann wrote: On Fri, 2011-08-26 at 14:41 +1000, David Gibson wrote: On Wed, Aug 24, 2011 at 09:41:43PM -0300, Thiago Jung Bauermann wrote: On Wed, 2011-08-24 at 14:00 +1000, David Gibson wrote: On Tue, Aug 23, 2011 at 02:57:56PM +0530, K.Prasad wrote: On Tue, Aug 23, 2011 at 03:09:31PM +1000, David Gibson wrote: On Fri, Aug 19, 2011 at 01:23:38PM +0530, K.Prasad wrote: While PPC_PTRACE_SETHWDEBUG ptrace flag in PowerPC accepts PPC_BREAKPOINT_MODE_EXACT mode of breakpoint, the same is not intimated to the user-space debuggers (like GDB) who may want to use it. Hence we introduce a new PPC_DEBUG_FEATURE_DATA_BP_EXACT flag which will be populated on the features member of struct ppc_debug_info to advertise support for the same on Book3E PowerPC processors. I thought the idea was that the BP_EXACT mode was the default - if the new interface was supported at all, then BP_EXACT was always supported. So, why do you need a new flag? Yes, BP_EXACT was always supported but not advertised through PPC_PTRACE_GETHWDBGINFO. We're now doing that. I can see that. But you haven't answered why. BookS doesn't support BP_EXACT, that's why I suggested this flag. Surely you can support it with exactly the same sort of filtering you're using for the 8-byte ranges now? Yes, but to detect that the processor doesn't support BP_EXACT in hardware I'd have to send a ptrace request, and have it rejected. Only then I'd step back and simulate one with ranges. Considering that it's easy and backwards compatible to add a new flag to signal that BP_EXACT is not supported, I don't know why it would be better to go with the more convoluted process. No, I'm saying why not implement BP_EXACT on server. -- David Gibson| I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
