Hi John: Forwarded your message to bug-hurd maillist. > After successfully completing an install, the computer froze at the stage where it was supposed to do an fsck during first boot. I booted to rescue mode and >edited a file to skip running fsck. Unfortunately, it froze at the same spot the next boot. Altogether I did four installs and about twelve boots. I wanted to get the >dmesg file, so I booted to rescue mode and tried to put it on a jump drive, but rescue mode wouldn't allow the jump drive to be mounted, nor could I read the >dmesg file.
Hurd uses ext2 filesystem. By this reason, if the system do a hard shutdown, you must to execute *fsck *to repair the filesystem, previously to the next boot. If not, the boot process will shows an error, saying the filesystem was not cleanly umount, and will ask you to execute a fsck. [image: imagen.png] If this error appears, you only have to press enter, and execute *fsck -y *to repair the filesystem If you press ctrl+d, the system will shows the same error during the next boot, and won't allow booting the system. El dom., 11 ago. 2019 a las 3:13, John Woodward (<jrwoodw...@electro-net.com>) escribió: > After successfully completing an install, the computer froze at the stage > where it was supposed to do an fsck during first boot. I booted to rescue > mode and edited a file to skip running fsck. Unfortunately, it froze at the > same spot the next boot. Altogether I did four installs and about twelve > boots. I wanted to get the dmesg file, so I booted to rescue mode and tried > to put it on a jump drive, but rescue mode wouldn't allow the jump drive to > be mounted, nor could I read the dmesg file. > > (These things may have happened because rescue mode doesn't have the > functionality, rather than because they were forbidden.) > > Since HURD wasn't going to boot, I moved on to play with another OS. I > would still like to know what caused the computer to hang -- it must be > whatever boot action comes right after the fsck, but I could never find > what that is. I realize this is thin information to diagnose the problem, > but is there any setting I choose during the install that could have caused > this problem? I tried lvm with encryption, lvm without encryption and > standard install with ext 3 or 4. Nothing made any difference. > > The computer was a 10-year-old Altec with 8g memory and an 80g drive. I > told the install program to partition the whole drive. > There were no hardware errors mentioned during the install. > > At some point I may try HURD on another computer. > > What I would like to know most off all is what happens right after > boot-time fsck. That's where things went bad. Perhaps you could send me a > dmesg file from a successful boot? Or at least the chunk starting on the > line just before the fsck and continuing for another twenty or so lines. > > Thank you. > > On 08 10, 2019, at 08:46 AM, Almudena Garcia <liberamenso10...@gmail.com> > wrote: > > Hi John: > > Explain us your problem, and we'll try to help you. > > Thanks > > > El sáb., 10 ago. 2019 a las 14:33, John Woodward (< > jrwoodw...@electro-net.com>) escribió: > I encountered a problem right off the bat. I need feedback as to whether > it was a bug or an error on my part.Thanks. > > > >
