Shajenko Posted August 20, 2016 Share Posted August 20, 2016 This might be a stupid question, but I want to make sure I'm not missing something very obvious. When I insert a microSD card into the Wifi Pineapple Nano, I stop when I get to the point that a spring is pushing it back out. Doing so results in the Pineapple not seeing the microSD card (I've tried two different ones). It doesn't show in fdisk -l, or in the Resources page under Advanced in the web interface. I have tried using the web interface to format the card and then restart multiple times - still nothing. Thoughts? Quote Link to comment Share on other sites More sharing options...
Just_a_User Posted August 20, 2016 Share Posted August 20, 2016 Hi, the SD needs pushing flush with the nano case, its a spring toggle latch not a slider. Push till it clicks and will stay in with just the edge sticking out of the case. Quote Link to comment Share on other sites More sharing options...
Shajenko Posted August 20, 2016 Author Share Posted August 20, 2016 I was right, I was missing something. I wasn't pushing it in quite far enough. It works fine now. Quote Link to comment Share on other sites More sharing options...
Shajenko Posted August 21, 2016 Author Share Posted August 21, 2016 Spoke too soon. Only the 128 MB card worked - the 32 GB one is seen in fdisk, but doesn't seem to be detected in the web interface. Quote Link to comment Share on other sites More sharing options...
b0N3z Posted August 21, 2016 Share Posted August 21, 2016 you might have to format the sd card in the webui for the pineapple to read it fully Quote Link to comment Share on other sites More sharing options...
Shajenko Posted August 21, 2016 Author Share Posted August 21, 2016 Tried that multiple times, restarting after each time. dmesg says this in the relevant part upon startup: [ 8.600000] scsi 0:0:0:0: Direct-Access Generic STORAGE DEVICE 0933 PQ: 0 ANSI: 6 [ 9.150000] sd 0:0:0:0: [sda] 65536000 512-byte logical blocks: (33.5 GB/31.2 GiB) [ 9.170000] sd 0:0:0:0: [sda] Write Protect is off [ 9.170000] sd 0:0:0:0: [sda] Mode Sense: 21 00 00 00 [ 9.170000] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 9.190000] sda: sda1 sda2 [ 9.200000] sd 0:0:0:0: [sda] Attached SCSI removable disk [ 9.360000] procd: - init - [ 13.090000] Truncating oversized swap area, only using 2097152k out of 8233276k [ 13.110000] Adding 2097148k swap on /dev/sdcard/sd2. Priority:-1 extents:1 across:2097148k [ 13.170000] Loading modules backported from Linux version v4.4-rc5-1913-gc8fdf68 fdisk -l: Disk /dev/mtdblock0: 0 MB, 131072 bytes 255 heads, 63 sectors/track, 0 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk /dev/mtdblock0 doesn't contain a valid partition table Disk /dev/mtdblock1: 1 MB, 1134080 bytes 255 heads, 63 sectors/track, 0 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk /dev/mtdblock1 doesn't contain a valid partition table Disk /dev/mtdblock2: 15 MB, 15446016 bytes 255 heads, 63 sectors/track, 1 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk /dev/mtdblock2 doesn't contain a valid partition table Disk /dev/mtdblock3: 2 MB, 2293760 bytes 255 heads, 63 sectors/track, 0 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk /dev/mtdblock3 doesn't contain a valid partition table Disk /dev/mtdblock4: 0 MB, 65536 bytes 255 heads, 63 sectors/track, 0 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk /dev/mtdblock4 doesn't contain a valid partition table Disk /dev/mtdblock5: 16 MB, 16580608 bytes 255 heads, 63 sectors/track, 2 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk /dev/mtdblock5 doesn't contain a valid partition table Disk /dev/sda: 33.5 GB, 33554432000 bytes 255 heads, 63 sectors/track, 4079 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 1026 4079 24531255 83 Linux /dev/sda2 1 1025 8233281 83 Linux Partition table entries are not in disk order Resources area in webUI: Filesystem Size Used Available Use% Mounted on rootfs 2.2M 572.0K 1.6M 26% / /dev/root 12.8M 12.8M 0 100% /rom tmpfs 29.9M 92.0K 29.8M 0% /tmp /dev/mtdblock3 2.2M 572.0K 1.6M 26% /overlay overlayfs:/overlay 2.2M 572.0K 1.6M 26% / tmpfs 512.0K 0 512.0K 0% /dev Interestingly, after using the webUI to format the SD card, dmesg has this to say: [ 694.070000] usb-storage 1-1.2:1.0: USB Mass Storage device detected [ 694.100000] scsi host1: usb-storage 1-1.2:1.0 [ 695.100000] scsi 1:0:0:0: Direct-Access Generic STORAGE DEVICE 0933 PQ: 0 ANSI: 6 [ 695.100000] sd 1:0:0:0: Attached scsi generic sg0 type 0 [ 695.650000] sd 1:0:0:0: [sdb] 65536000 512-byte logical blocks: (33.5 GB/31.2 GiB) [ 695.660000] sd 1:0:0:0: [sdb] Write Protect is off [ 695.660000] sd 1:0:0:0: [sdb] Mode Sense: 21 00 00 00 [ 695.660000] sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 695.680000] sdb: sdb1 sdb2 [ 695.700000] sd 1:0:0:0: [sdb] Attached SCSI removable disk [ 696.310000] Truncating oversized swap area, only using 2097152k out of 8233276k [ 696.320000] Adding 2097148k swap on /dev/sdcard/sd2. Priority:-2 extents:1 across:2097148k [ 702.220000] sdb: sdb1 sdb2 [ 702.550000] Truncating oversized swap area, only using 2097152k out of 8233276k [ 702.560000] Adding 2097148k swap on /dev/sdcard/sd2. Priority:-2 extents:1 across:2097148k [ 703.130000] Truncating oversized swap area, only using 2097152k out of 8233276k [ 703.140000] Adding 2097148k swap on /dev/sdcard/sd2. Priority:-2 extents:1 across:2097148k [ 744.840000] EXT4-fs (sdb1): couldn't mount as ext3 due to feature incompatibilities [ 744.850000] EXT4-fs (sdb1): couldn't mount as ext2 due to feature incompatibilities [ 744.860000] EXT4-fs (sdb1): ext4_check_descriptors: Block bitmap for group 0 not in group (block 4294967295)! [ 744.870000] EXT4-fs (sdb1): group descriptors corrupted! The SD card is brand new out of the package, but I suppose it still could be damaged. From my readings on the forums, problems with microSD cards are very common. FYI, I'm using firmware version 1.1.1. Next idea is to reset the pineapple to factory settings and see what happens from there. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.