Posted by: smu
Problem after drive upgrade - 11/03/2003 16:08
Hi.
I recently upgraded my empeg's HD to a nice 60GB disc. However: While the player seems to run fine, I took it inside for a few uploads and sync is _SLOW_ to say the least. I expected the fs checks to be much slower than with the previous disc, but there seems to be an additional problem, which I noticed on the log when connected by serial during a sync:
This does not look normal to me, but what exactly might this mean? The sector on which the error occures is different on each occasion. But the pattern is always the same.
Any hint would be appreciated.
cu,
sven
I recently upgraded my empeg's HD to a nice 60GB disc. However: While the player seems to run fine, I took it inside for a few uploads and sync is _SLOW_ to say the least. I expected the fs checks to be much slower than with the previous disc, but there seems to be an additional problem, which I noticed on the log when connected by serial during a sync:
empeg:/empeg/bin# logout
Shell exit
Starting player
Using non-standard cache size 20 (adjustment 64)
player.cpp : 385:empeg-car 2.00-beta13 2002/07/24.
! tags.cpp : 61:Failed to open tags (0xc0041002).
Restored terminal settings
Remounting first music partition read-only
Remounting second music partition read-only
No secondary hard disk
Abnormal player termination
Player received SIGINT, user interruption
Switching to shell-player loop
Starting bash.
empeg:/empeg/bin# logout
Shell exit
Starting player
Using non-standard cache size 20 (adjustment 64)
player.cpp : 385:empeg-car 2.00-beta13 2002/07/24.
! tags.cpp : 61:Failed to open tags (0xc0041002).
Prolux 4 empeg car - 2.1434 Jul 24 2002
Vcb: 0x4014d000
Adding Swap: 24060k swap-space (priority -2)
e2fsck 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/hda4 is mounted.
hda: irq timeout: status=0xd0
ide0: reset: success
hda: irq timeout: status=0xd0
ide0: reset: success
hda: irq timeout: status=0xd0
end_request: I/O error, dev 03:04 (hda), sector 2883864
hda: status timeout: status=0xd0
hda: drive not ready for command
ide0: reset: success
hda: irq timeout: status=0xd0
ide0: reset: success
hda: irq timeout: status=0xd0
ide0: reset: success
hda: irq timeout: status=0xd0
ide0: reset: success
hda: irq timeout: status=0xd0
end_request: I/O error, dev 03:04 (hda), sector 6815816
hda: status timeout: status=0xd0
hda: drive not ready for command
ide0: reset: success
hda: irq timeout: status=0xd0
ide0: reset: success
hda: irq timeout: status=0xd0
end_request: I/O error, dev 03:04 (hda), sector 6815824
hda: status timeout: status=0xd0
hda: drive not ready for command
ide0: reset: success
hda: irq timeout: status=0xd0
ide0: reset: success
hda: irq timeout: status=0xd0
ide0: reset: success
hda: irq timeout: status=0xd0
ide0: reset: success
hda: irq timeout: status=0xd0
end_request: I/O error, dev 03:06 (hda), sector 8
hda: status timeout: status=0xd0
hda: drive not ready for command
ide0: reset: success
hda: irq timeout: status=0xd0
ide0: reset: success
hda: irq timeout: status=0xd0
end_request: I/O error, dev 03:06 (hda), sector 16
hda: status timeout: status=0xd0
hda: drive not ready for command
This does not look normal to me, but what exactly might this mean? The sector on which the error occures is different on each occasion. But the pattern is always the same.
Any hint would be appreciated.
cu,
sven