#284134 - 07/07/2006 16:38
Problem with new Disk installation
|
new poster
Registered: 25/07/2003
Posts: 48
Loc: Reading UK
|
Hi
I have searched.
I am attempting a brand new disk install. I am at the step in the FAQ guide where the Disk Builder image is run. I get an error that says "error couldn't find pump".
The disk is in IDE0. I have recrimped the IDE0 and also tried the IDE1 location.
I tried installing V2.00 Developer, that went OK then followed with the Disk Builder, but the Disk Imager won't run still so I can't begin putting music onto the new disk.
_________________________
Empeg V2 60GB running v3 (alpha 11) and the autoupdated hijack from jemplode.
|
|
Top
|
|
|
|
|
#284135 - 07/07/2006 16:42
Re: Problem with new Disk installation
[Re: estocks]
|
carpal tunnel
Registered: 25/06/1999
Posts: 2993
Loc: Wareham, Dorset, UK
|
Usual drill - serial log capture, post it here, blah blah
_________________________
One of the few remaining Mk1 owners...  #00015
|
|
Top
|
|
|
|
|
#284136 - 07/07/2006 16:42
Re: Problem with new Disk installation
[Re: estocks]
|
carpal tunnel
Registered: 19/01/2002
Posts: 3584
Loc: Columbus, OH
|
Is the disk more than 60 gig or so? If so, you'll need to manually format and partition it instead of using the disk builder image that is referenced in the drive upgrade guide. Roger's got some instructions somewhere.
EDIT: They're linked from the guide. Read the section entitled "Special note for large drives:".
Edited by JBjorgen (07/07/2006 16:45)
_________________________
~ John
|
|
Top
|
|
|
|
|
#284137 - 07/07/2006 17:10
Re: Problem with new Disk installation
[Re: JBjorgen]
|
new poster
Registered: 25/07/2003
Posts: 48
Loc: Reading UK
|
It is s 60GB. @scofeil I connect to the player with HT after the fail and record empeg-car bootstrap v1.02 20001106 ( [email protected]) If there is anyone present who wants to upgrade the flash, let them speak now, or forever hold their peace... empeg-car bootstrap v1.02 20001106 ( [email protected]) If there is anyone present who wants to upgrade the flash, let them speak now, or forever hold their peace... empeg-car bootstrap v1.02 20001106 ( [email protected]) If there is anyone present who wants to upgrade the flash, let them speak now, or forever hold their peace...it s empeg-car bootstrap v1.02 20001106 (hugo@empeg .com) If there is anyone present who wants to upgrade the flash, let them speak now, or forever hold their peace... empeg-car bootstrap v1.02 20001106 ( [email protected]) If there is anyone present who wants to upgrade the flash, let them speak now, or forever hold their peace...
_________________________
Empeg V2 60GB running v3 (alpha 11) and the autoupdated hijack from jemplode.
|
|
Top
|
|
|
|
|
#284138 - 07/07/2006 17:17
Re: Problem with new Disk installation
[Re: estocks]
|
carpal tunnel
Registered: 15/08/2000
Posts: 4859
Loc: New Jersey, USA
|
Okay. Brand new drive. 60GB. Try this...
- Unplug the player.
- Install disk builder, leaving the empeg OFF until the uploader says that it is trying to find the empeg. Once that happens, plug the empeg in.
- Upload the disk builder software
- As soon as the upgrade completes, and the empeg is rebooting, pull the plug on the empeg
- Set up to capture a hyperterminal session
- Plug the empeg in, capturing the session
- Hit "enter" if you are asked to on console
- When you see the disk stress test running, stop the capture and post it here. Leave the stress test running.
The intent of this is to a) load the builder software while b) capturing the output of the build to make sure it worked.
One the stress test has been running for a while, and if the output from the hyperterm session and build looks good, you will then load the developer software version of the player using the first three steps above.
_________________________
Paul Grzelak
200GB with 48MB RAM, Illuminated Buttons and Digital Outputs
|
|
Top
|
|
|
|
|
#284139 - 07/07/2006 17:32
Re: Problem with new Disk installation
[Re: pgrzelak]
|
new poster
Registered: 25/07/2003
Posts: 48
Loc: Reading UK
|
Riiight. The reboot (I.E: display relighting with the boot logos) was not happening before. Not realising that, I whipped the power just as the Kernel began flashing and recorded the If there is anyone present who wants to upgrade the flash, let them speak now,
or forever hold their peace... message. I went through the upload again expecting to whip the power/click cancel just as the disk pump search began. This time the player lit up and found the disks all on its own, it is now pumping happily. I HTH the next person. Speaking too soon; thanks all is fine now 
_________________________
Empeg V2 60GB running v3 (alpha 11) and the autoupdated hijack from jemplode.
|
|
Top
|
|
|
|
|
#284140 - 07/07/2006 19:46
Re: Problem with new Disk installation
[Re: estocks]
|
new poster
Registered: 25/07/2003
Posts: 48
Loc: Reading UK
|
Gah! Spoke too soon.
Emplode would not read the music database afer installing Developer V3.
The player does not reboot after the kernel is flashed with the Disk Builder.
Help!
Edited by estocks (07/07/2006 19:47)
|
|
Top
|
|
|
|
|
#284141 - 07/07/2006 20:27
Re: Problem with new Disk installation
[Re: estocks]
|
carpal tunnel
Registered: 20/12/1999
Posts: 31597
Loc: Seattle, WA
|
Quote:
Developer V3.
If you're having problems at all, don't use V3. V3 is alpha software and has bugs. Use V2 final.
|
|
Top
|
|
|
|
|
#284142 - 07/07/2006 20:49
Re: Problem with new Disk installation
[Re: tfabris]
|
new poster
Registered: 25/07/2003
Posts: 48
Loc: Reading UK
|
Overwrote v3 with V2.01 final but Emplode doesn't read the Media database. The player then reboots.
@pgrzelak Because the player does not reboot after the Disk Builder kernel is loaded I cannot get a log.
It remains in the download state after the DC is removed and reinserted also.
Edited by estocks (07/07/2006 21:54)
|
|
Top
|
|
|
|
|
#284143 - 07/07/2006 22:58
Re: Problem with new Disk installation
[Re: estocks]
|
carpal tunnel
Registered: 20/12/1999
Posts: 31597
Loc: Seattle, WA
|
It's possible that installing version 3 messed up the databases, since it uses a different database format. Also, make sure that your emplode is version 2.0 exactly, not any other version. If that doesn't work, then see if rebuilding the databases manually fixes the problem.
|
|
Top
|
|
|
|
|
#284144 - 08/07/2006 00:05
Re: Problem with new Disk installation
[Re: estocks]
|
carpal tunnel
Registered: 29/08/2000
Posts: 14493
Loc: Canada
|
Quote:
The player does not reboot after the kernel is flashed with the Disk Builder.
Help!
That's normal. After the disk builder has finished the "building" parts, it just loops doing tests until you shut it up. Install the normal car2-upgrade image now.
-ml
|
|
Top
|
|
|
|
|
#284145 - 08/07/2006 07:30
Re: Problem with new Disk installation
[Re: tfabris]
|
new poster
Registered: 25/07/2003
Posts: 48
Loc: Reading UK
|
@tfabris this is my log with V2.01 installed. I guess something is wrong with the file system Quote:
empeg:/empeg/bin# rwm
mount: /drive0 not mounted already, or bad option
empeg:/empeg/bin# rm/drive0/var/database
bash: rm/drive0/var/database: No such file or directory
empeg:/empeg/bin# rm/drive0/var/database3
bash: rm/drive0/var/database3: No such file or directory
empeg:/empeg/bin# rm/drive0/var/tags
bash: rm/drive0/var/tags: No such file or directory
empeg:/empeg/bin# dd if=/dev/zero of=/dev/hdc bs=1024 count=1024
dd: /dev/hdc: Device not configured
empeg:/empeg/bin# fdisk -l /dev/hdc
empeg:/empeg/bin# fdisk -l /dev/hdc
empeg:/empeg/bin#
@mlord the disk doesn't reboot to pump the disks, and does not get to the testing stage.
_________________________
Empeg V2 60GB running v3 (alpha 11) and the autoupdated hijack from jemplode.
|
|
Top
|
|
|
|
|
#284146 - 08/07/2006 08:04
Re: Problem with new Disk installation
[Re: estocks]
|
carpal tunnel
Registered: 18/01/2000
Posts: 5683
Loc: London, UK
|
Quote:
@tfabris this is my log with V2.01 installed.
Copy-and-paste the commands from the FAQ. You're missing a whole heap of spaces in those commands.
But, also, your second disk doesn't seem to be being recognised (/dev/hdc: Device not configured), so you should attach a complete boot log. Instructions for that are in the FAQ, too.
_________________________
-- roger
|
|
Top
|
|
|
|
|
#284147 - 08/07/2006 10:09
Re: Problem with new Disk installation
[Re: Roger]
|
new poster
Registered: 25/07/2003
Posts: 48
Loc: Reading UK
|
@Roger, This is my boot log (I have one brand new 60GB WD disk in IDE0) Quote:
empeg-car bootstrap v1.02 20001106 ([email protected])
If there is anyone present who wants to upgrade the flash, let them speak now,
or forever hold their peace...it seems not. Let fly the Penguins of Linux!
e000 v1.04
Copying kernel...
Calling linux kernel...
Uncompressing Linux..................................... done, booting the kernel.
Linux version 2.2.14-rmk5-np17-empeg55 (peter@tatu) (gcc version 2.95.3 20010315 (release)) #20 Tue Jul 6 15:36:06 BST 2004
Processor: Intel StrongARM-1100 revision 11
Checking for extra DRAM:
c1000000: wrote ffffffff, read 9afffff0
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
empeg-car player (hardware revision 9, serial number 10101510)
Command line: mem=16m
Calibrating delay loop... 207.67 BogoMIPS
Memory: 15024k/16M available (964k code, 20k reserved, 372k data, 4k init)
Dentry hash table entries: 2048 (order 2, 16k)
Buffer cache hash table entries: 16384 (order 4, 64k)
Page cache hash table entries: 4096 (order 2, 16k)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
TCP: Hash tables configured (ehash 16384 bhash 16384)
IrDA (tm) Protocols for Linux-2.2 (Dag Brattli)
Linux-IrDA: IrCOMM protocol ( revision:Tue May 18 03:11:39 1999 )
ircomm_tty: virtual tty driver for IrCOMM ( revision:Wed May 26 00:49:11 1999 )
Starting kswapd v 1.5
SA1100 serial driver version 4.27 with no serial options enabled
ttyS00 at 0xf8010000 (irq = 15) is a SA1100 UART
ttyS01 at 0xf8050000 (irq = 17) is a SA1100 UART
ttyS02 at 0xf8030000 (irq = 16) is a SA1100 UART
Signature is 67706d65 'empg'
Scheduling custom logo.
empeg display initialised.
empeg dsp audio initialised
empeg dsp mixer initialised
empeg dsp initialised
empeg audio-in initialised, CS4231A revision a0
empeg remote control/panel button initialised.
empeg usb initialised, PDIUSBD12 id 1012
empeg state support initialised 0089/88c1 (save to d0005e80).
empeg RDS driver initialised
empeg power-pic driver initialised (first boot)
RAM disk driver initialized: 16 RAM disks of 4096K size
empeg single channel IDE
Probing primary interface...
hda: WDC WD600VE-75HDT1, ATA DISK drive
hda: WDC WD600VE-75HDT1, ATA DISK drive
hda: WDC WD600VE-75HDT1, ATA DISK drive
hda: WDC WD600VE-75HDT1, ATA DISK drive
hda: WDC WD600VE-75HDT1, ATA DISK drive
hda: WDC WD600VE-75HDT1, ATA DISK drive
ide0 at 0x000-0x007,0x038 on irq 6
hda: WDC WD600VE-75HDT1, 57231MB w/8192kB Cache, CHS=7296/255/63
empeg-flash driver initialized
smc chip id/revision 0x3349
smc9194.c:v0.12 03/06/96 by Erik Stahlman ([email protected])
SMC9194: SMC91C94(r:9) at 0x4008000 IRQ:7 INTF:TP MEM:6144b MAC 00:02:d7:22:05:e6
Partition check:
hda: hda1 < hda5 hda6 > hda2 hda3 hda4
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 320 blocks [1 disk] into ram disk... |/-\|/-\|/-\|/-\|/-\done.
EXT2-fs warning: checktime reached, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
empeg-pump v0.03 (19980601)
Press Ctrl-A to enter pump... VFS: Mounted root (ext2 filesystem) readonly.
change_root: old root has d_count=1
Trying to unmount old root ... okay
Freeing unused kernel memory: 4k initempeg init 0.8
I see this is a developer image!
Mounting proc
Mounting first music partition
Tried to mount /dev/hda4 as reiserfs but got error 19
VFS: Can't find an ext2 filesystem on dev ide0(3,4).
Tried to mount /dev/hda4 as ext2 but got error 22
Error mounting partitions (possibly already mounted)
Remounting first music partition read-only
No primary hard disk
Remounting second music partition read-only
No secondary hard disk
Press 'q' now to go into development mode. You Have Zero Seconds To ComplůStarting player
player.cpp : 385:empeg-car 2.01 2004/07/06.
! tags.cpp : 61:Failed to open tags (0xc0041002).
Prolux 4 empeg car - 2.1434 Jul 5 2004
Vcb: 0x4086d000
I am fairly sure there is a problem with the Disk Builder Image section. It does not work like the FAQ says it will. It does not reboot the player before pumping the disk, like a player image does, and there is no way for me to get a Disk Builder log becasue of that.
Edited by estocks (08/07/2006 10:46)
_________________________
Empeg V2 60GB running v3 (alpha 11) and the autoupdated hijack from jemplode.
|
|
Top
|
|
|
|
|
#284148 - 08/07/2006 11:22
Re: Problem with new Disk installation
[Re: estocks]
|
carpal tunnel
Registered: 29/08/2000
Posts: 14493
Loc: Canada
|
That particular boot log is from a normal developer image, NOT from a builder image.
What are you trying to do, and what are you trying to show here?
Thanks
|
|
Top
|
|
|
|
|
#284149 - 08/07/2006 12:10
Re: Problem with new Disk installation
[Re: estocks]
|
carpal tunnel
Registered: 18/01/2000
Posts: 5683
Loc: London, UK
|
Quote:
VFS: Can't find an ext2 filesystem on dev ide0(3,4).
Tried to mount /dev/hda4 as ext2 but got error 22
Error mounting partitions (possibly already mounted)
The disk builder didn't successfully format your music partition. This is a fairly common occurrence with larger disks. You should first retry the disk builder, which sometimes succeeds.
If that doesn't work, you'll have to format the partition yourself. Install a developer release, get to a shell prompt, and then follow the instructions on this page.
_________________________
-- roger
|
|
Top
|
|
|
|
|
#284150 - 08/07/2006 12:35
Re: Problem with new Disk installation
[Re: Roger]
|
new poster
Registered: 25/07/2003
Posts: 48
Loc: Reading UK
|
@mlord I have a single 60GB brand new disk I want to partition, format, and add a player image to. I cannot complete the Disk Builder image as it does not reboot the player at the Pump Hard Disk stage of the flashing. Unfortunatly a log is not possible as the player remains in the download state. It flashed once I thinght and so added a player image. It was V3, and Emplode V2.10 would not recognise the player database. I put on V2.01 Final and Emplode 2.0 and again it would not read the player database. @roger these are my logs from attempting a partiton followed by a format followed by a partition. They do not seem to be responding as the FAQ suggests. Quote:
empeg:/empeg/bin# dd if=/dev/zero of=/dev/hdc bs=1024 count=1024
dd: /dev/hdc: Device not configured
Quote:
empeg:/empeg/bin# mke2fs -m 0 -s 1 -i 131072 /dev/hdc4
mke2fs 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
ext2fs_check_if_mount: No such file or directory while determining whether /dev/
hdc4 is mounted.
mke2fs: Device not configured while trying to determine filesystem size
Quote:
empeg:/empeg/bin# dd if=/dev/zero of=/dev/hdc bs=1024 count=1024
dd: /dev/hdc: Device not configured
empeg:/empeg/bin#
_________________________
Empeg V2 60GB running v3 (alpha 11) and the autoupdated hijack from jemplode.
|
|
Top
|
|
|
|
|
#284151 - 08/07/2006 12:54
Re: Problem with new Disk installation
[Re: estocks]
|
carpal tunnel
Registered: 18/01/2000
Posts: 5683
Loc: London, UK
|
Quote:
I cannot complete the Disk Builder image as it does not reboot the player at the Pump Hard Disk stage of the flashing. Unfortunatly a log is not possible as the player remains in the download state.
That's because you're supposed to do it by having the player unplugged initially, and then by reapplying the power.
Also, my instructions assume that you're formatting a second disk, so if you want to format a single disk manually, you'll need to replace every instance of /dev/hdc with /dev/hda in those instructions.
_________________________
-- roger
|
|
Top
|
|
|
|
|
#284152 - 08/07/2006 13:49
Re: Problem with new Disk installation
[Re: Roger]
|
new poster
Registered: 25/07/2003
Posts: 48
Loc: Reading UK
|
Quote:
Quote:
I cannot complete the Disk Builder image as it does not reboot the player at the Pump Hard Disk stage of the flashing. Unfortunatly a log is not possible as the player remains in the download state.
That's because you're supposed to do it by having the player unplugged initially, and then by reapplying the power.
I do start with the palyer unplugged and insert the power when instructed I am certain.Quote:
Also, my instructions assume that you're formatting a second disk, so if you want to format a single disk manually, you'll need to replace every instance of /dev/hdc with /dev/hda in those instructions.
Here are the logs I captured.Quote:
Starting bash.
empeg:/empeg/bin# dd if=/dev/zero of=/dev/hda bs=1024 count=1024
1024+0 records in
1024+0 records out
empeg:/empeg/bin# fdisk -l /dev/hda
Disk /dev/hda: 255 heads, 63 sectors, 7296 cylinders
Units = cylinders of 16065 * 512 bytes
Disk /dev/hda doesn't contain a valid partition table
empeg:/empeg/bin# fdisk /dev/hda
Device contains neither a valid DOS partition table, nor Sun or SGI disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that, of course, the previous
content won't be recoverable.
The number of cylinders for this disk is set to 7296.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): n
Command action
e extended
p primary partition (1-4)
e
Partition number (1-4): 1
First cylinder (1-7296, default 1): 1
Last cylinder or +size or +sizeM or +sizeK (1-7296, default 7296): +32M
Command (m for help): n
Command action
l logical (5 or over)
p primary partition (1-4)
p
Partition number (1-4): 2
First cylinder (6-7296, default 6):
Using default value 6
Last cylinder or +size or +sizeM or +sizeK (6-7296, default 7296): +32M
Command (m for help): n
Command action
l logical (5 or over)
p primary partition (1-4)
p
Partition number (1-4): 3
First cylinder (11-7296, default 11):
Using default value 11
Last cylinder or +size or +sizeM or +sizeK (11-7296, default 7296): +16M
Command (m for help): t
Partition number (1-5): 3
Hex code (type L to list codes): 10
Changed system type of partition 3 to 10 (OPUS)
Command (m for help): n
Command action
l logical (5 or over)
p primary partition (1-4)
p
Partition number (1-4): 4
First cylinder (14-7296, default 14):
Using default value 14
Last cylinder or +size or +sizeM or +sizeK (14-7296, default 7296):
Using default value 7296
Command (m for help): n
First cylinder (1-5, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-5, default 5): +16M
Command (m for help): n
First cylinder (4-5, default 4):
Using default value 4
Last cylinder or +size or +sizeM or +sizeK (4-5, default 5):
Using default value 5
Command (m for help): t
Partition number (1-6): 6
Hex code (type L to list codes): 82
Changed system type of partition 6 to 82 (Linux swap)
Command (m for help): p
Disk /dev/hda: 255 heads, 63 sectors, 7296 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 5 40131 5 Extended
/dev/hda2 6 10 40162+ 83 Linux
/dev/hda3 11 13 24097+ 10 OPUS
/dev/hda4 14 7296 58500697+ 83 Linux
/dev/hda5 1 3 24034+ 83 Linux
/dev/hda6 4 5 16033+ 82 Linux swap
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Re-read table failed with error 16: Device or resource busy.
Reboot your system to ensure the partition table is updated.
WARNING: If you have created or modified any DOS 6.x
partitions, please see the fdisk manual page for additional
information.
Syncing disks.
empeg:/empeg/bin#
Then a reboot.Quote:
empeg-car bootstrap v1.02 20001106 ([email protected])
If there is anyone present who wants to upgrade the flash, let them speak now,
or forever hold their peace...it seems not. Let fly the Penguins of Linux!
e000 v1.04
Copying kernel...
Calling linux kernel...
Uncompressing Linux..................................... done, booting the kerne
l.
Linux version 2.2.14-rmk5-np17-empeg55 (peter@tatu) (gcc version 2.95.3 20010315
(release)) #20 Tue Jul 6 15:36:06 BST 2004
Processor: Intel StrongARM-1100 revision 11
Checking for extra DRAM:
c1000000: wrote ffffffff, read 9afffff0
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
empeg-car player (hardware revision 9, serial number 10101510)
Command line: mem=16m
Calibrating delay loop... 207.67 BogoMIPS
Memory: 15024k/16M available (964k code, 20k reserved, 372k data, 4k init)
Dentry hash table entries: 2048 (order 2, 16k)
Buffer cache hash table entries: 16384 (order 4, 64k)
Page cache hash table entries: 4096 (order 2, 16k)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
TCP: Hash tables configured (ehash 16384 bhash 16384)
IrDA (tm) Protocols for Linux-2.2 (Dag Brattli)
Linux-IrDA: IrCOMM protocol ( revision:Tue May 18 03:11:39 1999 )
ircomm_tty: virtual tty driver for IrCOMM ( revision:Wed May 26 00:49:11 1999 )
Starting kswapd v 1.5
SA1100 serial driver version 4.27 with no serial options enabled
ttyS00 at 0xf8010000 (irq = 15) is a SA1100 UART
ttyS01 at 0xf8050000 (irq = 17) is a SA1100 UART
ttyS02 at 0xf8030000 (irq = 16) is a SA1100 UART
Signature is 67706d65 'empg'
Scheduling custom logo.
empeg display initialised.
empeg dsp audio initialised
empeg dsp mixer initialised
empeg dsp initialised
empeg audio-in initialised, CS4231A revision a0
empeg remote control/panel button initialised.
empeg usb initialised, PDIUSBD12 id 1012
empeg state support initialised 0089/88c1 (save to d0004300).
empeg RDS driver initialised
empeg power-pic driver initialised (first boot)
RAM disk driver initialized: 16 RAM disks of 4096K size
empeg single channel IDE
Probing primary interface...
hda: WDC WD600VE-75HDT1, ATA DISK drive
hda: WDC WD600VE-75HDT1, ATA DISK drive
hda: WDC WD600VE-75HDT1, ATA DISK drive
hda: WDC WD600VE-75HDT1, ATA DISK drive
hda: WDC WD600VE-75HDT1, ATA DISK drive
hda: WDC WD600VE-75HDT1, ATA DISK drive
ide0 at 0x000-0x007,0x038 on irq 6
hda: WDC WD600VE-75HDT1, 57231MB w/8192kB Cache, CHS=7296/255/63
empeg-flash driver initialized
smc chip id/revision 0x3349
smc9194.c:v0.12 03/06/96 by Erik Stahlman ([email protected])
SMC9194: SMC91C94(r:9) at 0x4008000 IRQ:7 INTF:TP MEM:6144b MAC 00:02:d7:22:05:e
6
Partition check:
hda: hda1 < hda5 hda6 > hda2 hda3 hda4
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 320 blocks [1 disk] into ram disk... done.
EXT2-fs warning: checktime reached, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
empeg-pump v0.03 (19980601)
Press Ctrl-A to enter pump...Kernel panic: VFS: Unable to mount root fs on 03:05
Display says No hard disk found contact support And I cant get to the command shell to format the disk.
_________________________
Empeg V2 60GB running v3 (alpha 11) and the autoupdated hijack from jemplode.
|
|
Top
|
|
|
|
|
#284153 - 08/07/2006 14:36
Re: Problem with new Disk installation
[Re: estocks]
|
carpal tunnel
Registered: 29/08/2000
Posts: 14493
Loc: Canada
|
Well, since the builder is already giving you troubles, could you please try this custom builder I have prepared for big disks, and see what it does (or doesn't do). Thanks.
|
|
Top
|
|
|
|
|
#284154 - 08/07/2006 15:08
Re: Problem with new Disk installation
[Re: mlord]
|
new poster
Registered: 25/07/2003
Posts: 48
Loc: Reading UK
|
Quote:
Well, since the builder is already giving you troubles, could you please
try this custom builder I have prepared for big disks, and see what it does (or doesn't do).
Thanks.
The Disk Builder downloaded, rebooted and began pumping the disk first time thanks. It rebooted and ran the builder image for the first time.
Making /dev/hda4 filesystem
Mounting...
** Some workds and a table flys by **
Spinning Down
Spinning Up
**Screen goes blank. Disk whirs on and off**
The Player V2.01 image is in and the database is being read with Emplode. Thanks guys.
_________________________
Empeg V2 60GB running v3 (alpha 11) and the autoupdated hijack from jemplode.
|
|
Top
|
|
|
|
|
#284155 - 08/07/2006 15:59
Re: Problem with new Disk installation
[Re: estocks]
|
carpal tunnel
Registered: 29/08/2000
Posts: 14493
Loc: Canada
|
Super. Happy Trails, then!
|
|
Top
|
|
|
|
|
#284156 - 09/07/2006 22:19
Re: Problem with new Disk installation
[Re: estocks]
|
carpal tunnel
Registered: 20/12/1999
Posts: 31597
Loc: Seattle, WA
|
Quote:
I cannot complete the Disk Builder image as it does not reboot the player at the Pump Hard Disk stage of the flashing.
Wow.
I'm glad Mark's custom builder image worked for you, but I'm stymied as to why the factory builder image didn't behave as expected, unless you somehow got a corrupted file.
|
|
Top
|
|
|
|
|
#284157 - 23/07/2006 21:29
Re: Problem with new Disk installation
[Re: tfabris]
|
new poster
Registered: 30/07/2005
Posts: 2
|
I encountered the same problem, and this builder fixed the issue. The drive i'm using is a Fujitsu MHV2040AH (40GB 5400RPM). Thank you all for your help, the FAQ and this board have made everything go smoothly for me.
|
|
Top
|
|
|
|
|
#284158 - 26/07/2006 15:39
Re: Problem with new Disk installation
[Re: Gize]
|
new poster
Registered: 03/01/2001
Posts: 18
|
Same here, though with an IBM disk. Did the Disk Builder image get damaged during the restore of the site, perhaps?
|
|
Top
|
|
|
|
|
#284159 - 26/07/2006 20:35
Re: Problem with new Disk installation
[Re: gbsallery]
|
carpal tunnel
Registered: 29/08/2000
Posts: 14493
Loc: Canada
|
Quote:
Did the Disk Builder image get damaged during the restore of the site, perhaps?
No, the copy on the site is just fine. It just doesn't always work reliably with drives >= 40GB or so.
Cheers
|
|
Top
|
|
|
|
|
#284160 - 13/10/2006 15:12
Re: Problem with new Disk installation
[Re: mlord]
|
stranger
Registered: 11/05/2002
Posts: 84
Loc: Cincinnati, OH
|
I'm having the same problem with the stock builder. Mark's custom builder works fine, but I only have 20GB and 30GB drives. Will using Mark's builder be a problem with these smaller drives? Has anyone actually gotten the stock builder to work lately?
Jeff
Edited by JeffreyB (13/10/2006 15:34)
|
|
Top
|
|
|
|
|
#284161 - 13/10/2006 15:37
Re: Problem with new Disk installation
[Re: JeffreyB]
|
stranger
Registered: 11/05/2002
Posts: 84
Loc: Cincinnati, OH
|
...
Edited by JeffreyB (13/10/2006 16:00)
|
|
Top
|
|
|
|
|
#284162 - 13/10/2006 17:01
Re: Problem with new Disk installation
[Re: JeffreyB]
|
carpal tunnel
Registered: 20/12/1999
Posts: 31597
Loc: Seattle, WA
|
Mark's builder should work fine, but I'm more worried about why you're the third person to report a problem with the stock builder.
Does the empeg support web site have a corrupted file by any chance?
|
|
Top
|
|
|
|
|
#284163 - 15/10/2006 03:13
Re: Problem with new Disk installation
[Re: tfabris]
|
enthusiast
Registered: 21/02/2006
Posts: 325
|
I was able to manually build a 120 GB drive and then I used the Big Disk Builder program for 5 other drives ( I have 3 Mk2s with 2 each 120 GB drives in them).
I have had success with both Hitachi and Toshiba drives. I have not mixed vendor drives in a Rio.
The builder works very well, good work.
Thanks
_________________________
In SI, a little termination and attention to layout goes a long way. In EMC, without SI, you'll spend 80% of the effort on the last 3dB.
|
|
Top
|
|
|
|
|
#284164 - 15/10/2006 12:44
Re: Problem with new Disk installation
[Re: Ross Wellington]
|
carpal tunnel
Registered: 29/08/2000
Posts: 14493
Loc: Canada
|
Quote:
I was able to manually build a 120 GB drive and then I used the Big Disk Builder program for 5 other drives ( I have 3 Mk2s with 2 each 120 GB drives in them).
..
The builder works very well, good work.
Excellent. I guess it was worth the effort. Some day I might even need it myself, I suppose!
Cheers
|
|
Top
|
|
|
|
|
#284165 - 24/10/2006 12:05
CAUTION for 160GB (and larger) drives
[Re: mlord]
|
carpal tunnel
Registered: 29/08/2000
Posts: 14493
Loc: Canada
|
Just a reminder, really. It now seems commonplace for many of us to be installing 80GB and 120GB drives into the Empeg/Rio Car players. Which means it will soon be more common to hear of 160GB (or larger) drives being used. There is a dangerous pitfall with these drives: your data WILL be corrupted if you ever install a stock player kernel into a system with a 160GB (or larger) drive installed.Thus, the usual sequence for many people here: - install the new big drive
- format it all using the big builder image: okay
- install the v2.01 player image from Windoze: instant corruption.
Only the Hijack kernels should ever be used with drives that large. Cheers
|
|
Top
|
|
|
|
|
#284166 - 24/10/2006 12:50
Re: CAUTION for 160GB (and larger) drives
[Re: mlord]
|
carpal tunnel
Registered: 15/08/2000
Posts: 4859
Loc: New Jersey, USA
|
Good tip! I can guarantee that would have been the upgrade path I would have eventually taken! 
_________________________
Paul Grzelak
200GB with 48MB RAM, Illuminated Buttons and Digital Outputs
|
|
Top
|
|
|
|
|
#284167 - 24/10/2006 13:03
Re: CAUTION for 160GB (and larger) drives
[Re: pgrzelak]
|
old hand
Registered: 07/01/2005
Posts: 893
Loc: Sector ZZ9pZa
|
Oh yes, me too. Thanks Mark.
|
|
Top
|
|
|
|
|
#284168 - 24/10/2006 13:33
Re: CAUTION for 160GB (and larger) drives
[Re: mlord]
|
carpal tunnel
Registered: 29/08/2000
Posts: 14493
Loc: Canada
|
Quote:
- install the v2.01 player image from Windoze: instant corruption.
Only the Hijack kernels should ever be used with drives that large.
Of course, one might then ask, So how *do* I install the player software onto such a drive?
Simple. Use one of these installers instead of the stock one:
Totally untested, of course, just like the original builder_bigdisk.upgrade was. 
Cheers
Edited by mlord (24/10/2006 15:08)
|
|
Top
|
|
|
|
|
#284169 - 24/10/2006 13:36
Re: CAUTION for 160GB (and larger) drives
[Re: mlord]
|
carpal tunnel
Registered: 29/08/2000
Posts: 14493
Loc: Canada
|
Note -- original post (above) edited: I changed the names of the downloads.
-ml
|
|
Top
|
|
|
|
|
#284170 - 24/10/2006 13:44
Re: CAUTION for 160GB (and larger) drives
[Re: mlord]
|
carpal tunnel
Registered: 30/10/2000
Posts: 4931
Loc: New Jersey, USA
|
Quote:
Use one of these installers instead of the stock one:
http://rtr.ca/car2_v2.01_hijack.upgrade
http://rtr.ca/car2_v3a11_hijack.upgrade
Not to look a gift horse in the mouth, but is it possible to make one of those handy packages for 2 beta 13? Many of us use it as it's the most stable v2 release to support tuner seeking. Thanks!
_________________________
-Rob Riccardelli
80GB 16MB MK2 090000736
|
|
Top
|
|
|
|
|
#284171 - 24/10/2006 15:06
Re: CAUTION for 160GB (and larger) drives
[Re: robricc]
|
carpal tunnel
Registered: 29/08/2000
Posts: 14493
Loc: Canada
|
Quote:
Not to look a gift horse in the mouth, but is it possible to make one of those handy packages for 2 beta 13? Many of us use it as it's the most stable v2 release to support tuner seeking. Thanks!
Done. Link added to original post above.
Cheers
|
|
Top
|
|
|
|
|
#284172 - 24/10/2006 15:35
Re: CAUTION for 160GB (and larger) drives
[Re: mlord]
|
carpal tunnel
Registered: 30/10/2000
Posts: 4931
Loc: New Jersey, USA
|
Awesome 
_________________________
-Rob Riccardelli
80GB 16MB MK2 090000736
|
|
Top
|
|
|
|
|
#284174 - 24/10/2006 18:29
Re: CAUTION for 160GB (and larger) drives
[Re: robricc]
|
enthusiast
Registered: 21/02/2006
Posts: 325
|
Once again this demonstrates the value of this forum.
The RioCar is a really cool product, other manufacturers are now seeing the vision. WAY AHEAD OF ITS TIME. Bigger drives will lengthen its life and since it is not a static product (firmware upgradable, not throw-away), it has a good future ahead of it for those who can get them. Thanks to those who provide us that upgrade path and provide a great resource for the newbies too.
I too, would have made the same mistake with 160 GB drives, now, I won't. But I would have spent alot of frustrating hours trying to figure it out and could have damaged one of my Rios.
Thanks,
Ross
|
|
Top
|
|
|
|
|
#284175 - 24/10/2006 19:19
Re: CAUTION for 160GB (and larger) drives
[Re: mlord]
|
carpal tunnel
Registered: 20/12/1999
Posts: 31597
Loc: Seattle, WA
|
Drive Upgrade Guide modified with this new information. Thanks.
|
|
Top
|
|
|
|
|
#284176 - 25/10/2006 06:06
Re: CAUTION for 160GB (and larger) drives
[Re: mlord]
|
pooh-bah
Registered: 09/08/2000
Posts: 2091
Loc: Edinburgh, Scotland
|
Thanks Mark - once again you make life easier for us.
Cheers
_________________________
Rory
MkIIa, blue lit buttons, memory upgrade, 1Tb in Subaru Forester STi
MkII, 240Gb in Mark Lord dock
MkII, 80Gb SSD in dock
|
|
Top
|
|
|
|
|
#284177 - 27/10/2006 00:41
Re: CAUTION for 160GB (and larger) drives
[Re: mlord]
|
carpal tunnel
Registered: 29/08/2000
Posts: 14493
Loc: Canada
|
Quote:
Quote:
- install the v2.01 player image from Windoze: instant corruption.
Only the Hijack kernels should ever be used with drives that large.
Of course, one might then ask, So how *do* I install the player software onto such a drive?
Simple. Use one of these installers instead of the stock one:
Totally untested, of course, just like the original builder_bigdisk.upgrade was.
Cheers
ARGHH!! Okay, at least the v3a11 image (above) actually did NOT have a Hijack kernel inside of it (I just tried to use it here). I'm fixing that right now, and have put three fresh replacement images (the .upgrade files linked to above) onto my server now.
I *think* these are okay, but still have to wait for the test to complete to verify that Hijack is indeed integrated into them.
More in a few minutes..
|
|
Top
|
|
|
|
|
#284178 - 27/10/2006 00:55
Re: CAUTION for 160GB (and larger) drives
[Re: mlord]
|
carpal tunnel
Registered: 29/08/2000
Posts: 14493
Loc: Canada
|
Quote:
Quote:
Quote:
- install the v2.01 player image from Windoze: instant corruption.
Only the Hijack kernels should ever be used with drives that large.
Of course, one might then ask, So how *do* I install the player software onto such a drive?
Simple. Use one of these installers instead of the stock one:
Totally untested, of course, just like the original builder_bigdisk.upgrade was.
Cheers
ARGHH!! Okay, at least the v3a11 image (above) actually did NOT have a Hijack kernel inside of it (I just tried to use it here). I'm fixing that right now, and have put three fresh replacement images (the .upgrade files linked to above) onto my server now.
I *think* these are okay, but still have to wait for the test to complete to verify that Hijack is indeed integrated into them.
More in a few minutes..
[EDIT]Mmm.. LBA48 support may be buggy in Hijack.. working on it now..[/EDIT]
Cheers
Edited by mlord (27/10/2006 01:58)
|
|
Top
|
|
|
|
|
#284179 - 27/10/2006 03:32
Re: CAUTION for 160GB (and larger) drives
[Re: mlord]
|
carpal tunnel
Registered: 29/08/2000
Posts: 14493
Loc: Canada
|
See the new thread in General: Hijack v464
|
|
Top
|
|
|
|
|
#284180 - 02/11/2006 03:10
Re: CAUTION for 160GB (and larger) drives
[Re: mlord]
|
enthusiast
Registered: 21/02/2006
Posts: 325
|
Hi,
Does the new V464 Flash Firmware include the function to automatically corrupt (fill the boot partition with junk), so that a disk with a previous format on it will be forced to fully partition and format the disk?
I noticed that a drive with a previous partition and format indicates that " the drive appears to have been built". When the drive is "scribbled" on like in the FAQ, it seems better behaved. It also should free up the complete partition for a new database.
Did I miss something?
Thanks,
Ross
|
|
Top
|
|
|
|
|
#284181 - 02/11/2006 11:48
Re: CAUTION for 160GB (and larger) drives
[Re: mlord]
|
old hand
Registered: 17/01/2003
Posts: 998
|
Quote:
Quote:
- install the v2.01 player image from Windoze: instant corruption.
Only the Hijack kernels should ever be used with drives that large.
Of course, one might then ask, So how *do* I install the player software onto such a drive?
Simple. Use one of these installers instead of the stock one:
Totally untested, of course, just like the original builder_bigdisk.upgrade was.
Cheers
All these links seem to be broken, at least for me.
Never mind, Found them here.....
http://rtr.ca/bigdisk/
Edited by Redrum (02/11/2006 11:51)
|
|
Top
|
|
|
|
|
#284182 - 02/11/2006 13:30
Re: CAUTION for 160GB (and larger) drives
[Re: Ross Wellington]
|
carpal tunnel
Registered: 29/08/2000
Posts: 14493
Loc: Canada
|
Quote:
Does the new V464 Flash Firmware include the function to automatically corrupt (fill the boot partition with junk), so that a disk with a previous format on it will be forced to fully partition and format the disk?
No. And if it did have that feature, I know of many people on this BBS who would eventually cry out "hey, it killed my good drive and I lost all of my tunes -- no backup, either!".
So, no.
|
|
Top
|
|
|
|
|
#284183 - 03/11/2006 16:13
Re: CAUTION for 160GB (and larger) drives
[Re: mlord]
|
enthusiast
Registered: 21/02/2006
Posts: 325
|
Yeah, that was a dumb question, wasn't it....
Sorry to waste your time.
Ross
|
|
Top
|
|
|
|
|
#284185 - 03/11/2006 18:30
Re: CAUTION for 160GB (and larger) drives
[Re: Ross Wellington]
|
carpal tunnel
Registered: 29/08/2000
Posts: 14493
Loc: Canada
|
Quote:
Yeah, that was a dumb question, wasn't it....
Actually, I think it was a good question. And if I were doing these builder thingies for myself, that's how I'd want it to work.
But I've never actually *used* these builder thingies -- I just fixed them for everyone else to use.
Cheers
|
|
Top
|
|
|
|
|
#284186 - 04/11/2006 02:18
Re: CAUTION for 160GB (and larger) drives
[Re: Redrum]
|
pooh-bah
Registered: 19/09/2002
Posts: 2494
Loc: East Coast, USA
|
Mark, you're the man! Images saved, for when I get 160gig drives in about 4 years or so. TRUE upgrade paths; rare in computers these days. Thanks.
_________________________
- FireFox31 110gig MKIIa (30+80), Eutronix lights, 32 meg stacked RAM, Filener orange gel lens, Greenlights Lit Buttons green set
|
|
Top
|
|
|
|
|
#284187 - 25/11/2006 19:12
Re: CAUTION for 160GB (and larger) drives
[Re: Redrum]
|
enthusiast
Registered: 20/11/2000
Posts: 279
Loc: Pacific Northwest
|
Hey Guys! Long time no chat. I've recently be amid a drive upgrade and found FAQ fix needed... It looks like this FAQ page needs a slight update. The link "Mark Lord's Special Disk Builder for large disks" points to an old location: Quote:
Special note for large drives: You might run into a problem if your disk drive is larger than about 40-60 gigabytes. The official empeg builder image hasn't been updated to support large disks. It sometimes runs out of memory when building the music partition. This will manifest itself as disk drive errors when the player boots or when you try to put music onto the player. If this happens, there are a few things you can try: You can use Mark Lord's Special Disk Builder for large disks. You can try to apply the builder image a second time (starting the procedure from the top). Sometimes this is enough. You can also partition and format the hard disk manually. If your disk is larger than 128 gigabytes, make sure to install the latest Hijack Kernel before partitioning and formatting manually. You will also need to re-install the Hijack Kernel after putting the developer upgrade onto the player.
Given the below:
Quote:
Quote:
Quote:
- install the v2.01 player image from Windoze: instant corruption.
Only the Hijack kernels should ever be used with drives that large.
Of course, one might then ask, So how *do* I install the player software onto such a drive?
Simple. Use one of these installers instead of the stock one:
Totally untested, of course, just like the original builder_bigdisk.upgrade was.
Cheers
All these links seem to be broken, at least for me.
Never mind, Found them here.....
http://rtr.ca/bigdisk/
|
|
Top
|
|
|
|
|
#284188 - 01/12/2006 15:54
Re: CAUTION for 160GB (and larger) drives
[Re: time]
|
enthusiast
Registered: 21/02/2006
Posts: 325
|
Hi,
I may have seen a related problem.
I have seen a problem (probably unrelated to V464) where I loaded 2 of my 3 Empegs and on one of them when resyncing it spends ALOT of time on Checking The Disk Integrity. I load approximately 200 GB of .WAV files on each Empeg. One has Hitachi drives another has Toshiba drives.
It probably spends an hour checking the media (got longer as I filled it up), completes the resync, and operates fine. I have re-partitioned & reformatted them and they seem to do the same thing.
The other Empeg (it has two Toshiba 120 GB drives in it), doesn't seem to have the problem.
Has anyone seen this problem, do I need to perform some kind of FSCK or something?
Maybe Hitachi drives just choke on my listening tastes (Classic Rock, Easy Listening), I don't know....
Thanks,
Ross
_________________________
In SI, a little termination and attention to layout goes a long way. In EMC, without SI, you'll spend 80% of the effort on the last 3dB.
|
|
Top
|
|
|
|
|
|
Previous Topic
Index