OpenBSD downgrades HDD transfer mode, I want to upgrade it WITHOUT BOOTING


 
Thread Tools Search this Thread
Operating Systems BSD OpenBSD downgrades HDD transfer mode, I want to upgrade it WITHOUT BOOTING
# 1  
Old 02-16-2009
OpenBSD downgrades HDD transfer mode, I want to upgrade it WITHOUT BOOTING

Hi,

I have a crappy hard disk and am trying to back up stuff from it onto my newer hopefully less crappy disk. There are dead sectors on the disk and some files can't be read (at all) so OpenBSD downgrades the transfer mode down until PIO mode 4. I noticed the transfer speed slowing down extremely, and I would guess it's due to these downgrades, which are done when reading certain blocks continuously produces errors. But there are files on the disk that ARE READABLE and I don't want to reboot every time I end up on a trashed area on the disk, since the rest is fine and can be read in Ultra-DMA mode 5.

I looked it up a bit, and found out that apparently you can change device flags - including the transfer modes - with the config/UKC (User Kernel Config) utility, but AFAIK that is for rewriting the kernel image without recompiling. When OpenBSD downgrades the DMA modes, it's obviously doing something else, and I just need to do the reverse operation. The point being: if it can be downgraded without booting, it can be changed, and therefore upgraded without booting.

Anyone know how to upgrade from PIO4 without a reboot?
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

How to set file transfer in binary mode in SFTP using Expect?

The below is my script. /usr/bin/expect<<EOD spawn /usr/bin/sftp -o Port=$PORT $USER@$HOST expect "sftp>" expect "password:" set timout 15 send "$password\r" expect "sftp>" send "lcd $remotedir\r" expect "sftp>" ... (1 Reply)
Discussion started by: Anilsaggu9
1 Replies

2. Red Hat

[Solved] Redhat system is not booting in GUI mode

Hi Guys Required help in Redhat 6.1. After installation of Redhat 6.1 in VMware system is not going in GUI mode. please to solve the issue... Thanks... (5 Replies)
Discussion started by: deviltech
5 Replies

3. AIX

IBM AIX Internal HDD vs SAN HDD and Oracle

Hi Folks, I am facing an issue with the performance. P4 with 1 processor and 16 GB RAM and SAN HDD = Oracle report takes 25 minutes P5 with 2 processors and 16 GB RAM internall HDD with LPAR = Oracle Report takes 1 hour 15 minutes ( please note I have assigned all the max processors and... (7 Replies)
Discussion started by: filosophizer
7 Replies

4. Solaris

System booting to maintenance mode

Hi Guys, I have a sunblade 1500. I booted the system and it booted to maintenance mode. How can I fix this? Thanks lots (8 Replies)
Discussion started by: cjashu
8 Replies

5. Red Hat

Fedora booting in text mode (screen messes up)

Hello everyone Had a problem booting Fedora. I installed it as a server without any desktop environment(kde, gnome) except for X. Problem is when i booting system after it loads kernel suddenly screen messes up with parts of fedora graphics(it's not clear but you can see it -... (8 Replies)
Discussion started by: dimamu15
8 Replies

6. Shell Programming and Scripting

SFTP file transfer mode question

I am having trouble viewing a file in ASCII after doing a 'get' using SFTP. It appears to have come across as machine language. Does the file have to be in ASCII format prior to the 'get' or is there a way to convert it to ascii after I get it onto my server? I have read where the secure file... (0 Replies)
Discussion started by: wsiefkas
0 Replies

7. Solaris

problem while booting from hdd

hello gurus, i have just installed the os on hdd, when i write down boot command on ok prompt, I get following error continuously. what could be the possible problem WARNING: /ssm@0,0/pci@18,600000/scsi@2/sd@0,0 (sd0): auto request sense failed (reason=reset) WARNING:... (2 Replies)
Discussion started by: sameergrover
2 Replies

8. Solaris

Machine is booting to maintenance mode.

I had a power failure the other day and when my relatively new Solaris 10 machine rebooted it is thrown into maintenance mode. I've found the following lines in the /var/adm/messages file, I'm assuming this is the root cause of the problem. However, I don't have the slightest idea on how to... (9 Replies)
Discussion started by: cheetobandito
9 Replies

9. Filesystems, Disks and Memory

Unix not Booting after defect HDD

Hi there, Here I have an old HP LC3 server from a client of ours. The server was running in Raid1 Mirror mode. Yesterday the server didn't boot anymore and now I have concluded that 1 drive is damaged. I pulled it out so it can boot from the "good" one. Unfortuanally this didn't work. I... (3 Replies)
Discussion started by: severt
3 Replies
Login or Register to Ask a Question
FDISK(8)						      System Manager's Manual							  FDISK(8)

NAME
fdisk - partition a hard disk [IBM] SYNOPSIS
fdisk [-hm] [-sn] [file] OPTIONS
-h Number of disk heads is m -s Number of sectors per track is n EXAMPLES
fdisk /dev/hd0 # Examine disk partitions fdisk -h9 /dev/hd0 # Examine disk with 9 heads DESCRIPTION
When fdisk starts up, it reads in the partition table and displays it. It then presents a menu to allow the user to modify partitions, store the partition table on a file, or load it from a file. Partitions can be marked as MINIX, DOS or other, as well as active or not. Using fdisk is self-explanatory. However, be aware that repartitioning a disk will cause information on it to be lost. Rebooting the sys- tem immediately is mandatory after changing partition sizes and parameters. MINIX, XENIX, PC-IX, and MS-DOS all have different partition numbering schemes. Thus when using multiple systems on the same disk, be careful. Note that MINIX, unlike MS-DOS , cannot access the last sector in a partition with an odd number of sectors. The reason that odd partition sizes do not cause a problem with MS-DOS is that MS-DOS allocates disk space in units of 512-byte sectors, whereas MINIX uses 1K blocks. Fdisk has a variety of other features that can be seen by typing h. Fdisk normally knows the geometry of the device by asking the driver. You can use the -h and -s options to override the numbers found. SEE ALSO
part(8). FDISK(8)