After one of my two hard drives gave up the ghost, I've been suspicious that the player might somehow think it's still got two disk drives. Reasoning: I still see a "drive1" when I quit to the shell and type "ls". There have also been some other messages on the serial port which made me suspicious, such as "ext2fs_check_if_mount: No such file or directory while determining whether /dev/hda4 is mounted."

For reference, here's the chronology of events:

- Original system has 4gb drive.
- I temporarily remove the 4gb drive and put only the 6gb drive in the player.
- I use Mike's formatting kernel to format the 6gb drive.
- I install one of the Beta 10 versions of the player software onto that 6gb drive.
- I move the 6gb drive to the secondary controller and plug the 4gb back into the primary controller.
- I now have 10gb and it works well for several months.
- The 4gb drive goes south, so I remove it and put the 6gb on the primary controller.
- The 6gb drive works fine as my only drive and I upgrade the beta10 software to 1.01, and I re-upload my music (still had less than 6gb total to put in the player).

So does my player really think it's got more drives than it should? How do I tell it otherwise?

___________
Tony Fabris

I have a drive1 directory in the root of both my single drive empegs.
It's just a mount point, nothing to worry about... =)

Jazz
(List 112, Mk2 12 gig #40. Mk1 4 gig #30. Mk3 1.6 16v)

Okay, but every time I boot, it tells me that I need to run a disk check, and it's run several. I think it's telling me that the second nonexistent drive is the one that has to be checked.

___________
Tony Fabris

Might it be that the lines for the partition(s) on the second disk
haven't been removed from /etc/fstab?

Comment out (start the lines with #) any lines regarding the
second disk (/dev/hdc[x] for a MkI and /dev/hdb[x] for a MkII)

Might it be that the lines for the partition(s) on the second disk haven't been removed from /etc/fstab?

I dunno, here's what my etc/fstab looks like:

#
# /etc/fstab
#
#           
/dev/hda5       /               ext2          defaults,ro    1      1
/dev/hda4	/drive0		ext2	      defaults,ro    1	    1
none             /proc          proc          defaults

My bootup sequence looks like this (note that I'm running a modified kernel and init, hence the "not doing ioctl" and "running selecter" messages, these are my bootup selecter- could that be related?):

Registering drives...
ide0 at 0x040-0x047,0x078 on irq 7
hda: TOSHIBA MK6014MAP, 5729MB w/0kB Cache, CHS=12416/15/63
empeg-flash driver initialized
Partition check:
 hda: hda1 < hda5 hda6 > hda2 hda3 hda4
RAMDISK: Couldn't find valid RAM disk image starting at 0.
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 8k init
Running selecter (q to exit)
Not doing ioctl
Running player
empeg-car 1.01.

Is everything fine and I'm just paranoid, or have I done something wrong to my player?

___________
Tony Fabris

The warning about mounting an unchecked filesystem is caused by forgetting to "ro" when you leave the shell.

The way I got rid of it on mine is, I copied the file from a fresh debian-arm distribution (for some reason the fsck that comes with the empeg does not work). And ran it on the root filesystem. Seemed to do the trick.

But shouldn't a synch force an FSCK? I've synched many times since the last time I played at the shell.

___________
Tony Fabris

I believe sync only FSCKs the music partition, but I'm not certain. You need to FSCK the root partition. It could just take more syncs to check the root partition than the music partition.

Brian

-See my empeg here-

You need to FSCK the root partition.

Okay, cool. How do I do that?

___________
Tony Fabris

I wish I had my player with me so I could test this out. I'm pretty sure you just need to do an fsck.ext2 /dev/hda5

It should complain that the filesystem is mounted and you could mess it up. I'm fairly certain this is ok if the filesystem is mounted readonly. Although I take no responsibility if it trashes your root partition. If it does do that I would think an upgrade would fix it again.

I vaguely remember doing just that when I forgot to go back to ro before pulling power. Again I have not tested that today. If you want to wait I will try it as soon as I get home and post my results here.

Brian

-See my empeg here-

That took care of the message, thanks.

___________
Tony Fabris