partition cannot be mounted from grub
Hi, Using Suse 10.1, I had a spontaneous reboot after which I got a fast running screen full of reiserfs messages. Another (inflicted) reboot and Grub gives error 17, meaning it cannot mount a recognized partition. Using the boot-dvd, I selected Rescue, and logged in as root but I have no idea how to proceed trying to save my system. Help is appreciated. Thanks, Huub
Re: partition cannot be mounted from grub
Huub wrote: Hi, Using Suse 10.1, I had a spontaneous reboot after which I got a fast running screen full of reiserfs messages. Another (inflicted) reboot and Grub gives error 17, meaning it cannot mount a recognized partition. Using the boot-dvd, I selected Rescue, and logged in as root but I have no idea how to proceed trying to save my system. Help is appreciated. Thanks, Huub Correction: errormessage means: This error is returned if the partition requested exists, but the filesystem type cannot be recognized by GRUB. I.e. GRUB doesn't recognize it's a ReiserFS partition...
Re: reiser4 resize
Alexey Polyakov wrote:
On 9/20/06, Łukasz Mierzwa [EMAIL PROTECTED] wrote:
It's been proven that flushes are doing much more job then they should.
Not so long ago someone send a trace of block device io accesess during
reiser4 work and someone anylized it and said that some files or parts of
file where written over and over 200 times or so.
Wow. I should go back and read that -- I assume this is being worked on?
a few months old filesystem that had been used often just shows a week
spot in reiser4, while downloading files with azureus with only 64KB of
data per second I got disk lid on almost all the time, swithcing to
rtorrent helped as it does not seem to call fsync ( I think I disabled
fsync in azureus).
Hmm, strange. I am using Azureus, but I don't think it's fsync. I can
try rtorrent, but there are several things I like about Azureus that
nothing else seems to do yet.
But also, Azureus didn't always do this. In fact, I used it for several
months before I started having this problem.
Ah, I see, if bittorrent calls fsync often, it's no wonder that
reiser4 behaves badly. I had to preload libnosync for some of my
programs that do fsync to avoid this.
Way ahead of you. I noticed how much fsync performance sucked when
using vim, and I was sick of waiting 10 seconds every time I hit :w -- a
LOT of stuff can pile up in 2 gigs of disk buffer, and at the time,
Reiser4 fsync effectively just called sync.
I didn't know about libnosync (or it didn't exist yet, or didn't work,
I'm not entirely sure), so I was faced with either patching vim, which
had just been patched to _add_ fsync'ing, not to mention all the other
programs that might fsync too much; patching glibc (huge, I don't
update it often, and I'd have no idea where to start); or patching the
kernel.
I now keep backups, and I maintain and apply the following (STUPID,
DON'T TRY THIS AT HOME) patch to my kernel:
--- linux/fs/buffer.c 2006-08-15 20:40:36.504608696 -0500
+++ linux/fs/buffer.c.new 2006-08-15 20:42:35.877461264 -0500
@@ -366,12 +366,12 @@
asmlinkage long sys_fsync(unsigned int fd)
{
- return __do_fsync(fd, 0);
+ return 0;
}
asmlinkage long sys_fdatasync(unsigned int fd)
{
- return __do_fsync(fd, 1);
+ return 0;
}
/*
Re: reiser4 resize
Alexey Polyakov wrote: On 9/19/06, David Masover [EMAIL PROTECTED] wrote: When I have over a gig of RAM free (not even buffer/cache, but _free_), and am trying to download anything over BitTorrent, even if it's less than 200 megs, the disk thrashes so badly that the system is really only usable for web and email. Even movies will occasionally stall when this is happening, and by occasionally, I mean every minute or so. Do you have this problem on plain vanilla + reiser4? Yes. Well, no. My kernel is: vanilla 2.6.17.13 on amd64 patches: sk98lin 8.36, latest from the manufacturer reiser4-for-2.6.17-3 my own patch that disables fsync and fdatasync external modules, installed via Portage: ALSA 1.0.11 driver, using snd_emu10k1 and all sorts of support stuff (OSS emulation, synth, etc) nvidia driver, 1.0.8762 I've also been having a bit of instability issues, but only very rarely do these seem at all FS-related. I'm overclocked a bit, and I can reliably crash my system by playing Neverball, Doom 3, or Quake 4 for several hours. I strongly suspect this is either my overclocking or the nvidia drivers here. However, I doubt anything I've done beyond vanilla+reiser4 is affecting this disk access issue, and I'm pretty much rock solid when I'm not playing a game. I also have a close-to-identical machine nearby which is not overclocked, same kernel, same modules, everything except the nvidia driver, been rock solid for a year, no performance issues to speak of. The main difference, other than graphics, is that the stable machine is using 21 gigs out of 72, whereas the unstable one (the one that's sluggish for BitTorrent) is using 279 gigs out of 350, and has been up to 320 or 330 at least before I started cleaning things out. So I think we're down to two possibilities: Either an update to Azureus has found a way to sync that I'm not aware of, or this is the behavior someone described where Reiser4 will attempt to find contiguous space to allocate, and continue searching and re-searching the same areas of the disk almost every write. To be honest, I hope it's about syncing, somehow, because I'd much rather believe my disk isn't horrendously fragmented...
Re: reiser4 resize
Dnia Thu, 21 Sep 2006 09:30:09 +0200, David Masover [EMAIL PROTECTED]
napisał:
--- linux/fs/buffer.c 2006-08-15 20:40:36.504608696 -0500
+++ linux/fs/buffer.c.new 2006-08-15 20:42:35.877461264 -0500
@@ -366,12 +366,12 @@
asmlinkage long sys_fsync(unsigned int fd)
{
- return __do_fsync(fd, 0);
+ return 0;
}
asmlinkage long sys_fdatasync(unsigned int fd)
{
- return __do_fsync(fd, 1);
+ return 0;
}
/*
I remember that I played a little with disabling sync in reiser4 sources,
it helped only for amarok (it's uses sqlite for storing statistic data and
it writes to it on song change, sqlite calls sync and it ends up with
writeing to disk instead of playing a song, at least on my fs),
bittorrents clients were generating as lot of disk as previously so I gues
it's more likely coused by data/tree fragmentation.
Just my 0,6374526$ ;)
Re: reiser4 resize
Dnia Thu, 21 Sep 2006 09:30:09 +0200, David Masover [EMAIL PROTECTED] napisał: On 9/20/06, Łukasz Mierzwa [EMAIL PROTECTED] wrote: It's been proven that flushes are doing much more job then they should. Not so long ago someone send a trace of block device io accesess during reiser4 work and someone anylized it and said that some files or parts of file where written over and over 200 times or so. Wow. I should go back and read that -- I assume this is being worked on? Well it was not a file but a block, but the effect is the same. http://marc.theaimsgroup.com/?l=reiserfsm=115488109712570w=2
Re: partition cannot be mounted from grub
Hello On Thursday 21 September 2006 09:57, Huub wrote: Hi, Using Suse 10.1, I had a spontaneous reboot after which I got a fast running screen full of reiserfs messages. Another (inflicted) reboot and Grub gives error 17, meaning it cannot mount a recognized partition. Using the boot-dvd, I selected Rescue, and logged in as root but I have no idea how to proceed trying to save my system. Help is appreciated. being booted off boot-dvd, please, run reiserfsck for partitions which were formatted as reiserfs and let us see reiserfsck' output. Thanks, Huub
Re: partition cannot be mounted from grub
being booted off boot-dvd, please, run reiserfsck for partitions which were formatted as reiserfs and let us see reiserfsck' output. fdisk /dev/hdc shows that I have: /dev/hdc1 Linux swap /dev/hdc2 * Linux /dev/hdc3 Linux As I stated in my own response, error 17 means it doesn't recognize a partition as being ReiserFS. Should I do reiserfsck /dev/hdc2 anyway?
Re: r4 observations
Hello On Wednesday 20 September 2006 22:47, Peter wrote: I booted from a non-reiser4 partition in order to make a backup of my main / which was a r4 partition. After the backup, I unmounted the drive explicitly, then rebooted. I did not use the backed up drive for anything except tar-ring its files. On next boot to the r4 / partition, all kinds of file not found errors occurred. I booted again to my non-r4 partition, and ran fsck.reiser4 --check -y there were fatal errors on my r4 /. The backup was fine. I downgraded back to reiserfs which does not exhibit this problem. I have not experienced any problem with other r4 partitions. Just /. /home, /tmp, /src, etc. are fine. Unfortunately, I don't have time to keep wondering where the problem is or why. Perhaps it's the kernel or the init scripts. Nonetheless, the instability of whatever the problem is is unnerving. Please provide information about which kernel and which reiser4 did you use. Am I correct that you were trying to run gentoo on reiser4?
Re: partition cannot be mounted from grub
On Thu, 21 Sep 2006 08:16:26 +0200, Huub wrote: Huub wrote: Hi, Using Suse 10.1, I had a spontaneous reboot after which I got a fast running screen full of reiserfs messages. Another (inflicted) reboot and Grub gives error 17, meaning it cannot mount a recognized partition. Using the boot-dvd, I selected Rescue, and logged in as root but I have no idea how to proceed trying to save my system. Help is appreciated. Thanks, Huub Correction: errormessage means: This error is returned if the partition requested exists, but the filesystem type cannot be recognized by GRUB. I.e. GRUB doesn't recognize it's a ReiserFS partition... Two suggestions. 1) I have found that grub files in r3 have to be copied using -o notail on the mount command. If you do not use notail, the files are not able to be read by grub. 2) do not try and create a grub boot while in the r3 partition. Make sure the partition is unmounted, then boot from a live cd and run grub from there. e.g. in your case, with /dev/hdc2 being your root root(hd2,1) # at this point grub should respond that filesystem is reiserfs setup(hd2) # at this point, grub should install the boot loader. # unless hdc is NOT your boot disk. If not, then use hd0 or 1. If not, try recopying /boot/grub by doing this from the live cd. mount /dev/hdc2 /mnt/wherever -o notail,rw,[noatime] cd /boot cp -rP grub grub2 rm -fr grub mv grub2 grub then umount it and try the grub commands above. I have had lots of woes with grub and reiser 3/4. This seems to work for me. -- Peter + Do not reply to this email, it is a spam trap and not monitored. I can be reached via this list, or via jabber: pete4abw at jabber.org ICQ: 73676357
Re: r4 observations
On Thu, 21 Sep 2006 15:02:01 +0400, Vladimir V. Saveliev wrote: Hello On Wednesday 20 September 2006 22:47, Peter wrote: I booted from a non-reiser4 partition in order to make a backup of my main / which was a r4 partition. After the backup, I unmounted the drive explicitly, then rebooted. I did not use the backed up drive for anything except tar-ring its files. On next boot to the r4 / partition, all kinds of file not found errors occurred. I booted again to my non-r4 partition, and ran fsck.reiser4 --check -y there were fatal errors on my r4 /. The backup was fine. I downgraded back to reiserfs which does not exhibit this problem. I have not experienced any problem with other r4 partitions. Just /. /home, /tmp, /src, etc. are fine. Unfortunately, I don't have time to keep wondering where the problem is or why. Perhaps it's the kernel or the init scripts. Nonetheless, the instability of whatever the problem is is unnerving. Please provide information about which kernel and which reiser4 did you use. Am I correct that you were trying to run gentoo on reiser4? Yes, Vladimir. When making the backup, I was not running Gentoo at all. I was running Slackware 10.2. I booted into Slackware with the beyond patchset (ck superset) based on 2.6.17.11 with the reiser4 2.6.17-3 patch. All of the work on backup mount and unmount was on Slackware. It was when rebooting back into Gentoo (with the init and base layout which DID NOT CAUSE a boot problem) that the fatal errors occurred. Interestingly, and maybe this is helpful, only the / partition seems to be affected. I have observed no problematic behavior with any of the other three partitions I used r4 for. In fact, even though I downgraded / to reiserfs3, the other r4 partitions work fine. Please let me know if I can provide additional information. -- Peter + Do not reply to this email, it is a spam trap and not monitored. I can be reached via this list, or via jabber: pete4abw at jabber.org ICQ: 73676357
Re: partition cannot be mounted from grub
Hello On Thursday 21 September 2006 14:19, Huub wrote: being booted off boot-dvd, please, run reiserfsck for partitions which were formatted as reiserfs and let us see reiserfsck' output. fdisk /dev/hdc shows that I have: /dev/hdc1 Linux swap /dev/hdc2 * Linux /dev/hdc3 Linux As I stated in my own response, error 17 means it doesn't recognize a partition as being ReiserFS. Should I do reiserfsck /dev/hdc2 anyway? yes that should give us a hint whether the problem is in reiserfs or in grub
Re: partition cannot be mounted from grub
yes that should give us a hint whether the problem is in reiserfs or in grub Looks like I can do a clean install. No filesystem or superblock found.
Re: partition cannot be mounted from grub
Hello On Thursday 21 September 2006 16:14, Huub wrote: yes that should give us a hint whether the problem is in reiserfs or in grub Looks like I can do a clean install. If there is no important data on the system - this is the easiest way. No filesystem or superblock found. I would guess that you got partition table corruption. You may want to try to fdisk /dev/hdc in the way it was partitioned before. However, boundaries of partitions are to known presizely for that, though. You may also try gpart(8). It does not look at partition table and may find partition boundaries.
Re: partition cannot be mounted from grub
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Peter wrote: Two suggestions. 1) I have found that grub files in r3 have to be copied using -o notail on the mount command. If you do not use notail, the files are not able to be read by grub. 2) do not try and create a grub boot while in the r3 partition. Make sure the partition is unmounted, then boot from a live cd and run grub from there. I'm curious what version of grub caused you to come to these conclusions. Grub has been using the REISERFS_IOC_UNPACK ioctl for ages. It's the same thing lilo uses and causes those files to only use indirect blocks (ie: no tails). If you've been running into this problem with any recent version of grub, it's a bug. - -Jeff - -- Jeff Mahoney SUSE Labs -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFFEptrLPWxlyuTD7IRAlsHAJ9GvQ/jJDKbWmCuAlmJxcwcl66gJwCgot5t qQBPRVmv5OWTwJ2VPX4facE= =x/4R -END PGP SIGNATURE-
Re: partition cannot be mounted from grub
On Thu, 21 Sep 2006 10:02:19 -0400, Jeff Mahoney wrote: snip... I'm curious what version of grub caused you to come to these conclusions. Grub has been using the REISERFS_IOC_UNPACK ioctl for ages. It's the same thing lilo uses and causes those files to only use indirect blocks (ie: no tails). If you've been running into this problem with any recent version of grub, it's a bug. - -Jeff 0.94/0.97 (not grub2). Just happened yesterday as a test. I also found it impossible to run grub in its /boot/grub mounted partition. I had to boot off another partition or a live cd and run grub from there. I did not find this trouble with r4 however. Just my experience however. -- Peter + Do not reply to this email, it is a spam trap and not monitored. I can be reached via this list, or via jabber: pete4abw at jabber.org ICQ: 73676357
Re: partition cannot be mounted from grub
I would guess that you got partition table corruption. You may want to try to fdisk /dev/hdc in the way it was partitioned before. However, boundaries of partitions are to known presizely for that, though. You may also try gpart(8). It does not look at partition table and may find partition boundaries. Reinstalled Suse 10.1 from scratch. Went very smooth. Running again...just curious for how long. Another question however: is ReiserFS capable of handling sudden reboots? I suspect my systemboard needs to be replaced since it reboot or freezes now and then, but so far I never had an fs being ruined beyond repair.
