PPv4 Connection Refused and New IP Address/MAC

[DaCurryman]

So I'm not very experienced with ALARM and can't explain why this is happening, but here's my situation.

Installed ALARM a few months ago and it was working fine without any problems. All of a sudden, my HD stopped responding, so I tried to SSH in with the root account and see what the issue was. I received a "Connection Refused" message. I did a power reset since I couldn't think of any other way (not being able to log in).

Now comes the weird part. I still can't get it to work, but the PPv4 isn't even registering on my router with the same info. I had it previously set with it's MAC address to a specific IP (192.168.1.99). Now it's showing up on my DHCP list with a new MAC address and on a new IP address. When I try to SSH into that IP address, I still get a "Connection Refused" message.

I'm open to any suggestions since I have no idea what's going on. I unplugged my HD from it till I get this squared away.

Thanks in advance for any help.

Side question: Does everyone else's PPv4 run really hot?

[UberSlackr]

Is ALARM running of a USB? If so, power cycle the PP with the HDD removed.
Wait for Green Light, Wait 2 min, then check Router for IP, then Try SSH.
If SSH connect is achieved, then attach HHD

I was having a similar issue; where it seems the bootloader was looking for ALARM on the HDD instead of the USB.

[DaCurryman]

It was running off USB (on top of the device). Tried power cycling with and without the HD, but didn't do anything.

Finally got it back to stock using the "revert" folder (got scared when that didn't work at first either).

I think I'm gonna give it another shot by reinstalling ALARM. Hopefully once that's done, I can just reconnect the external HD and it'll recognize the volumes. Otherwise, I'm just going to use the PPv4 as it was intended.

[DaCurryman]

OK, so I reinstalled ALARM and can now SSH into it again. Now a stupid question. I plugged the external HD (storage drive) back in, but I have no idea how to identify it within /dev so that I can mount it. I can't seem to find the guide page on the ALARM website that showed me how to do it the first time either.

I don't want to reformat the drive again and lose everything that's on it. Any help here is appreciated.

Thanks.

Additional Info:
I can see that the device recognizes the GoFlex Desk external HD. The SanDisk Micro is my boot USB with ALARM.
$this->bbcode_second_pass_code('', '[root@alarm /]# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 0bc2:50a5 Seagate RSS LLC FreeAgent GoFlex Desk USB 3.0
Bus 001 Device 002: ID 0781:5406 SanDisk Corp. Cruzer Micro U3')

However, it doesn't show up as having a valid partition.
$this->bbcode_second_pass_code('', '[root@alarm /]# cat /proc/partitions
major minor #blocks name

31 0 2048 mtdblock0
31 1 3072 mtdblock1
31 2 3072 mtdblock2
31 3 8192 mtdblock3
31 4 114688 mtdblock4
31 5 64 mtdblock5
8 0 4013894 sda
8 1 4008186 sda1

[root@alarm /]# fdisk -l /dev/[sh]d?

Disk /dev/sda: 4110 MB, 4110227968 bytes, 8027789 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00086853

Device Boot Start End Blocks Id System
/dev/sda1 63 8016434 4008186 83 Linux')

[winestock]

$this->bbcode_second_pass_quote('DaCurryman', 'O')K, so I reinstalled ALARM and can now SSH into it again. Now a stupid question. I plugged the external HD (storage drive) back in, but I have no idea how to identify it within /dev so that I can mount it. I can't seem to find the guide page on the ALARM website that showed me how to do it the first time either.

I don't want to reformat the drive again and lose everything that's on it. Any help here is appreciated.

Thanks.

[DaCurryman]

$this->bbcode_second_pass_quote('winestock', 'I')f at present you have two HDs plugged in then you should see /dev/sdb1 show up. If you have 2 or more partitions on the external HD the you will see, /dev/sdb1, /dev/sdb2, etc. You will need to mount each partition if you want to access it.

[UberSlackr]

just issue
$this->bbcode_second_pass_code('', 'fdisk -l') into the terminal.
post output (should be the same, but just to check)

and make sure you have updated (since you did a fresh install of alARM)
$this->bbcode_second_pass_code('', 'packman -Sy')
to ensure ntfs (assuming this is format of GoFlex Drive) utilities are updated

May also need to install/update ntfsprogs & ntfs-3g:
$this->bbcode_second_pass_code('', '# pacman -S ntfsprogs
# pacman -S ntfs-3g')

[DaCurryman]

$this->bbcode_second_pass_quote('UberSlackr', 'j')ust issue
$this->bbcode_second_pass_code('', 'fdisk -l') into the terminal.
post output (should be the same, but just to check)

and make sure you have updated (since you did a fresh install of alARM)
$this->bbcode_second_pass_code('', 'packman -Sy')
to ensure ntfs (assuming this is format of GoFlex Drive) utilities are updated

May also need to install/update ntfsprogs & ntfs-3g:
$this->bbcode_second_pass_code('', '# pacman -S ntfsprogs
# pacman -S ntfs-3g')

[DaCurryman]

don't know what happened. just rebooted the PPv4 with just the USB stick again and then plugged in the GoFlex and it seems to have picked it up. gonna see what I can do with it now.

$this->bbcode_second_pass_code('', '[root@alarm ~]# cat /proc/partitions
major minor #blocks name

31 0 2048 mtdblock0
31 1 3072 mtdblock1
31 2 3072 mtdblock2
31 3 8192 mtdblock3
31 4 114688 mtdblock4
31 5 64 mtdblock5
8 0 4013894 sda
8 1 4008186 sda1
8 16 2930266580 sdb
8 17 1048576 sdb1
8 18 2929216980 sdb2')

[UberSlackr]

$this->bbcode_second_pass_quote('DaCurryman', 'd')on't know what happened. just rebooted the PPv4 with just the USB stick again and then plugged in the GoFlex and it seems to have picked it up. gonna see what I can do with it now.