PS Please pardon my imperfect spelling...
On Sat, Jun 6, 2009 at 12:43 PM, hyperfitz <hyperf...@gmail.com> wrote: > Alright, Ted is not listening anymore, and he was not totally belligerent > this time, so I will bite my tongue with some of what I have to say to him. > What I will say is this. The error I experienced is not from multiple file > systems labeled "/". And, deleting fsck is not that big of a deal! If you > are entirely non-proactive with protecting any of your data, then there is a > chance that, in the long run, you may experience data loss due to file > system errors. Fsck, however, will not protect you against hardware > failures, which are probably as common as file system errors. You should, > therefore, be backing up your data, period. This has been true for the last > 30 years, at least. > > Now, if you are a Ubuntu user and you are experiencing an error in which > your system will not boot because it locks up on the boot-time file system > check, then you can drop into a root prompt (which the grub boot loader has > labeled as "recovery" in its boot-time menu, if I am not mistaken) and you > can delete the fsck binaries from your /sbin directory. This should make > your computer run normally again. If you do this, it is probably a good idea > to run a file system check periodically. You can do this with a live CD, or > a bootable flash memory stick, etc. However, there is a significant chance > that you will experience a hardware failure before you experience a file > system error, so back up any data you care about in general. > > My apologies to any developers who have heard this who were looking for > something more interesting. My post was never aimed at you. My target was > users, who usually just want there computer to work. I understand the > frustration in a post like mine and I am sorry for not posting something > more useful to you. > > I am not the only person who has experienced a problem like this. However, > if you want to blame it on me, then it is possibly a hardware problem. I > have a significantly buggy EliteGroup motherboard, and I have been too cheap > to replace it. There is a chance that this problem has nothing to do with > any OS level code. > > If it happens again, I will do something that may be more useful for > developers. > > > On Thu, Jun 4, 2009 at 5:28 AM, Theodore Ts'o <ty...@mit.edu> wrote: > >> On Thu, Jun 04, 2009 at 04:26:20AM -0000, Hyperfitz wrote: >> > Wow, this is constructive. For the record, there is nothing wrong with >> my >> > file system. There is, however, something wrong with the check that >> happens >> > at boot. It is not user error, sorry if you think otherwise--doesn't >> change >> > the facts. My suggestion is hardly (in the slightest) like telling >> people to >> > drive around without seat belts. You ought to know just a little bit >> more >> > about people before you simply start insulting them, Theodore. You know >> > nothing about me--not one little thing. >> >> The problem is there's not enough information to do anything >> interesting with your report. You can't even tell me what errors were >> being reported by fsck. >> >> In the case of the original bug reporter, it was clear that there was >> a confusion caused by Ubuntu labelling multiple filesystems with the >> label name "/". I don't know what's going on with your case. But I >> can say that no other users from any other distributions have reported >> anything like this. So I'm pretty confident it is either user error >> or some other kind of confusion. >> >> In any case, this bug report was marked as incomplete over a year ago >> due to a lack of information, and I am now unsubscribing from this bug >> report as it is clear there is no intelligent life here. If someone >> else wants to report a related issue, please open a new bug with full >> details if you want any help. If you want to just vent about how >> unfair life is, and how much Ubuntu, or e2fsprogs sucks, please feel >> free to do it where you want. If you want to suggest to people that >> deleting fsck binaries are a sane thing to do, I don't want to have >> any involvement in it, as that will only lead to tears. >> >> - Ted >> >> -- >> filesystem check fails on boot, but filesystem isn't bad >> https://bugs.launchpad.net/bugs/48563 >> You received this bug notification because you are a direct subscriber >> of the bug. >> >> Status in “e2fsprogs” source package in Ubuntu: Incomplete >> >> Bug description: >> Binary package hint: e2fsprogs >> >> Hello, >> >> I've just installed ubuntu dapper drake, and I have a persistent problem >> where it fails the filesystem check during bootup, and I get dropped into a >> root shell. Ignoring the problem lets me boot up, and if I check the >> filesystem from the live CD (with fsck /dev/hda -f) it comes up clean. For >> some reason it seems to be checking the root filesystem (/dev/hda5) even >> though that's already been checked earlier on, and should be mounted at this >> stage. The other filesystems check clean. I looked at the script >> (/etc/rcS.d/S30checkfs.sh), and the fsck command includes the '-R' flag >> which should tell it not to check the root filesystem, so I don't understand >> why this is happening. As far as I can guess, the problem is that: a) for >> some reason fsck is not picking up the fact that dev/hda5 is mounted as >> root. b) because of this, it's checking the filesystem while still mounted, >> and finding an error because of that. >> >> I've tried doing the following: >> - booting from a live CD and checking the filesystem from that, including >> a read/write bad blocks test. It always comes up clean or with a minor >> error, but the same error comes up again when I reboot from the hard disk. >> - rebuilding my partition table using fdisk (writing down the cylinder >> numbers, deleting it and recerating it) >> - looking at fstab. It's pasted below. >> >> # /etc/fstab: static file system information. >> # >> # <file system> <mount point> <type> <options> <dump> <pass> >> proc /proc proc defaults 0 0 >> /dev/hda5 / ext3 defaults,errors=remount-ro 0 >> 1 >> /dev/hda3 /local ext3 defaults 0 2 >> /dev/hda1 /media/hda1 ext3 defaults 0 2 >> /dev/hda4 /media/hda4 ext3 defaults 0 2 >> /dev/hda7 /var ext3 defaults 0 2 >> /dev/hda6 none swap sw 0 0 >> /dev/hdc /media/cdrom0 udf,iso9660 user,noauto 0 0 >> /local/home /home auto defaults,bind 0 0 >> /local/usr-local /usr/local auto defaults,bind 0 0 >> >> For the moment I'm carrying on using the system as it is, but I'm not >> happy to do this in the long term if there's a persistent error. I've tried >> to do everything I can to fix the problem, and it hasn't worked, so I'm >> filing this as a possible bug. If you need any help finding the problem, I'm >> happy to post logs etc. >> > > -- filesystem check fails on boot, but filesystem isn't bad https://bugs.launchpad.net/bugs/48563 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
