[debian-non-standard] Problems installing debian on FSG-3 (boots from flash, but cannot see internal disk)

[Tomasz Chmielewski]

juan--nsd82 at lavera.dnsalias.net schrieb:
> Hi everyone,
> 
> While trying to follow the instructions at 
> http://wpkg.org/Running_Debian_on_Freecom_FSG-3,
> I couldn't see my internal disk after booting from pendrive.
> (it is the original 500GB disk that came with the FSG, connection is IDE)
> 
> fdisk -l, /proc/scsi, dmesg, ... nowhere could I see a trace of the disk.
> 
> After doing recovery and using the FSG firmware (4.3.8 beta) I discarded 
> a hardware failure. The disk is seen again. The relevant lines from 
> dmesg are:
> 
> <7>libata version 2.00 loaded.
> <7>sata_via 0000:00:0c.0: version 2.0
> <4>PCI: enabling device 0000:00:0c.0 (0000 -> 0001)
> <6>sata_via 0000:00:0c.0: routed to hard irq line 6
> <6>ata1: PATA max UDMA/133 cmd 0x1420 ctl 0x142A bmdma 0x1400 irq 22
> <6>ata2: PATA max UDMA/133 cmd 0x1440 ctl 0x144A bmdma 0x1410 irq 22
> <6>ata3: PATA max UDMA/133 cmd 0x1430 ctl 0x143A bmdma 0x1408 irq 22
> <6>scsi0 : sata_via
> <4>ATA: abnormal status 0x7F on port 0x1427
> <6>scsi1 : sata_via
> <6>ata2.00: ATA-7, max UDMA/133, 976773168 sectors: LBA48
> <6>ata2.00: ata2: dev 0 multi count 0
> <6>ata2.00: configured for UDMA/133
> <6>scsi2 : sata_via
> <4>ATA: abnormal status 0x7F on port 0x1437
> <5>  Vendor: ATA       Model: Hitachi HDT72505  Rev: V56O
> <5>  Type:   Direct-Access                      ANSI SCSI revision: 05
> <5>SCSI device sda: 976773168 512-byte hdwr sectors (500108 MB)
> <5>sda: Write Protect is off
> <7>sda: Mode Sense: 00 3a 00 00
> <5>SCSI device sda: drive cache: write back
> <5>SCSI device sda: 976773168 512-byte hdwr sectors (500108 MB)
> <5>sda: Write Protect is off
> <7>sda: Mode Sense: 00 3a 00 00
> <5>SCSI device sda: drive cache: write back
> <6> sda: sda1 sda2
> <5>sd 1:0:0:0: Attached scsi disk sda
> 
> 
>  From /proc/config.gz (for the FSG original firmware), the part about 
> the disk is:
> 
> #
> # ATA/ATAPI/MFM/RLL support
> #
> # CONFIG_IDE is not set
> 
> #
> # SCSI device support
> #
> # CONFIG_RAID_ATTRS is not set
> CONFIG_SCSI=y
> CONFIG_SCSI_PROC_FS=y
> 
> #
> # SCSI support type (disk, tape, CD-ROM)
> #
> CONFIG_BLK_DEV_SD=y
> # CONFIG_CHR_DEV_ST is not set
> # CONFIG_CHR_DEV_OSST is not set
> CONFIG_BLK_DEV_SR=y
> # CONFIG_BLK_DEV_SR_VENDOR is not set
> # CONFIG_CHR_DEV_SG is not set
> # CONFIG_CHR_DEV_SCH is not set
> #
> # SCSI low-level drivers
> # (JPC comment, all of them disabled except the following ones)
> CONFIG_SCSI_SATA=y
> CONFIG_SCSI_SATA_VIA=y

Yes, it's sata_via module which is used for this SATA chipset.


> So my guess is that maybe some module/configuration is missing in the 
> kernel provided with fsg-3-deploy-stick.tar.bz2.

Works fine for me - I have it installed on multiple FSGs (with a 160 GB 
drive, though).

1) could you post your *full* dmesg when you boot FSG from a USB stick?
2) could you post hdparm -i and hdparm -I for that drive using original 
firmware (I'm not sure they have hdparm, though)? Maybe it's some drive 
which is not supported (I've no idea where to look for)
3) are you familiar with compiling your own kernels? you could compile a 
new kernel and boot it without flashing using kexec. A serial cable 
(preferred; you need to open your FSG) or a USB-serial cable would be 
helpful here, but not necessarily needed.
4) if you can open your FSG and try with another HDD, it would be some 
starting point, too.


The next mail will contain dmesg, fdisk -l etc. for a FSG booted from a HDD.


-- 
Tomasz Chmielewski
http://wpkg.org