There really is not a lot you can do. You have filesystem corruption. If you do not have a backup you can try checking and replacing problematic cables or raid (NAS) boxes. If you have another SCO system, you can try to attach the hard drive to the other system then run
See also the badtrk command.
Gee, I have not thought about SCO for years... surprised myself with what I remembered.
Probably due to all the SCO nightmares we had.
For legacy systems like that you absolutely positively MUST have current backups. You also want to keep spare parts, as newer disk controllers, etc., may not work with the driver set. Try Ebay for spares.
I recall having to get some old hardware from Ebay... which finally triggered the Duh? response from management.
This User Gave Thanks to jim mcnamara For This Post:
Could somone please tell me what happened when I reboot my computer, it take too long to pass the part it said "starting sendmail"
I only changed the server name and when I reboot the server, all of the services are running except when it got to :
starting sendmail
it take toooo long to... (1 Reply)
Hi All,
1st HDD is loaded with Windows 2000 Professional and I have installed Red Hat ES 3.0 on second HDD(80GB). After linux installation failed to load windows and boot stucks with displaying only L How to fix this issue
Thanks in advance for your valuable answer.
Regards,
Bachegowda (1 Reply)
Hi,all:
I want to boot an IA unix box from network, I am sure I set the DHCP and boot server, but it still failed !
It says : Client MAC Address: 00 18 FE 28 91 82 .....-
PXE-E16: Valid PXE offer not received.
Load of Core LAN Gb A failed: Not Found
I use the nettl command to trace the UDP... (0 Replies)
Hello, have HP Visualize C3600 workstation. Issue is as follows:
When I attempt to boot, unit will not boot successfully and will halt at a menu, the same menu as when during a boot one hits any key within 10 seconds to discontinue. When I attempt to boot with Boot primary, both with IPL... (17 Replies)
I had logged into Server via ALOM and was placed into runlevel 5 other than 3 which is default.
I did a svcadm delete boot-archive, and was promptly placed in runlevel 3.
Now, I am unable to do a telnet or login into the server through any other service.
bash-3.00# svcs -a
svcs -a
STATE ... (3 Replies)
Machine: x86
OS : Dualboot Solaris and RHEL5 -Solaris 10 in first fdisk partition.
RHEL5 - /boot in partition2
/ in partition3
swap in 1st... (1 Reply)
Hi,
I have a laptop with two os running in it, Windows XP & RHEL5. Accidentally, we have deleted the windows entry in grub.conf file. Later we connected the hard disk of laptop to another system & deleted the linux partitions from the disk management tool of windows.
Now the issue is, the... (7 Replies)
Hi all
i have an issue
when i change auto-boot?=false and reboot it
again it is going to auto-boot?=true
can any one tell that
what should i do for auto-boot?=false for permanently
thank you in advance (11 Replies)
Hi all,
please i need your help urgently
I am faced to a serious boot disks issue on an Sun Fire E2900.
The system run with two disque in zpool .
The operating system is Solaris 10 (ZFS)
The first time the issue occured, i got the error below on the two disks:
Apr 7 08:04:33... (0 Replies)
In the server room at my new job, there is a V100 with a problem. When power is turned on, the machine goes to the lom prompt. Entering poweron yields an endless supply of this message with no way to break out of it.
**********************************************
PSTATE=0000000000000015... (3 Replies)
Discussion started by: chilinski
3 Replies
LEARN ABOUT NETBSD
ubt
UBT(4) BSD Kernel Interfaces Manual UBT(4)NAME
ubt -- USB Bluetooth driver
SYNOPSIS
ubt* at uhub? port ? configuration ? interface ?
DESCRIPTION
The ubt driver provides support for USB Bluetooth dongles to the Bluetooth protocol stack.
USB Bluetooth dongles provide two interfaces, both of which the ubt driver claims. The second interface is used for Isochronous data and
will have several alternate configurations regarding bandwidth consumption, which can be set using the hw.ubtN.config sysctl(8) variable.
The number of alternate configurations is indicated by the value in the hw.ubtN.alt_config variable, and the isoc frame size for the current
configuration is shown in the hw.ubtN.sco_rxsize and hw.ubtN.sco_txsize variables.
By default, configuration 0 is selected, which means that no bandwidth is used on the Isochronous interface and no SCO data can be sent.
Consult the Bluetooth USB specification at https://www.bluetooth.org/ for complete instructions on setting bandwidth consumption. The fol-
lowing extract may be useful as a general guidance though details may differ between manufacturers.
0 No active voice channels
1 One voice channel with 8-bit encoding
2 Two voice channels with 8-bit encoding, or one voice channel with 16-bit encoding.
3 Three voice channels with 8-bit encoding
4 Two voice channels with 16-bit encoding
5 Three voice channels with 16-bit encoding
SEE ALSO bluetooth(4), uhub(4), sysctl(8)HISTORY
This ubt device driver was originally a character device written by David Sainty and Lennart Augustsson. It was rewritten to support socket
based Bluetooth access for NetBSD 4.0 by Iain Hibbert.
CAVEATS
Isochronous data is seemingly not well supported over USB in the current system and to get SCO working, you may have to calculate the SCO
packet size that the stack will use. This is the sco_mtu value reported by the btconfig(8) command, and when combined with the SCO header (3
bytes) should fit exactly into an integer number of Isochronous data frames where the frame size is indicated by the 'hw.ubtN.sco_txsize'
sysctl variable.
For example: I want one voice channel (which is all that is supported, for now) so am using configuration #2, with a frame length of 17
bytes. This gives possible values of:
(17 * 1) - 3 = 14
(17 * 2) - 3 = 31
(17 * 3) - 3 = 48
(17 * 4) - 3 = 65
(17 * 5) - 3 = 82
etc.
btconfig(8) shows the maximum SCO payload as 64 bytes, so I am using the next smaller size of 48, to minimize the overhead of the 3 header
bytes.
The SCO packet size can be changed using the 'scomtu' option to btconfig(8).
The failure mode is that the USB Bluetooth dongle locks up though generally removal/reinsertion will clear the problem.
BUGS
The Isochronous configuration can only be changed when the device is not marked up.
BSD August 27, 2006 BSD