| Title | Date | Comments | |||
|---|---|---|---|---|---|
| recover file before it is deleted | 1997-2004 | ||||
| - If the app has the file open, its data blocks will not be deleted until kmail closes the file. Therefore, tool like "lsof" can find the inode number of the file. - | |||||
| grub vs. lilo | 1997-2004 | ||||
| - Grub is a lot "smarter" in that it has its own mini-shell, knows about a lot of filesystem formats, and can be configured extensively to boot almost anything no matter how weird its startup requirements may be. I've had to deal with a busted system in the past, and Grub's shell facilities enabled me to take a look and see what was wrong -- and even, fix the problem. - | |||||
| drive geometry 3.2v4.2 | 1997-2004 | ||||
| - It doesn't matter what geometry you claim as long as it multiplies out to the right size (or a bit less) - | |||||
| fsck fails crashed disk linux | 1997-2004 | ||||
| - fsck fails crashed disk linux. The superblock could not be read or does not describe a correct ext2 file system - | |||||
| divvy filesystem larger than device -->Re Unable tomount 2nd hard drive, filesystem size is larger than device | 1997-2004 | ||||
| - divvy filesystem larger than device -->Re: Unable tomount 2nd hard drive, filesystem size is larger than device - | |||||
| bad rcp performance -->Re Very bad RCP performance inLinux-help! | 1997-2004 | ||||
| - bad rcp performance -->Re: Very bad RCP performance inLinux-help! - | |||||
| trubleshooting data file corruption testing disks memory-->Re How to trouble-shoot file corruption? | 1997-2004 | ||||
| - If you don't have the space, you have to take running snapshots with fuser or lsof- that may not satisfy a very stubborn vendor who is convinced that *their* programs never screw up. - | |||||
| mounting old hard drive divvy disk geometry -->Re Can'tmount drive with install disk. | 1997-2004 | ||||
| - SCSI disks on OpenServer obtain their geometry from a combination of the motherboard BIOS, host adapter, host adapter BIOS, and disk. - | |||||
| defragmenting Unix filesystems -->Re Defrag freeware? | 1997-2004 | ||||
| - defragmenting Unix filesystems -->Re: Defrag freeware? - | |||||
| 5.0.6 filesystem sizes -->Re SCO Unix 5.0.6a | 1997-2004 | ||||
| - 5.0.6 filesystem sizes -->Re: SCO Unix 5.0.6a - | |||||
| RAID configuration -->Re how to configure a logicaldrive | 1997-2004 | ||||
| - The logical drive presents itself as a physical drive. If you look at /etc/conf/cf.d/mscsi now, you'll see one entry for your RAID array- presented as one physical drive. - | |||||
| fsck lost+found inode -->Re rebooting problem | 1997-2004 | ||||
| - If it is named "12 it was originally inode 12. You'd need someone with the same (unmentioned) version and maybe even a similar install method to be sure what that would be. - | |||||
| data recovery break-in security lazarus -->Re DamagedEXT2 parition; standard utilities didn't help | 1997-2004 | ||||
| - Maybe. In another ng this morning a person I know and respect was waxing on about http://www.porcupine.org/forensics/ Apparently it includes a program called Lazarus that runs through disk blocks intelligently. Here's what he had to say about it: - | |||||
| write to running program -->Re What happensif... | 1997-2004 | ||||
| - Depends on what you are relacing and how smart the replacement program is about what it is doing. Generally speaking, Unix systems won't let you overwrite a binary that is in memory- that is enforced because of paging: not all of the binary is necessarily in memory and other parts may need to be brought in from disk- to avoid a spectacular crash, you aren't allowed to do that. However, the locking out is by inode number (names are really meaningless to the kernel) so an update that knows enough to move the older binary to another name (or just remove it outright) can slip in a replacement. - | |||||
| fsck 3.2v4.2 free list -->Re fsstat root filesystemneeds checking | 1997-2004 | ||||
| - I don't recall the specifics of this, but did you answer "y" (or - | |||||
| 2Gb file size limit -->Re tar and tgz size | 1997-2004 | ||||
| - Who knows how many years will pass before none of these limitations exist anywhe - | |||||
| probe scsi disks odt3 -->Re Probing SCSI HD on SCO ODT3 | 1997-2004 | ||||
| - Well, as long as you don't touch the partition, the next thing you get is a divvy table- that would tell you for sure what you are looking at. Double check /etc/conf/cf.d/mscsi to be sure the right stuff got in there. - | |||||
| mkdev hd fisk no such device -->Re SCSI HardDrive | 1997-2004 | ||||
| - I suspect you may be confused as to what the first invocation of mkdev hd did, which really was nothing more than to trust you: in other words, you said "there's a scsi disk attached to this controller and it has this id, etc." and mkdev hd said "Kewl- I'll add that to /etc/conf/cf.d/mscsi and build a new kernel which can access that". - | |||||
| compaq IDA raid -->Re Compaq array | 1997-2004 | ||||
| - You couldn't have a 2 disk RAID 5 array. RAID 5 needs at least 3 disks.: You say "Only 2 of the disks have been allocated to a filesystem"; - | |||||
| defragmenting scsi disk database raw partitions -->ReDefrag Continued. Speed is Speed | 1997-2004 | ||||
| - defragmenting scsi disk database raw partitions -->Re:Defrag Continued. Speed is Speed - | |||||
| Windows cd-rw cdrom -->Re copy tar file to cd inwindows- can Sco read it? | 1997-2004 | ||||
| - Windows cd-rw cdrom -->Re: copy tar file to cd inwindows- can Sco read it? - | |||||
| biosgeom 1023 cylinder boot -->Re 1023 CylinderLimit | 1997-2004 | ||||
| - biosgeom 1023 cylinder boot -->Re: 1023 CylinderLimit - | |||||
| Install SCO Unix on non-default division/partition | 1997-2004 | ||||
| - To install anywhere other than the default division-2-of-active-partition requires hackery that few people know - | |||||
| vmware and old sco image | 1997-2004 | ||||
| - Old SCO 3.2v4.2 in vmware? Obtaining memory map with 'defbootstr prompt' - | |||||
| cloning sco disk with dd - data corruption | 1997-2004 | ||||
| - Note that when OSR505 first shipped, the idea of a 20GB IDE disk was some sort of bizarre fantasy. - | |||||
| mkdev hd is all you need | 1997-2004 | ||||
| - Why don't people just run "mkdev hd" ? That gives an interface that lets you choose what you are adding and is less likely to get you confused or in trouble. - | |||||
| using microlite edge to back up non-unix partitions | 1997-2004 | ||||
| - BackupEDGE will backup and restore non-UNIX partitions. A great deal of work has gone in to giving BackupEDGE the ability to backup, checksum, compress, encrypt, restore and disaster-recover non-UNIX partitions - | |||||
| 2 TB drives(SCO Unix) | 1997-2004 | ||||
| - When this was written (November 2005), there was no such thing as a terabyte drive and most of us couldn't imagine ever using one. - | |||||
| sata ide emulation SCO Unix 5.0.6/7 ahci driver | 1997-2004 | ||||
| - Without the expense of a SATA RAID controller and driver software, SATA drives under 5.0.6 and 5.0.7 just run in IDE emulation mode. - | |||||
| scoansi vs. ansi vs. at386 (SCO Unix);Re 1023 Cylinder Limit | 1997-2004 | ||||
| - These are all variants of 'ansi' terminal emulation, but obviously there are differences. Examining termcap or using infocomp can show what the differences are. - | |||||
| damaged file system | 1997-2004 | ||||
| - If the disk geometry hasn't suddenly changed, mount: cannot stat '/dev/u' means a corrupted superblock. Recovery is not easy, period. - | |||||
| hdparm -u | 1997-2004 | ||||
| - When is it safe to use hdparm -u? Is it safe for my drive/controller combination? - | |||||
| unusable space in fdisk | 1997-2004 | ||||
| - You have only 4 primary partitions available and you have used all of them. Thus although there is space available, there is no partition toput it in! It's unusable. - | |||||
| fsrd read sco filesystem | 1997-2004 | ||||
| - fsrd read sco filesystem from Linux - | |||||
| /etc/ff ff command ncheck -->Re /etc/ff | 1997-2004 | ||||
| - ff(ADM) comments 'This command only works on UNIX filesystems.' What it really means is that it only works on S51K filesystems (and, more by luck than by design, on the closely affiliated filesystem types ES51K, AFS and EAFS). I haven't checked, but wouldn't be surprised if it also worked on Xenix filesystems... - | |||||
| informix 2gb partitions -->Re raw disks | 1997-2004 | ||||
| - Surely it must support using multiple raw partitions? If you use OpenServer's partitions & divisions to their fullest, you can have 28 divisions on a disk == 56GB. Ok, won't let you use all of a reasonably big current disk, but you can have 54GB of 2GB raw divisions + one big Unix filesystem on the rest... - | |||||
| panic from bad hard drive -->Re Panic trap solved | 1997-2004 | ||||
| - When we physically removed the disk drive from the cabinet, the panic - | |||||
| move sco to smaller drive -->Re Ghosting SCO to asmaller drive | 1997-2004 | ||||
| - move sco to smaller drive -->Re: Ghosting SCO to asmaller drive - | |||||
| 1542 scsi adaptor -->Re Errors after moving HD | 1997-2004 | ||||
| - Be aware that all 1542's are not the same. The 'C's' were not very good, the 'CF' was a pretty good card and the 'CP's' were more of a problem. - | |||||
| ide and scsi boot -->Re Adding IDE drive toOSR5.0.5 | 1997-2004 | ||||
| - ide and scsi boot -->Re: Adding IDE drive toOSR5.0.5 - | |||||
| linux cdrw cdrecord mkisofs -->Re Mkisofs How to createan empty ISO9660 image | 1997-2004 | ||||
| - linux cdrw cdrecord mkisofs -->Re: Mkisofs: How to createan empty ISO9660 image - | |||||
| Unixware UW veritas sync frequency -->Re syncfrequency | 1997-2004 | ||||
| - Unixware UW veritas sync frequency -->Re: "sync"frequency - | |||||
| unzip 10gb file -->Re GUNZIP a 10Gb file? | 1997-2004 | ||||
| - File system limits on older systems, LFS introduced late 20000 - | |||||
| marking bad disk sectors -->Re marking 'bad'sectors? | 1997-2004 | ||||
| - marking bad disk sectors -->Re: marking 'bad'sectors? - | |||||
| Perc driver not loaded -->Re DELL 2400 & PERCcontroller SCO 5.0.5 install failure . | 1997-2004 | ||||
| - Perc driver not loaded -->Re: DELL 2400 & PERCcontroller SCO 5.0.5 install failure . - | |||||
| -->Re 1024 Cyls or Mb's? | 1997-2004 | ||||
| - Physical disk geometry vs. logical disk geometry0 - | |||||
| ideMap ide devices query ide -->Re Adding new disk to SCO box | 1997-2004 | ||||
| - Undocumented SCO Unix /etc/ideMap command to show ide devices. - | |||||
| 32 bit vs 64 bit scsi dma 2940 pci -->Re Is U160 REALLY faster than Ultra-Wide on SCO? | 1997-2004 | ||||
| - Arguments over mixing 32 bit and 64 bit scsi devices. Do the 32 bit devices destroy the value of the 64 bit? - | |||||
| defragment scsi disk -->Re Defrag Software | 1997-2004 | ||||
| - Comments on SCI seek optimizations and their effect on fragmentation - | |||||
| Windows CDROM -->Re how do I store disk images of unix disk on w95 cdrom | 1997-2004 | ||||
| - Storing floppy disk imaages on CDROM or DVD for archival storage - | |||||
![]() | |||||
| timeout on fixed disk -->Re Error message Timeout on fixed disk??? | 1997-2004 | ||||
| - What can cause a hard drive to lock up and time out?0 - | |||||
| divvy sees NON FS -->Re Problem with FS | 1997-2004 | ||||
| - NONFS tag shown in SCO Unix divvy - troubleshooting advice - | |||||
| lost lilo -->Re Get Lilo Back?!?!?!?!? | 1997-2004 | ||||
| - Recover missing lilo or grub configuration from boot or rescue floppy or CD - | |||||
| HTFS filesystem inodes -->Re When Double/Triple indirect blocks on SCO 5 | 1997-2004 | ||||
| - The SCO Unix HTFS filesystem has the same indirect block layout as earlier versions.0 - | |||||
| SCSI disk performance -->Re Disk Xfer Rates vs Bus speed | 1997-2004 | ||||
| - Old SCSI disk performance benchmarks make interesting historical reference. - | |||||
| bandwidth vs. servers -->Re Print servers + ip printing+ scoadmin = brain haemorrage | 1997-2004 | ||||
| - Assigning printer names, assigning ip addreses, cloning disks -a mixed bag!0 - | |||||
| alad vs. alad325 -->Re SCSI Drivers | 1997-2004 | ||||
| - An example of why you have to be careful when searching for drivers to install old SCO Unix - | |||||
| Comparisons of file systems -->Re Why v5.0.x emergency floppies take so long to load ? (solved) | 1997-2004 | ||||
| - SCO Unix and Xenix file system details, including floppy disk formats.0 - | |||||
| Finding symbolic links -->Re Recommendations on upgrading from 504 to 505 | 1997-2004 | ||||
| - A more complex and potentially useful script for finding symbolic links and displaying their destinations in an orderly way.0 - | |||||
More Disks/Filesystems articles
Previous Disks/Filesystems articles