Skip to main content
Tweeted twitter.com/#!/StackRaspi/status/280446002316603392
added fsck output
Source Link
Matt Ellen
  • 151
  • 1
  • 7
/dev/sdd2Pass 1: cleanChecking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

   66856/237568 inodes used (28.14%)
      25 non-contiguous files, 386579(0.0%)
      93 non-contiguous directories (0.1%)
         # of inodes with ind/948480dind/tind blocks: 0/0/0
         Extent depth histogram: 51823/14
  386579 blocks used (40.76%)
       0 bad blocks
       1 large file

   46850 regular files
    4498 directories
      12 character device files
      25 block device files
       2 fifos
     594 links
   15460 symbolic links (14972 fast symbolic links)
       0 sockets
--------
   67441 files
Checking we can access the last sector of the filesystem
Boot sector contents:
System ID "mkdosfs"
Media byte 0xf8 (hard disk)
       512 bytes per logical sector
      8192 bytes per cluster
        16 reserved sectors
First FAT starts at byte 8192 (sector 16)
         2 FATs, 16 bit entries
     16384 bytes per FAT (= 32 sectors)
Root directory starts at byte 40960 (sector 80)
       512 root directory entries
Data area starts at byte 57344 (sector 112)
      7161 data clusters (58662912 bytes)
63 sectors/track, 255 heads
         0 hidden sectors
    114688 sectors total
Reclaiming unconnected clusters.
/dev/sdd1: 11 files, 2109/7161 clusters
/dev/sdd2: clean, 66856/237568 files, 386579/948480 blocks
/dev/sdd1: 11 files, 2109/7161 clusters
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

   66856 inodes used (28.14%)
      25 non-contiguous files (0.0%)
      93 non-contiguous directories (0.1%)
         # of inodes with ind/dind/tind blocks: 0/0/0
         Extent depth histogram: 51823/14
  386579 blocks used (40.76%)
       0 bad blocks
       1 large file

   46850 regular files
    4498 directories
      12 character device files
      25 block device files
       2 fifos
     594 links
   15460 symbolic links (14972 fast symbolic links)
       0 sockets
--------
   67441 files
Checking we can access the last sector of the filesystem
Boot sector contents:
System ID "mkdosfs"
Media byte 0xf8 (hard disk)
       512 bytes per logical sector
      8192 bytes per cluster
        16 reserved sectors
First FAT starts at byte 8192 (sector 16)
         2 FATs, 16 bit entries
     16384 bytes per FAT (= 32 sectors)
Root directory starts at byte 40960 (sector 80)
       512 root directory entries
Data area starts at byte 57344 (sector 112)
      7161 data clusters (58662912 bytes)
63 sectors/track, 255 heads
         0 hidden sectors
    114688 sectors total
Reclaiming unconnected clusters.
/dev/sdd1: 11 files, 2109/7161 clusters
added fsck output
Source Link
Matt Ellen
  • 151
  • 1
  • 7

On boot I'm getting to the line

[OK] Setting kernel variables ... done

A few lines before that there is a failure

[....] Mounting local file system...[    14.601764] mmc0: missed completion of cmd 18 DMA (512/512 [1]/[1]) - ignoring it
[    14.914927] mmc0: DMA IRQ 6 ignored - results were reset
failed

The changes leading up to the this were that I installed upstart and then tried to reboot (sudo reboot). The reboot command didn't error, it also didn't do anything, no output to the screen like "Hey I'm about to reboot!" or whatever the normal message is. I tried the command a few more times, and then pulled the plug. I've been getting the above or simply a failure to load the file system ever since.

How can I fix this?

Output from fsck (3.9GB part, ext4):

/dev/sdd2: clean, 66856/237568 files, 386579/948480 blocks

59MB part, vfat:

/dev/sdd1: 11 files, 2109/7161 clusters

On boot I'm getting to the line

[OK] Setting kernel variables ... done

A few lines before that there is a failure

[....] Mounting local file system...[    14.601764] mmc0: missed completion of cmd 18 DMA (512/512 [1]/[1]) - ignoring it
[    14.914927] mmc0: DMA IRQ 6 ignored - results were reset
failed

The changes leading up to the this were that I installed upstart and then tried to reboot (sudo reboot). The reboot command didn't error, it also didn't do anything, no output to the screen like "Hey I'm about to reboot!" or whatever the normal message is. I tried the command a few more times, and then pulled the plug. I've been getting the above or simply a failure to load the file system ever since.

How can I fix this?

On boot I'm getting to the line

[OK] Setting kernel variables ... done

A few lines before that there is a failure

[....] Mounting local file system...[    14.601764] mmc0: missed completion of cmd 18 DMA (512/512 [1]/[1]) - ignoring it
[    14.914927] mmc0: DMA IRQ 6 ignored - results were reset
failed

The changes leading up to the this were that I installed upstart and then tried to reboot (sudo reboot). The reboot command didn't error, it also didn't do anything, no output to the screen like "Hey I'm about to reboot!" or whatever the normal message is. I tried the command a few more times, and then pulled the plug. I've been getting the above or simply a failure to load the file system ever since.

How can I fix this?

Output from fsck (3.9GB part, ext4):

/dev/sdd2: clean, 66856/237568 files, 386579/948480 blocks

59MB part, vfat:

/dev/sdd1: 11 files, 2109/7161 clusters
Source Link
Matt Ellen
  • 151
  • 1
  • 7

Not completing boot. Failing to mount the local file system

On boot I'm getting to the line

[OK] Setting kernel variables ... done

A few lines before that there is a failure

[....] Mounting local file system...[    14.601764] mmc0: missed completion of cmd 18 DMA (512/512 [1]/[1]) - ignoring it
[    14.914927] mmc0: DMA IRQ 6 ignored - results were reset
failed

The changes leading up to the this were that I installed upstart and then tried to reboot (sudo reboot). The reboot command didn't error, it also didn't do anything, no output to the screen like "Hey I'm about to reboot!" or whatever the normal message is. I tried the command a few more times, and then pulled the plug. I've been getting the above or simply a failure to load the file system ever since.

How can I fix this?