Re: wd0(wdc1:0:0): timeout on openbsd 4.0 macppc
On 1 Sep 2008, at 22:41, johan beisser wrote: On Sep 1, 2008, at 11:44 AM, Khalid Schofield wrote: Hi, I'm running openbsd 4.0 (yeh old I know but it's a vital system that I'm replacing but it processes data that makes a lot of money). Better replace the disk tomorrow, then. Or, implement the software on a new system, and take the hit on some downtime while it's being replaced. Thanks for the tip. Just bought one. Those are signs of odd errors on the physical media itself. OpenBSD can (and may) crash due to bad sectors and failed writes. I did allow a system to limp along on a bad drive for nearly a year while I tried to source a very old (no longer available) drive. The old disk is a 40Gb IDE disk and the new one one is a 120Gb disk. If I want to clone the disk can I just cat /dev/sd0 /dev/sd1 if I boot off the install cd? I will rebuild this system on another box but to make sure the disk doesn't die instantly I want to clone it asap since it makes cash. I've got another system on the boil with a 36Gb 15k scsi disk and decent hardware but I want to keep this mac mini server going just long enough to role the new server out. Last night I connected a USB disk and tried to use dump to clone /dev/ rwd0a but it was only dumping the first 4Gb's which was irritating to put it mildly. I used dump -0auf /usb/root.dump /dev/rwd0a I also tried dump -0auB 4198400 -f /usb/root.dump /dev/rwd0a and still it bombs out asking for the next media to be inserted after 4gb's. Doesn't matter what I try still only dumps 4gb's. The system is a g4 which is a 32bit cpu which is the only clue I thought of that would limit me to 4gb's. khalid
Re: wd0(wdc1:0:0): timeout on openbsd 4.0 macppc
I'm running openbsd 4.0 (yeh old I know but it's a vital system that I'm replacing but it processes data that makes a lot of money). Better replace the disk tomorrow, then. Or, implement the software on a new system, and take the hit on some downtime while it's being replaced. Thanks for the tip. Just bought one. Those are signs of odd errors on the physical media itself. OpenBSD can (and may) crash due to bad sectors and failed writes. I did allow a system to limp along on a bad drive for nearly a year while I tried to source a very old (no longer available) drive. The old disk is a 40Gb IDE disk and the new one one is a 120Gb disk. If I want to clone the disk can I just cat /dev/sd0 /dev/sd1 if I boot off the install cd? No. Do a proper install, then do a dump|restore of the filesystems you need to preserve. I will rebuild this system on another box but to make sure the disk doesn't die instantly I want to clone it asap since it makes cash. I've got another system on the boil with a 36Gb 15k scsi disk and decent hardware but I want to keep this mac mini server going just long enough to role the new server out. Last night I connected a USB disk and tried to use dump to clone /dev/ rwd0a but it was only dumping the first 4Gb's which was irritating to put it mildly. I used dump -0auf /usb/root.dump /dev/rwd0a Why is your / that big? Do you really need to dump it as one whole? I also tried dump -0auB 4198400 -f /usb/root.dump /dev/rwd0a and still it bombs out asking for the next media to be inserted after 4gb's. Doesn't matter what I try still only dumps 4gb's. The system is a g4 which is a 32bit cpu which is the only clue I thought of that would limit me to 4gb's. khalid
Re: wd0(wdc1:0:0): timeout on openbsd 4.0 macppc
On 2008-09-02, Khalid Schofield [EMAIL PROTECTED] wrote: If I want to clone the disk can I just cat /dev/sd0 /dev/sd1 if I boot off the install cd? dd if=/dev/rsd0c of=/dev/rsd1c This will limit you to the size of the smaller drive. It is better to (fdisk)/disklabel/newfs/mount partitions on the new drive, then you can do things like cd /newdrive; dump -0uf - / | restore rf - cd /newdrive/usr; dump -0uf - /usr | restore rf - etc. Last night I connected a USB disk and tried to use dump to clone /dev/ rwd0a but it was only dumping the first 4Gb's which was irritating to put it mildly. I used dump -0auf /usb/root.dump /dev/rwd0a I also tried dump -0auB 4198400 -f /usb/root.dump /dev/rwd0a and still it bombs out asking for the next media to be inserted after 4gb's. See mount_msdos(8) CAVEATS, then reformat it with FFS.
Re: wd0(wdc1:0:0): timeout on openbsd 4.0 macppc
Khalid Schofield wrote: On 1 Sep 2008, at 22:41, johan beisser wrote: On Sep 1, 2008, at 11:44 AM, Khalid Schofield wrote: Hi, I'm running openbsd 4.0 (yeh old I know but it's a vital system that I'm replacing but it processes data that makes a lot of money). Better replace the disk tomorrow, then. Or, implement the software on a new system, and take the hit on some downtime while it's being replaced. Thanks for the tip. Just bought one. Those are signs of odd errors on the physical media itself. OpenBSD can (and may) crash due to bad sectors and failed writes. I did allow a system to limp along on a bad drive for nearly a year while I tried to source a very old (no longer available) drive. The old disk is a 40Gb IDE disk and the new one one is a 120Gb disk. If I want to clone the disk can I just cat /dev/sd0 /dev/sd1 if I boot off the install cd? I will rebuild this system on another box but to make sure the disk doesn't die instantly I want to clone it asap since it makes cash. if it is making money for you, you need to have a much better maintenance plan, which includes maintenance and upgrade plans. Otherwise, your money making plans are temporary. IF you can read the whole disk: dd if=/dev/rwd0c of=/dev/rwd1c bs=1M will image the disk to another disk. Replace /dev/rwd1c with whatever is appropriate -- another disk, a file, whatever. You can often do this live, at the cost of an fsck on the new disk (which is often not fatal...depending on the app, of course). Odds are, however, you are going to have a fatal read error, so you will probably need to copy files rather than the entire disk image. Personally, I'd just toss together another machine, put OpenBSD 4.3 or 4.4 on it (ok, I'd 4.4 on it, you would put 4.3 on it :), and migrate your apps over to it. I've got another system on the boil with a 36Gb 15k scsi disk and decent hardware but I want to keep this mac mini server going just long enough to role the new server out. I'm not impressed. It is not the bling of your hardware that's a problem, it is the maintenance plan. By pointing out the specs of your hardware, I don't think you have learned your lesson. You will do far better with TWO cheap machines than one expensive machine. This way, you can actually test your upgrade process on a regular basis, and keep this money maker running securely, and deal with hardware failures trivially. Getting a system running is not the sign of good system administration. The trick is having a plan in place to KEEP it running and maintained even when the expected happens. Replacement of the OS, the hardware, the apps all need to be part of the initial plan. Nick.
Re: wd0(wdc1:0:0): timeout on openbsd 4.0 macppc
* Khalid Schofield [EMAIL PROTECTED] [2008-09-02 11:02:21]: On 1 Sep 2008, at 22:41, johan beisser wrote: On Sep 1, 2008, at 11:44 AM, Khalid Schofield wrote: Hi, I'm running openbsd 4.0 (yeh old I know but it's a vital system that I'm replacing but it processes data that makes a lot of money). Better replace the disk tomorrow, then. Or, implement the software on a new system, and take the hit on some downtime while it's being replaced. Thanks for the tip. Just bought one. Those are signs of odd errors on the physical media itself. OpenBSD can (and may) crash due to bad sectors and failed writes. I did allow a system to limp along on a bad drive for nearly a year while I tried to source a very old (no longer available) drive. The old disk is a 40Gb IDE disk and the new one one is a 120Gb disk. If I want to clone the disk can I just cat /dev/sd0 /dev/sd1 if I boot off the install cd? I will rebuild this system on another box but to make sure the disk doesn't die instantly I want to clone it asap since it makes cash. I've got another system on the boil with a 36Gb 15k scsi disk and decent hardware but I want to keep this mac mini server going just long enough to role the new server out. Last night I connected a USB disk and tried to use dump to clone /dev/ rwd0a but it was only dumping the first 4Gb's which was irritating to put it mildly. I used dump -0auf /usb/root.dump /dev/rwd0a I also tried dump -0auB 4198400 -f /usb/root.dump /dev/rwd0a and still it bombs out asking for the next media to be inserted after 4gb's. Doesn't matter what I try still only dumps 4gb's. The system is a g4 which is a 32bit cpu which is the only clue I thought of that would limit me to 4gb's. khalid If imaging a failing disk is what you really want, then I recommend ddrescue http://www.gnu.org/software/ddrescue/ddrescue.html gnu bleh. -- Travers Buda
Re: wd0(wdc1:0:0): timeout on openbsd 4.0 macppc
On Tue, Sep 2, 2008 at 10:31 PM, Travers Buda [EMAIL PROTECTED] wrote: If imaging a failing disk is what you really want, then I recommend ddrescue http://www.gnu.org/software/ddrescue/ddrescue.html gnu bleh. Not sure what ddresuce means by trying hard to read a device, but it really can't do much that the kernel isn't already going to do with regards to retries. Anyway, if you just want to clone disks, there's also g4u. But it does require running netbsd, at least for a short while. ;) And there's probably some work to make it work on macppc.
Re: wd0(wdc1:0:0): timeout on openbsd 4.0 macppc
* Ted Unangst [EMAIL PROTECTED] [2008-09-02 22:56:49]: On Tue, Sep 2, 2008 at 10:31 PM, Travers Buda [EMAIL PROTECTED] wrote: If imaging a failing disk is what you really want, then I recommend ddrescue http://www.gnu.org/software/ddrescue/ddrescue.html gnu bleh. Not sure what ddresuce means by trying hard to read a device, but it really can't do much that the kernel isn't already going to do with regards to retries. Anyway, if you just want to clone disks, there's also g4u. But it does require running netbsd, at least for a short while. ;) And there's probably some work to make it work on macppc. You can get the recoverable stuff off a disk quickly because you can tell it to automatically skip over groups of bad sectors when you run into them (in the stead of retry, retry, retry) and go back over the troublesome spots later. That way you can get most of the data off the disk before the whole thing blows up and grapeshots your machine room with exploded platters containing all your precious data. However, you should never need a tool like this because you have a proper backup and recovery scheme, right, RIGHT? -- Travers Buda
Re: wd0(wdc1:0:0): timeout on openbsd 4.0 macppc
Khalid Schofield wrote: Hi, I'm running openbsd 4.0 (yeh old I know but it's a vital system that I'm replacing but it processes data that makes a lot of money). I'm getting these errors in dmesg. Should I be freaked out that the disk is failing or is it something else? I have tar backups but I want to make totally sure so I'm doing a dump in single user mode tonight (if it lets me who knows...). It's running on a powerpc mac mini. Errors are as follows: wd0(wdc1:0:0): timeout type: ata c_bcount: 32768 c_skip: 0 wd0a: device timeout reading fsbn 11840224 of 11840224-11840287 (wd0 bn 11843248; cn 11749 tn 4 sn 4), retrying wd0: soft error (corrected) /snip I would get a new disk soon. Fred :~S PS Out of interest how is the disk partitioned?
Re: wd0(wdc1:0:0): timeout on openbsd 4.0 macppc
On Sep 1, 2008, at 11:44 AM, Khalid Schofield wrote: Hi, I'm running openbsd 4.0 (yeh old I know but it's a vital system that I'm replacing but it processes data that makes a lot of money). Better replace the disk tomorrow, then. Or, implement the software on a new system, and take the hit on some downtime while it's being replaced. Those are signs of odd errors on the physical media itself. OpenBSD can (and may) crash due to bad sectors and failed writes. I did allow a system to limp along on a bad drive for nearly a year while I tried to source a very old (no longer available) drive.
