Menu
▾
▴
Re: Ahah, 4096 blocksize disk is not recognised under Linux?
|
From: Kulwant B. <kul...@bt...> - 2003-01-06 00:07:11
|
Hello Geert, > So now you saw the `Launch shell' entry as well? :-) Yes, but I didn't know what the syntax for the format command should be. But I won't be using that anyway now until I create some space for the Linux partitions on a "normal" 512 blocksize disk. Unless of course there is a Linux command that I can use to do the low level format :-) >> Partitions list >> >> The following partitions have been detected: >> >> Device Mounted On Type >> /dev/sda1 --Not mounted-- FFS >> /dev/sda2 --Not mounted-- FFS >> /dev/sda3 --Not mounted-- FFS >> /dev/sda4 --Not mounted-- FFS >> /dev/sda5 --Not mounted-- FFS >> /dev/sda6 --Not mounted-- FFS >> /dev/sda7 --Not mounted-- FFS >> >> Disk /dev/sdb has no partitons defined >> Disk /dev/sdc has no partitions defined > Aha, so it could be a problem with the partitioning support. Were these > disks partitioned under AmigaOS using HDToolBox? If yes, chances are high > that the Amiga RDB (Rigid Disk Block) support doesn't handle 4096-byte > blocks yet. Yes the disks were partitioned under AmigaOS using HDToolbox. I do know that the Amiga had trouble setting the blocksize to 512, I can set it to 4096 and above, but nothing less than 4096. To do this the disks would have to be low level formatted with a blocksize of 512. Once a disk has a blocksize of 512, the Amiga supports all blocksize from 512 up to 16384 (I think), but the low level blocksize is critical. Unfortunately none of the low level format commands on the Amiga have succeeded in resetting the block size to 512 :-( >> /dev/sdd1 --Not mounted-- FFS >> /dev/sdd2 --Not mounted-- FFS >> /dev/sdd3 --Not mounted-- FFS >> /dev/sdd4 --Not mounted-- FFS >> /dev/sdd5 --Not mounted-- FFS >> >> /dev/hda1 --Not mounted-- FFS >> /dev/hda2 --Not mounted-- FFS >> /dev/hda3 --Not mounted-- FFS >> >> where: >> >> sda is a Compaq 18Gb with a 512 blocksize >> sdb is a Seagate Baracudda 4.8Gb with a 4096 blocksize >> sdc is a Seagate Baracudda 4.8Gb with a 4096 blocksize >> sdd is a Compaq 9Gb with a 512blocksize and >> hda is a Connor 420Mb with a 512 blocksize >> >> And all of the disks have a number of partitions each. >> >> sdc is the drive I have set up the Linux partitions on. >> >> All the SCSI drives are second hand and the Seagates came with the 4096 >> blocksize and no Amiga program has been able to low level format them >> with a 512 blocksize. Only a Seagate tool (which runs on PC only) is >> available for this job apparently. > Just thinking of somethings: > 1. Is there a jumper on the drive to choose the blocksize? None that I am aware of, just the ones one would expect on a SCSI drive - SCSI ID, Motor start & delay options, Write Protect, Parity check, SingleEnded I/O & Terminator power. > 2. Does Linux recognize the blocksize during disk probing? E.g. for my > disks it says > | SCSI device sda: 8910423 512-byte hdwr sectors (4562 MB) > | SCSI device sdb: 6281856 512-byte hdwr sectors (3216 MB) > during startup. Will I see this on the text that flashes up when the Penguin appears at the top left of the screen and a whole load of white text on a black background appears? Trouble is, this stuff looks really interesting, but dissappears before I have a chance to read any of it :-( Is there any way I can probe again from a shell? I have tried debug=mem, but dmesg or bootmesg never finds anything after a reboot :-( > Should be safe. I never managed to corrupt my AmigaOS partitions from > within Linux. I know others did, but that was due to bugs in the linux > AFFS support, which were solved a long time ago. Sounds reassuring. > Linux has its own support for disks, which handles the >4 GB case just > fine. Don't know about the Amiga partitioning support, though. Does that mean Linux and Amiga partitions shared on a 18Gb disk are a no no? > BTW, since your Compaq is much larger than 4 GB, what does > `cat /proc/partitions' say? I will try this out andlet you know. Kind regards, Kulwant |
