Error in boot-uponly with win98 HDD installed

lilsirecho · 2003-12-05 06:51:54

Gents:

Desire to report a bug in arch 0.5 downloaded Oct 18, 2003.

Utilized arch 0.5 for some time but after installing arch linux, slackwareeline 9.0 and slackware linux 9.1 along with windows 98 in my system I encountered inability to load arch 0.5 until win98 HDD was removed.

Initial setup of the system operated correctly, each linux OS capable of mounting partitions of the other, whether it was arch to slackware or the reverse. This capability was in addition to accessing vfat on two HDD having fat file systems(one is a USB device the other the secondary slave. However, upon reboot, an fsck fail occurred asking for: " mount -n -o remount, rw/" . This notation appears in : man fsck....

I wish to pursue a bug description since this indicates a cross OS fault with win98 file systems/HDD.

The boot is selected in bios before initiating same.

How do I submit a bug?

zen_guerrilla · 2003-12-05 16:23:52

I'm not sure I understood your problem, could u pls clear it up a little bit ?
I successfully dual-boot AL with win 98/xp in lots of boxes (in a laptop at work I even triple-boot win98, xp & AL, all controlled by AL's grub...).
I'm suspecting a misconfiguration here...

lilsirecho · 2003-12-05 18:59:09

Sorry I must be more careful in describing the complex problem.

I utilize a pciide card to extend hdd capability,

I change boot-up HDD in bios for four mobo HDD as is standard.
I cannot boot on pciide card hdd's.

I have win98 on sec-slave, with no other OS partitioned.

I have slackware 9.0 attached to pciide slot sec-master with no partitions to other OS's.

I have slackware 9.1 attached to pri-master when used as the in-use HDD. It has access to partitions on arch, win98, and slckware 9.0.

I can install arch in pri-slave when using slackware as OS.

I can install arch as OS and slackware 9.0 as pri-slave and have access to partitions on all other HDD.

I also have a USB HDD which is accessible from the OS in all cases.

The problem in arch 0.5 is that after setting up the accessibilities in Linux and win98 HDD's, at next reboot I could not pass fsck. This condition persisted until I removed the win98HDD which cleared the problem.

In win98, the OS does not recognize any Linux HDD's.

In arch0.5, the presence of win98 HDD prevents arch 0.5 from booting.

I read ....."man fsck"... and it refers to drives as "/dev/hda...etc" and this type of ID does not apply to kernel 2.4.21 which uses /dev/discs/discX/partx and therefore I feel therein lies a bug. This seems to be true since I am booting kernel 2.4.21 in arch0.5 which ID's hdd's in a mode other than specified in fsck.

If fsck "sees" the win98HDD through the /dev/hdx search(supposedly a multiple parallel hdd check) it most certainly will fail the arch0.5 boot-up AFAICT.

Perhaps I have improved your understanding of my problem..I use lilo for booting and have ....append="hde=ide-scsi ide=reverse" to allow for pciide ID after mobo ID and to enable cdrw in pcide slot primary-pri.

If further info needed, I am ready to try.

lilsirecho · 2003-12-05 19:15:38

You refer to dual-boot as used in your system.

I am not dual-booting as my post explains but am singleOS booting with partition access to other HDD's.

zen_guerrilla · 2003-12-05 19:20:19

lilsirecho wrote:

The problem in arch 0.5 is that after setting up the accessibilities in Linux and win98 HDD's, at next reboot I could not pass fsck. This condition persisted until I removed the win98HDD which cleared the problem.

Obviously you have wrong entries in /etc/fstab in your arch installation & that's why it stops in fsck.

lilsirecho · 2003-12-05 19:47:03

I assume if it is working correctly in arch that it has to be correct.

Fstab:#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>

#/dev/#EXT2FS_BOOT# /boot ext2 defaults 0 1
#/dev/#REISERFS_ROOT# / reiserfs defaults 0 0
#/dev/#EXT2FS_ROOT# / ext2 defaults 0 1
#/dev/#SWAP# swap swap defaults 0 0
#/dev/#REISERFS_HOME# /home reiserfs defaults 0 0
#/dev/#EXT2FS_HOME# /home ext2 defaults 0 2

/dev/cdroms/cdrom0 /mnt/cd iso9660 ro,owner,noauto,unhide 0 0
/dev/cdroms/cdrom0 /mnt/dvd udf ro,owner,noauto,unhide 0 0
/dev/floppy/0 /mnt/fl vfat owner,noauto,unhide 0 0
none /proc proc defaults 0 0
none /dev/shm tmpfs defaults 0 0
tmpfs /tmp tmpfs size=2G,nr_inodes=10k 0 0

/dev/discs/disc0/part3 / ext3 defaults 0 1
/dev/discs/disc0/part1 /boot ext2 defaults 0 1
/dev/discs/disc0/part2 swap swap defaults 0 0
/dev/discs/disc1/part1 /mnt/fat vfat defaults 1 0
/dev/discs/disc2/part1 /mnt/fat1 vfat defaults 1 0
/dev/sda1 /mnt/fat2 vfat defaults 0 0
/dev/cdroms/cdrom1 /mnt/cdrw iso9660 ro,owner,noauto 0 0
/dev/discs/disc1/part3 /disc1 ext3 defaults 0 1
/dev/discs/disc1/part1 /disc1 ext3 defaults 0 1

Xentac · 2003-12-05 20:17:17

Get rid of those 1's at the end of the vfat entries. Pretty sure they should be 0 0.

lilsirecho · 2003-12-05 20:21:15

xentac

Will try that after attending funeral here....

lilsirecho · 2003-12-05 23:58:08

This is fstab now which did not solve the problem:#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>

#/dev/#EXT2FS_BOOT# /boot ext2 defaults 0 1
#/dev/#REISERFS_ROOT# / reiserfs defaults 0 0
#/dev/#EXT2FS_ROOT# / ext2 defaults 0 1
#/dev/#SWAP# swap swap defaults 0 0
#/dev/#REISERFS_HOME# /home reiserfs defaults 0 0
#/dev/#EXT2FS_HOME# /home ext2 defaults 0 2

/dev/cdroms/cdrom0 /mnt/cd iso9660 ro,owner,noauto,unhide 0 0
/dev/cdroms/cdrom0 /mnt/dvd udf ro,owner,noauto,unhide 0 0
/dev/floppy/0 /mnt/fl vfat owner,noauto,unhide 0 0
none /proc proc defaults 0 0
none /dev/shm tmpfs defaults 0 0
tmpfs /tmp tmpfs size=2G,nr_inodes=10k 0 0

/dev/discs/disc0/part3 / ext3 defaults 0 1
/dev/discs/disc0/part1 /boot ext2 defaults 0 1
/dev/discs/disc0/part2 swap swap defaults 0 0
/dev/discs/disc1/part1 /mnt/fat vfat defaults 0 0
/dev/discs/disc2/part1 /mnt/fat1 vfat defaults 0 0
/dev/sda1 /mnt/fat2 vfat defaults 0 0
/dev/cdroms/cdrom1 /mnt/cdrw iso9660 ro,owner,noauto 0 0
/dev/discs/disc1/part3 /disc1 ext3 defaults 0 1
/dev/discs/disc1/part1 /disc1 ext3 defaults 0 1

Xentac · 2003-12-06 00:05:34

Can you give like all of the error message, from the daemon start line (or whatever). More or less the whole page... I can't think of an easy way to copy it...

Having that other info will help to give more context to the error.

lilsirecho · 2003-12-06 00:14:16

The error message appears in the last post of my newbie post for : deleted /etc/rc.conf on page 4...

Xentac · 2003-12-06 00:24:35

That's your bootup script, not the error messages.

The really important stuff is the stuff you see above the first set of ***********'s

And I can't remember where you said it, but the error message does tell you that something's up and you should be aware of it. "FILESYSTEM CHECK FAILED" and "Please repair manually and reboot". It doesn't tell you you have to run the remount command, only if you want to change the root filesystem to read-write.

By having 0 0, fsck should not be trying to scan that partition. If commenting out the win98 partition it lets you boot everything fine, it means that fsck is having problems with the win98 partition. You have to find some way to tell fsck not to check the win98 partition (which makes sense, I don't know of any vfat filesystem checkers for linux).

zen_guerrilla · 2003-12-06 01:26:51

Xentac wrote:

I don't know of any vfat filesystem checkers for linux.

$ pacman -Q -l dosfstools  | grep fsck
dosfstools /sbin/dosfsck
dosfstools /sbin/fsck.msdos
dosfstools /sbin/fsck.vfat
dosfstools /usr/man/man8/dosfsck.8.gz
dosfstools /usr/man/man8/fsck.msdos.8.gz
dosfstools /usr/man/man8/fsck.vfat.8.gz

lilsirecho · 2003-12-06 02:48:46

I am afraid that I took the information that you referenced, Xentac ,as the error message since the item adjacent stated that the fsck failed and it was followed by the message which I presented with the data on page 4 post as noted in previous post. It made little sense to me and am not sure it does now...

In any case, fsck does hdd search(and maybe destroy?) and according to ...man fsck... checks hdd's in parallel using /dev/hdx as an addressor.

Since we are discussing arch on an arch forum, I have left out the next cross-OS fail. It concerns slackware and windows wherein win98 fails to boot until slack is removed.

Noted a number of items listed by zen-guerilla which might be of some interest....they reference fsck and dos.

I am on slack right now in primary-pri with arch0.5 in
primary-slave and win98 is removed. I have installed two switches for the jumper slots to enable easy interchange since each of the drives is either hda or /dev/discs/disc0
as determined by the systemOS.

lilsirecho · 2003-12-09 00:33:24

I have discovered that the win98 hdd was causing the problem in both arch and slackware.

All is well now and no bug report seems necessary although the inter-OS impact might be noted.

Thanks to all for their kind support.

Arch Linux

#1 2003-12-05 06:51:54

Error in boot-uponly with win98 HDD installed

#2 2003-12-05 16:23:52

Re: Error in boot-uponly with win98 HDD installed

#3 2003-12-05 18:59:09

Re: Error in boot-uponly with win98 HDD installed

#4 2003-12-05 19:15:38

Re: Error in boot-uponly with win98 HDD installed

#5 2003-12-05 19:20:19

Re: Error in boot-uponly with win98 HDD installed

#6 2003-12-05 19:47:03

Re: Error in boot-uponly with win98 HDD installed

#7 2003-12-05 20:17:17

Re: Error in boot-uponly with win98 HDD installed

#8 2003-12-05 20:21:15

Re: Error in boot-uponly with win98 HDD installed

#9 2003-12-05 23:58:08

Re: Error in boot-uponly with win98 HDD installed

#10 2003-12-06 00:05:34

Re: Error in boot-uponly with win98 HDD installed

#11 2003-12-06 00:14:16

Re: Error in boot-uponly with win98 HDD installed

#12 2003-12-06 00:24:35

Re: Error in boot-uponly with win98 HDD installed

#13 2003-12-06 01:26:51

Re: Error in boot-uponly with win98 HDD installed

#14 2003-12-06 02:48:46

Re: Error in boot-uponly with win98 HDD installed

#15 2003-12-09 00:33:24

Re: Error in boot-uponly with win98 HDD installed

Board footer