* reiser3.6 files inaccessable from rescue CD post reiserfsck --rebuild-tree
@ 2005-10-30 23:55 michael chang
2005-10-31 8:34 ` Vladimir V. Saveliev
0 siblings, 1 reply; 6+ messages in thread
From: michael chang @ 2005-10-30 23:55 UTC (permalink / raw)
To: ReiserFS List
I know this seems kinda funky, and this is the first time this has
ever happened to me using a reiser filesystem. (I've found that after
decent testing, the filesystems, like reiserfs3 work quite well.)
Anyways, I'd booted off of a Ubuntu 5.04 live CD and gotten gparted,
and tried to use that to resize my reiserfs v3.6 partition (
/dev/hda5, containing /boot inside (didn't put it as a seperate
partition, to my own woe) and a ClusterKNOPPIX cloop image and all the
files in the system). Anyways, I tried to shrink the partition (which
I'd done many with great sucess, albeit this was my first time using
gparted to do it), but for some reason it ran reiserfsck -y
--fix-fixable and wouldn't resize the partiton. So I went and
switched to parted, which while resizing told me that there was an
error with one of the inodes.
So I figured I'd check the partition. I went and ran reiserfsck
--check /dev/hda5 and it went and told me I needed a rebuild tree. So
I ran reiserfsck --rebuild-tree /dev/hda5, told it yes, and let it
run.
When I went back to mount the paritition, I could do an ls of the
root, and see filenames. But if I went in to one of the directories
(e.g. /etc, /boot, or whatever) and list, I would get a list of the
files, but -l would tell me the permission was denied to read the list
of files, while running as root, from a rescue CD. [At this point,
the entire disk was unbootable, because GRUB would give an Error 16
and sqawk because it couldn't read /boot/grub/menu.lst from the
partition.] I tried chmoding the files as root, just about
everything, and it would always fail.
If I boot my Ubuntu install cd and run the "rescue" system, and try
and select my reiserfs partition, it will fail, saying that it doesn't
have the permisisons to execute /bin/bash.
So, I'm sitting here with my pc next to me, with a reiserfs partition
that seems to have all the data intact on it, but gives a permision
denied error when I'm running any tool as root, even to just get a
directory listing and read the files.
Unfortunately, I didn't think to capture reiserfsck's output while it
was doing its work, so I don't have a copy of that, unfortunately.
I don't have $20, or otherwise I would send it, but I would appreciate
any help that could be given, if possible. I understand you're all
busy and resource-strapped, although I'm rather perplexed about my
situation. Thanks.
--
~Mike
- Just my two cents
- No man is an island, and no man is unable.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: reiser3.6 files inaccessable from rescue CD post reiserfsck --rebuild-tree
2005-10-30 23:55 reiser3.6 files inaccessable from rescue CD post reiserfsck --rebuild-tree michael chang
@ 2005-10-31 8:34 ` Vladimir V. Saveliev
2005-10-31 21:41 ` michael chang
0 siblings, 1 reply; 6+ messages in thread
From: Vladimir V. Saveliev @ 2005-10-31 8:34 UTC (permalink / raw)
To: michael chang; +Cc: ReiserFS List
Hello
michael chang wrote:
> I know this seems kinda funky, and this is the first time this has
> ever happened to me using a reiser filesystem. (I've found that after
> decent testing, the filesystems, like reiserfs3 work quite well.)
>
> Anyways, I'd booted off of a Ubuntu 5.04 live CD and gotten gparted,
> and tried to use that to resize my reiserfs v3.6 partition (
> /dev/hda5, containing /boot inside (didn't put it as a seperate
> partition, to my own woe) and a ClusterKNOPPIX cloop image and all the
> files in the system). Anyways, I tried to shrink the partition (which
> I'd done many with great sucess, albeit this was my first time using
> gparted to do it), but for some reason it ran reiserfsck -y
> --fix-fixable and wouldn't resize the partiton. So I went and
> switched to parted, which while resizing told me that there was an
> error with one of the inodes.
>
> So I figured I'd check the partition. I went and ran reiserfsck
> --check /dev/hda5 and it went and told me I needed a rebuild tree. So
> I ran reiserfsck --rebuild-tree /dev/hda5, told it yes, and let it
> run.
>
> When I went back to mount the paritition, I could do an ls of the
> root, and see filenames. But if I went in to one of the directories
> (e.g. /etc, /boot, or whatever) and list, I would get a list of the
> files, but -l would tell me the permission was denied to read the list
> of files, while running as root, from a rescue CD. [At this point,
> the entire disk was unbootable, because GRUB would give an Error 16
> and sqawk because it couldn't read /boot/grub/menu.lst from the
> partition.] I tried chmoding the files as root, just about
> everything, and it would always fail.
>
> If I boot my Ubuntu install cd and run the "rescue" system, and try
> and select my reiserfs partition, it will fail, saying that it doesn't
> have the permisisons to execute /bin/bash.
>
Please boot off install cd so that it does not mount problem reiserfs partition
(/dev/hda5) as root filesystem.
Mount /dev/hda5 to /mnt and run ls /mnt/bin/ -l
What do you get?
> So, I'm sitting here with my pc next to me, with a reiserfs partition
> that seems to have all the data intact on it, but gives a permision
> denied error when I'm running any tool as root, even to just get a
> directory listing and read the files.
>
> Unfortunately, I didn't think to capture reiserfsck's output while it
> was doing its work, so I don't have a copy of that, unfortunately.
>
> I don't have $20, or otherwise I would send it, but I would appreciate
> any help that could be given, if possible. I understand you're all
> busy and resource-strapped, although I'm rather perplexed about my
> situation. Thanks.
>
> --
> ~Mike
> - Just my two cents
> - No man is an island, and no man is unable.
>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: reiser3.6 files inaccessable from rescue CD post reiserfsck --rebuild-tree
2005-10-31 8:34 ` Vladimir V. Saveliev
@ 2005-10-31 21:41 ` michael chang
2005-11-01 12:12 ` Vladimir V. Saveliev
0 siblings, 1 reply; 6+ messages in thread
From: michael chang @ 2005-10-31 21:41 UTC (permalink / raw)
To: Vladimir V. Saveliev; +Cc: ReiserFS List
On 10/31/05, Vladimir V. Saveliev <vs@namesys.com> wrote:
> Hello
>
> michael chang wrote:
> > If I boot my Ubuntu install cd and run the "rescue" system, and try
> > and select my reiserfs partition, it will fail, saying that it doesn't
> > have the permisisons to execute /bin/bash.
> >
>
> Please boot off install cd so that it does not mount problem reiserfs partition
> (/dev/hda5) as root filesystem.
> Mount /dev/hda5 to /mnt and run ls /mnt/bin/ -l
> What do you get?
Other results that may be of relevance: (which explain why GRUB
complains, and note that for some reason, by default, ls is aliased to
"ls --color=auto")
ubuntu@ubuntu:/mnt$ ls boot
ls: boot/grub: Permission denied
ls: boot/knoppix: Permission denied
ls: boot/vmlinuz-2.6.12-9-686: Permission denied
ls: boot/memtest86+.bin: Permission denied
ls: boot/System.map-2.6.10-5-386: Permission denied
ls: boot/abi-2.6.12-9-686: Permission denied
ls: boot/config-2.6.10-5-386: Permission denied
ls: boot/initrd.img-2.6.10-5-386: Permission denied
ls: boot/System.map-2.6.12-9-686: Permission denied
ls: boot/config-2.6.12-9-686: Permission denied
ls: boot/initrd.img-2.6.12-9-686: Permission denied
ls: boot/vmlinuz-2.6.10-5-386: Permission denied
ubuntu@ubuntu:/mnt$ ls boot -l
ls: boot/grub: Permission denied
ls: boot/knoppix: Permission denied
ls: boot/vmlinuz-2.6.12-9-686: Permission denied
ls: boot/memtest86+.bin: Permission denied
ls: boot/System.map-2.6.10-5-386: Permission denied
ls: boot/abi-2.6.12-9-686: Permission denied
ls: boot/config-2.6.10-5-386: Permission denied
ls: boot/initrd.img-2.6.10-5-386: Permission denied
ls: boot/System.map-2.6.12-9-686: Permission denied
ls: boot/config-2.6.12-9-686: Permission denied
ls: boot/initrd.img-2.6.12-9-686: Permission denied
ls: boot/vmlinuz-2.6.10-5-386: Permission denied
total 0
ubuntu@ubuntu:/mnt$ ls boot --color=no
abi-2.6.12-9-686 initrd.img-2.6.10-5-386 System.map-2.6.10-5-386
config-2.6.10-5-386 initrd.img-2.6.12-9-686 System.map-2.6.12-9-686
config-2.6.12-9-686 knoppix vmlinuz-2.6.10-5-386
grub memtest86+.bin vmlinuz-2.6.12-9-686
ubuntu@ubuntu:~$ ls /mnt -l
total 371
lrwxrwxrwx 1 root root 32 2005-10-09 00:24 Archive ->
/windows/Downloads/media/Archive
drwxr-xr-x 2 root root 48 2005-10-14 00:19 bin
drwxr-xr-x 3 root root 72 2005-10-30 14:12 boot
lrwxrwxrwx 1 root root 11 2005-10-05 21:38 cdrom -> media/cdrom
drwxr-xr-x 12 root root 21688 2005-10-07 04:08 dev
drwxr-xr-x 147 root root 7856 2005-10-30 14:36 etc
drwxr-xr-x 2 root root 48 2005-10-05 21:38 hda6
drwxr-xr-x 7 root root 176 2005-10-15 14:45 home
drwxr-xr-x 2 root root 48 2005-10-05 21:39 initrd
lrwxrwxrwx 1 root root 28 2005-10-14 00:20 initrd.img ->
boot/initrd.img-2.6.12-9-686
lrwxrwxrwx 1 root root 28 2005-10-05 22:10 initrd.img.old ->
boot/initrd.img-2.6.10-5-386
drwxr-xr-x 20 root root 4768 2005-10-14 00:19 lib
drwx------ 794 root root 340208 2005-10-30 15:49 lost+found
drwxr-xr-x 4 root root 128 2005-10-30 14:10 media
drwxr-xr-x 2 root root 48 2005-03-31 19:09 mnt
drwxr-xr-x 2 root root 48 2005-10-09 03:12 opt
lrwxrwxrwx 1 root root 33 2005-10-09 00:24 Original ->
/windows/Downloads/media/Original
drwxr-xr-x 2 root root 48 2005-03-31 19:09 proc
drwxr-xr-x 13 root root 520 2005-10-29 23:54 root
drwxr-xr-x 2 root root 5120 2005-10-15 20:35 sbin
drwxr-xr-x 2 root root 48 2005-10-05 21:39 srv
drwxr-xr-x 2 root root 48 2005-10-23 04:26 swap
drwxr-xr-x 2 root root 48 2005-03-23 22:41 sys
drwxrwxrwt 7 root root 240 2005-10-30 14:36 tmp
drwxr-xr-x 15 root root 376 2005-10-20 23:29 usr
drwxr-xr-x 16 root root 384 2005-10-14 00:20 var
lrwxrwxrwx 1 root root 25 2005-10-14 00:20 vmlinuz ->
boot/vmlinuz-2.6.12-9-686
lrwxrwxrwx 1 root root 25 2005-10-05 22:10 vmlinuz.old ->
boot/vmlinuz-2.6.10-5-386
drwxr-xr-x 2 root root 48 2005-10-05 21:38 windows
ls /bin garners similar results (although I don't have an exact copy... sorry)
Unfortuantely, I didn't think to thorughly read your e-mail (misread
the first line) before preceeding to run reiserfsck from a different,
newer live CD (that I had a friend burn), which ran just fine. While
some files have "dissapeared" into lost+found (which means they need
to be recatagorized or something, including everything in /boot), the
remainder of the files (maybe 94% of them or so) are now readable. I
have no idea whether or not this is considered "progress". Probably
now have to go sort them by magic or something, with filenames like
"25740_124378" on them. Anyways, thanks very much for your help,
you've done a great job with reiserfs.
--
~Mike
- Just my two cents
- No man is an island, and no man is unable.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: reiser3.6 files inaccessable from rescue CD post reiserfsck --rebuild-tree
2005-10-31 21:41 ` michael chang
@ 2005-11-01 12:12 ` Vladimir V. Saveliev
2005-11-01 12:28 ` Vladimir V. Saveliev
0 siblings, 1 reply; 6+ messages in thread
From: Vladimir V. Saveliev @ 2005-11-01 12:12 UTC (permalink / raw)
To: michael chang; +Cc: ReiserFS List
michael chang wrote:
> On 10/31/05, Vladimir V. Saveliev <vs@namesys.com> wrote:
>>Hello
>>
>>michael chang wrote:
>>>If I boot my Ubuntu install cd and run the "rescue" system, and try
>>>and select my reiserfs partition, it will fail, saying that it doesn't
>>>have the permisisons to execute /bin/bash.
>>>
>>Please boot off install cd so that it does not mount problem reiserfs partition
>>(/dev/hda5) as root filesystem.
>>Mount /dev/hda5 to /mnt and run ls /mnt/bin/ -l
>>What do you get?
>
> Other results that may be of relevance: (which explain why GRUB
> complains, and note that for some reason, by default, ls is aliased to
> "ls --color=auto")
>
> ubuntu@ubuntu:/mnt$ ls boot
> ls: boot/grub: Permission denied
> ls: boot/knoppix: Permission denied
> ls: boot/vmlinuz-2.6.12-9-686: Permission denied
> ls: boot/memtest86+.bin: Permission denied
> ls: boot/System.map-2.6.10-5-386: Permission denied
> ls: boot/abi-2.6.12-9-686: Permission denied
> ls: boot/config-2.6.10-5-386: Permission denied
> ls: boot/initrd.img-2.6.10-5-386: Permission denied
> ls: boot/System.map-2.6.12-9-686: Permission denied
> ls: boot/config-2.6.12-9-686: Permission denied
> ls: boot/initrd.img-2.6.12-9-686: Permission denied
> ls: boot/vmlinuz-2.6.10-5-386: Permission denied
> ubuntu@ubuntu:/mnt$ ls boot -l
> ls: boot/grub: Permission denied
> ls: boot/knoppix: Permission denied
> ls: boot/vmlinuz-2.6.12-9-686: Permission denied
> ls: boot/memtest86+.bin: Permission denied
> ls: boot/System.map-2.6.10-5-386: Permission denied
> ls: boot/abi-2.6.12-9-686: Permission denied
> ls: boot/config-2.6.10-5-386: Permission denied
> ls: boot/initrd.img-2.6.10-5-386: Permission denied
> ls: boot/System.map-2.6.12-9-686: Permission denied
> ls: boot/config-2.6.12-9-686: Permission denied
> ls: boot/initrd.img-2.6.12-9-686: Permission denied
> ls: boot/vmlinuz-2.6.10-5-386: Permission denied
> total 0
> ubuntu@ubuntu:/mnt$ ls boot --color=no
> abi-2.6.12-9-686 initrd.img-2.6.10-5-386 System.map-2.6.10-5-386
> config-2.6.10-5-386 initrd.img-2.6.12-9-686 System.map-2.6.12-9-686
> config-2.6.12-9-686 knoppix vmlinuz-2.6.10-5-386
> grub memtest86+.bin vmlinuz-2.6.12-9-686
>
> ubuntu@ubuntu:~$ ls /mnt -l
> total 371
> lrwxrwxrwx 1 root root 32 2005-10-09 00:24 Archive ->
> /windows/Downloads/media/Archive
> drwxr-xr-x 2 root root 48 2005-10-14 00:19 bin
> drwxr-xr-x 3 root root 72 2005-10-30 14:12 boot
> lrwxrwxrwx 1 root root 11 2005-10-05 21:38 cdrom -> media/cdrom
> drwxr-xr-x 12 root root 21688 2005-10-07 04:08 dev
> drwxr-xr-x 147 root root 7856 2005-10-30 14:36 etc
> drwxr-xr-x 2 root root 48 2005-10-05 21:38 hda6
> drwxr-xr-x 7 root root 176 2005-10-15 14:45 home
> drwxr-xr-x 2 root root 48 2005-10-05 21:39 initrd
> lrwxrwxrwx 1 root root 28 2005-10-14 00:20 initrd.img ->
> boot/initrd.img-2.6.12-9-686
> lrwxrwxrwx 1 root root 28 2005-10-05 22:10 initrd.img.old ->
> boot/initrd.img-2.6.10-5-386
> drwxr-xr-x 20 root root 4768 2005-10-14 00:19 lib
> drwx------ 794 root root 340208 2005-10-30 15:49 lost+found
> drwxr-xr-x 4 root root 128 2005-10-30 14:10 media
> drwxr-xr-x 2 root root 48 2005-03-31 19:09 mnt
> drwxr-xr-x 2 root root 48 2005-10-09 03:12 opt
> lrwxrwxrwx 1 root root 33 2005-10-09 00:24 Original ->
> /windows/Downloads/media/Original
> drwxr-xr-x 2 root root 48 2005-03-31 19:09 proc
> drwxr-xr-x 13 root root 520 2005-10-29 23:54 root
> drwxr-xr-x 2 root root 5120 2005-10-15 20:35 sbin
> drwxr-xr-x 2 root root 48 2005-10-05 21:39 srv
> drwxr-xr-x 2 root root 48 2005-10-23 04:26 swap
> drwxr-xr-x 2 root root 48 2005-03-23 22:41 sys
> drwxrwxrwt 7 root root 240 2005-10-30 14:36 tmp
> drwxr-xr-x 15 root root 376 2005-10-20 23:29 usr
> drwxr-xr-x 16 root root 384 2005-10-14 00:20 var
> lrwxrwxrwx 1 root root 25 2005-10-14 00:20 vmlinuz ->
> boot/vmlinuz-2.6.12-9-686
> lrwxrwxrwx 1 root root 25 2005-10-05 22:10 vmlinuz.old ->
> boot/vmlinuz-2.6.10-5-386
> drwxr-xr-x 2 root root 48 2005-10-05 21:38 windows
>
> ls /bin garners similar results (although I don't have an exact copy... sorry)
>
> Unfortuantely, I didn't think to thorughly read your e-mail (misread
> the first line) before preceeding to run reiserfsck from a different,
> newer live CD (that I had a friend burn), which ran just fine. While
> some files have "dissapeared" into lost+found (which means they need
> to be recatagorized or something, including everything in /boot), the
> remainder of the files (maybe 94% of them or so) are now readable. I
> have no idea whether or not this is considered "progress". Probably
> now have to go sort them by magic or something, with filenames like
> "25740_124378" on them.
It might also be useful for you if knew that this file was initially created in
directory whose id is 25740. If it is not removed yet you can try to find that
directory with find /mnt -inum 25740.
Anyways, thanks very much for your help,
> you've done a great job with reiserfs.
>
> --
> ~Mike
> - Just my two cents
> - No man is an island, and no man is unable.
>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: reiser3.6 files inaccessable from rescue CD post reiserfsck --rebuild-tree
2005-11-01 12:12 ` Vladimir V. Saveliev
@ 2005-11-01 12:28 ` Vladimir V. Saveliev
2005-11-02 0:03 ` michael chang
0 siblings, 1 reply; 6+ messages in thread
From: Vladimir V. Saveliev @ 2005-11-01 12:28 UTC (permalink / raw)
To: michael chang; +Cc: ReiserFS List
Hello
Vladimir V. Saveliev wrote:
>>
>>Unfortuantely, I didn't think to thorughly read your e-mail (misread
>>the first line) before preceeding to run reiserfsck from a different,
>>newer live CD (that I had a friend burn), which ran just fine. While
>>some files have "dissapeared" into lost+found (which means they need
>>to be recatagorized or something, including everything in /boot), the
>>remainder of the files (maybe 94% of them or so) are now readable. I
>>have no idea whether or not this is considered "progress". Probably
>>now have to go sort them by magic or something, with filenames like
>>"25740_124378" on them.
>
> It might also be useful for you if knew that this file was initially created in
I meant:
It might be useful if you knew that this file was initially created in a
directory whose id is 25740. You can try to find that directory with find /mnt
-inum 25740
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: reiser3.6 files inaccessable from rescue CD post reiserfsck --rebuild-tree
2005-11-01 12:28 ` Vladimir V. Saveliev
@ 2005-11-02 0:03 ` michael chang
0 siblings, 0 replies; 6+ messages in thread
From: michael chang @ 2005-11-02 0:03 UTC (permalink / raw)
To: Vladimir V. Saveliev; +Cc: ReiserFS List
On 11/1/05, Vladimir V. Saveliev <vs@namesys.com> wrote:
> Hello
>
> Vladimir V. Saveliev wrote:
> >>
> >>Unfortuantely, I didn't think to thorughly read your e-mail (misread
> >>the first line) before preceeding to run reiserfsck from a different,
> >>newer live CD (that I had a friend burn), which ran just fine. While
> >>some files have "dissapeared" into lost+found (which means they need
> >>to be recatagorized or something, including everything in /boot), the
> >>remainder of the files (maybe 94% of them or so) are now readable. I
> >>have no idea whether or not this is considered "progress". Probably
> >>now have to go sort them by magic or something, with filenames like
> >>"25740_124378" on them.
> >
> > It might also be useful for you if knew that this file was initially created in
>
> I meant:
> It might be useful if you knew that this file was initially created in a
> directory whose id is 25740. You can try to find that directory with find /mnt
> -inum 25740
>
I understood the original message, and the clarification was very
helpful. Thank you very much.
--
~Mike
- Just my two cents
- No man is an island, and no man is unable.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2005-11-02 0:03 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-10-30 23:55 reiser3.6 files inaccessable from rescue CD post reiserfsck --rebuild-tree michael chang
2005-10-31 8:34 ` Vladimir V. Saveliev
2005-10-31 21:41 ` michael chang
2005-11-01 12:12 ` Vladimir V. Saveliev
2005-11-01 12:28 ` Vladimir V. Saveliev
2005-11-02 0:03 ` michael chang
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.